Skip to content

add numRows to segment metadata query response#1995

Merged
jon-wei merged 1 commit intoapache:masterfrom
himanshug:num_rows_seg_metadata_query
Dec 17, 2015
Merged

add numRows to segment metadata query response#1995
jon-wei merged 1 commit intoapache:masterfrom
himanshug:num_rows_seg_metadata_query

Conversation

@himanshug
Copy link
Copy Markdown
Contributor

I often need to see the number of rows in segments for some intervals. currently you can do that, for example, by sending a group-by query with count aggregator.
however, I think adding numRows to segment metadata query response makes it way more convenient.

also other queries with count aggregator would need to scan the segment in order to compute rows in the segment.

@himanshug himanshug force-pushed the num_rows_seg_metadata_query branch from 9960e6e to 7a89b2e Compare November 20, 2015 07:25
@himanshug himanshug added this to the 0.9.0 milestone Dec 2, 2015
@gianm
Copy link
Copy Markdown
Contributor

gianm commented Dec 4, 2015

@himanshug do you think we should add an analysis type for numRows, or simply always report it? I guess always reporting is fine, as numRows is cheap to compute- I think it's cached in the java heap and doesn't require hitting the mmapped segment.

@gianm
Copy link
Copy Markdown
Contributor

gianm commented Dec 4, 2015

👍

@himanshug
Copy link
Copy Markdown
Contributor Author

@gianm numRows is already available in the code so no expense .

@jon-wei
Copy link
Copy Markdown
Contributor

jon-wei commented Dec 17, 2015

👍

jon-wei added a commit that referenced this pull request Dec 17, 2015
add numRows to segment metadata query response
@jon-wei jon-wei merged commit f8cf84f into apache:master Dec 17, 2015
himanshug pushed a commit to himanshug/druid that referenced this pull request Jan 20, 2016
@himanshug himanshug deleted the num_rows_seg_metadata_query branch February 8, 2016 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants