Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-8551

Should BIGINT in Flink SQL will be enchanced

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.4.0
    • Component/s: Table SQL / API
    • Labels:
      None

      Description

      As we all known , see https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-type-conversions.html

      SQL data type BIGINT in mysql represents UNSIGNED BIGINT by default , it can receive value from some columns typed Long or BigInteger if we use java/scala driver to write data into db.

      MySQL Type Name Return value of GetColumnTyneName Return value of GetColumnClassName
      BIGINT[(M)] [UNSIGNED] BIGINT [UNSIGNED] java.lang.Long, if UNSIGNED java.math.BigInteger

       

      But now , in Flink SQL BIGINT just represents SIGNED BIGINT, that to say it can only receive value from some columns typed Long .

      all supported types of the Table API defined in this class org.apache.flink.table.api.Types

       

      so if we should let BIGINT in Flink SQL match the BIGINT in some SQL Engine , like MySQL.

      Or, as a new feature, support a new FLINK SQL type named BIGINTEGER for Java type Biginteger and also into MySQL BIGINT?

       

       

       

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              lynchlee Lynch Lee
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: