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

Rel Id should be generated per query context instead of globally

    XMLWordPrintableJSON

Details

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

    Description

      The rel id will continue increasing until the class is unloaded. We have observed that the id is reaching 100 million after running for just several days. Although we don't use the id for calculation, it might be OK for integer overflow, but it doesn't make sense to generate unique id globally, it will hard to read the dumped plan and the rel id in the log, because the rel id is so large. IMO, the id should be generated per query context.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              hyuan Haisheng Yuan
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: