adarshsanjeev commented on PR #12844: URL: https://github.com/apache/druid/pull/12844#issuecomment-1205226149
Thanks for the suggestion, that's a good idea to document the known issue. As for the index, I checked the above on a local MySql Druid metadata storage with EXPLAIN ANALYZE and it appears to be using an index. I tried a query for the intervals [2022-01-01/2022-06-01], [2022-08-01/2023-01-01], [1970-08-01/1971-01-01]. > Index lookup on druid_segments using idx_druid_segments_datasource_used_end_start (dataSource='mytest', used=true), with index condition: (((druid_segments.`start` < '2022-06-01T00:00:00.000Z') and (druid_segments.`end` > '2022-01-01T00:00:00.000Z')) or (druid_segments.`start` = '-146136543-09-08T08:23:32.096Z') or ((druid_segments.`start` < '2023-01-01T00:00:00.000Z') and (druid_segments.`end` > '2022-08-01T00:00:00.000Z')) or (druid_segments.`start` = '-146136543-09-08T08:23:32.096Z') or ((druid_segments.`start` < '1971-01-01T00:00:00.000Z') and (druid_segments.`end` > '1970-08-01T00:00:00.000Z')) or (druid_segments.`start` = '-146136543-09-08T08:23:32.096Z')) (cost=0.30 rows=1) (actual time=0.028..0.030 rows=1 loops=1) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
