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

Druid adapter: Use "scan" query rather than "select" query

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.16.0
    • Component/s: druid
    • Labels:
      None

      Description

      The biggest difference between select query and scan query is that, scan query doesn't retain all rows in memory before rows can be returned to client.
      Select query on very large segments will cause memory pressure on druid historicals if too many rows required by select query whereas Scan query doesn't have this issue.
      Scan query can also return all rows without issuing another pagination query, which is extremely useful when query against historical or realtime node directly.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                nishantbangarwa Nishant Bangarwa
                Reporter:
                nishantbangarwa Nishant Bangarwa
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: