You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2018/12/01 21:18:18 UTC

[GitHub] erankor commented on issue #6661: Slow timeBoundary queries

erankor commented on issue #6661: Slow timeBoundary queries
URL: https://github.com/apache/incubator-druid/issues/6661#issuecomment-443459247
 
 
   Thanks @kaijianding!
   The data source in the first example (timeBoundary) is tiny, the one from the second example (segmentMetadata) is larger -
   ```
   mysql> select count(1) from druid_segments where used and dataSource = 'reach-usage';
   +----------+
   | count(1) |
   +----------+
   |       22 |
   +----------+
   
   mysql> select count(1) from druid_segments where used and dataSource = 'player-events-historical';
   +----------+
   | count(1) |
   +----------+
   |    14740 |
   +----------+
   ```
   To make sure I understand what you wrote - in order to answer the second query, the broker has to perform it for all segments and merge the results?
   If so, maybe I'll hack it so that it only performs it for the last week or so, the latest schema is probably what I want anyway...

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org