Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-924

Ensure connectionIDs are unique

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • avatica
    • None

    Description

      Follow-up work from CALCITE-906:

      Some recommendations from ndimiduk from HBase-landia:

      We'll need unique connection ID's as well. HBase uses a combination of a unique hash per client + random number. Maybe we can do similarly for connections, and with a connection hash plus random number for statements. https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/PerClientRandomNonceGenerator.java

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. CALCITE-906 Avatica JdbcMeta statement IDs are not unique

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              elserj Josh Elser
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: