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

Hive/Druid integration: Incorrect result - Limit on timestamp disappears

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 3.0.0
    • Component/s: Druid integration
    • Labels:
      None
    • Target Version/s:

      Description

      This can be observed with the following query:

      SELECT DISTINCT `__time`
      FROM store_sales_sold_time_subset_hive
      ORDER BY `__time` ASC
      LIMIT 10;
      

      Query is translated correctly to Druid timeseries, but limit operator disappears.

      OK
      Plan optimized by CBO.
      
      Stage-0
        Fetch Operator
          limit:-1
          Select Operator [SEL_1]
            Output:["_col0"]
            TableScan [TS_0]
              Output:["__time"],properties:{"druid.query.json":"{\"queryType\":\"timeseries\",\"dataSource\":\"druid_tpcds_ss_sold_time_subset\",\"descending\":false,\"granularity\":\"NONE\",\"aggregations\":[],\"intervals\":[\"1900-01-01T00:00:00.000Z/3000-01-01T00:00:00.000Z\"]}","druid.query.type":"timeseries"}
      

      Thus, result has more than 10 rows.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jcamachorodriguez Jesus Camacho Rodriguez
                Reporter:
                jcamachorodriguez Jesus Camacho Rodriguez
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: