Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-5559

Frontend and backend have different notions of which slots are var-len.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • Impala 2.10.0
    • None
    • Frontend

    Description

      I discovered this on my buffer pool dev branch because the planner miscomputed the amount of reservation required for the sorter on this query:

      select t1.cl, COUNT(1) FROM chars_tiny t1 GROUP BY 1 ORDER BY t1.cl
      

      The frontend thinks that it doesn't need var-len data blocks to store t1.cl, which is a large CHAR() column.

      I think the problem is that two different concepts are being confused in the code:

      • Is the amount of storage required for the slot always a fixed amount?
      • Does the slot store data out-of-line from the main tuple?

      Attachments

        Issue Links

          Activity

            People

              tarmstrong Tim Armstrong
              tarmstrong Tim Armstrong
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: