Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-17627

Use druid scan query instead of the select query.

Log workAgile BoardRank to TopRank to BottomVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0
    • Component/s: Druid integration
    • 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.
      It will cause memory pressure if too many rows required by select query.
      Scan query doesn't have this issue.
      Scan query can return all rows without issuing another pagination query, which is extremely useful when query against historical or realtime node directly.

        Attachments

        1. HIVE-17627.1.patch
          15 kB
          Nishant Bangarwa
        2. HIVE-17627.2.patch
          15 kB
          Nishant Bangarwa
        3. HIVE-17627.patch
          15 kB
          Nishant Bangarwa

        Issue Links

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              nishantbangarwa Nishant Bangarwa Assign to me
              Reporter:
              bslim Slim Bouguerra

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment