-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Star Tree] [Search] Support for metric aggregations with/without term query #15289
base: main
Are you sure you want to change the base?
Conversation
❌ Gradle check result for ad54ace: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 6c6be02: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
995db38
to
885a383
Compare
❌ Gradle check result for 995db38: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 885a383: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 9491aae: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for a01c6e2: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
server/src/main/java/org/opensearch/index/query/QueryShardContext.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/search/startree/StarTreeFilter.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/search/startree/StarTreeQuery.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/opensearch/search/startree/StarTreeQuery.java
Outdated
Show resolved
Hide resolved
❌ Gradle check result for e4a270a: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
d812134
to
addb332
Compare
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
Signed-off-by: Sandesh Kumar <[email protected]>
❌ Gradle check result for 2d034c8: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
@msfroh @jainankitk @sarthakaggarwal97 @bharath-techie Thanks for the comments and suggestions on PR. I have addressed those comments and polished up the PR. Please let me know if there are more comments. |
@@ -29,4 +29,12 @@ public SortedNumericStarTreeValuesIterator(DocIdSetIterator docIdSetIterator) { | |||
public long nextValue() throws IOException { | |||
return ((SortedNumericDocValues) docIdSetIterator).nextValue(); | |||
} | |||
|
|||
public int valuesCount() throws IOException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit : can we have 1-1 mapping , lets have the same name docValueCount
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are "star tree values", though, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to avoid docValue
within the method name.
We also didn't had 1-1 mapping in the parent class as well.
public int entryId() {
return docIdSetIterator.docID();
}
public int nextEntry() throws IOException {
return docIdSetIterator.nextDoc();
}
valuesCount()
looked kind of okay to me, but okay to rename otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad on not giving context . I mean we can have 'entryValueCount' going by that convention - the thing is we have getValueCount and getDocValueCount for sortedSetDocValues - so just valuesCount
will have issues.
/**
* Retrieves the number of unique ords for the current document. This must always be greater than
* zero. It is illegal to call this method after {@link #advanceExact(int)} returned {@code
* false}.
*/
public abstract int docValueCount();
/**
* Returns the number of unique values.
*
* @return number of unique values in this SortedDocValues. This is also equivalent to one plus
* the maximum ordinal.
*/
public abstract long getValueCount();
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes. LGTM
...in/java/org/opensearch/index/compositeindex/datacube/startree/utils/StarTreeQueryHelper.java
Show resolved
Hide resolved
if (!supportedDimensions.contains(field)) { | ||
return null; | ||
} | ||
long inputQueryVal = Long.parseLong(tq.value().toString()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sandeshkr419, what happens if you pass "6"
as your value to the TermQueryBuilder
in your integ test?
I'm pretty sure it will successfully create the TermQueryBuilder
and doToQuery
will convert it to a Lucene query correctly. (Technically, it won't create a TermQuery
, but rather a PointRangeQuery
over the range [6,6]
.)
@@ -29,4 +29,12 @@ public SortedNumericStarTreeValuesIterator(DocIdSetIterator docIdSetIterator) { | |||
public long nextValue() throws IOException { | |||
return ((SortedNumericDocValues) docIdSetIterator).nextValue(); | |||
} | |||
|
|||
public int valuesCount() throws IOException { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are "star tree values", though, right?
Signed-off-by: Sandesh Kumar <[email protected]>
❌ Gradle check result for bdabc51: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for bdabc51: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Disclaimer
These changes are built on top of unmerged/in-review indexing changes, Reviewers kindly ignore this commit while reviewing this change. When the depending changes are merged, will remove theDo not merge
from title, and addchngelog
to the PR - avoiding adding now to avoid unnecessary rebasing/conflicts.Description
For an index supporting star-tree composite index, this changes tries to achieve resolving a metric aggregation with/without a numeric terms query with the help of star-tree.
In present state, the PR capture changes for sum, max, min, avg, value-count aggregation.
Once the high level changes in sum aggregation are reviewed, will increment with other aggregations.Approach
A new StarTreeQuery is introduced which helps resolve to star-tree documents. This star-tree query is formed (if it can be) at the shard level, this is not done at coordinator level to avoid node to node transportation. Also, all the information is present at shard level and OpenSearch does majority of query rewrite at shard level itself. This star tree query is encapsulated in an OriginalOrStarTreeQuery which helps preserve the original query alongwith the new star tree query. This encapsulation is done so as to preserve both the queries and decision whether to use which query can be taken at a segment level.
High Level Operations (to make code reviewing simple):
TODO in this PR:
This PR depends on #14809, therefore the depending unmerged changes have been utilized for now in my private fork to discuss the changes in parallel.
Example query shape:
No query + Agg:
Original Response:
Star Tree Response:
Request:
Original Response:
Star Tree Flow Response:
Multi-aggs in a single request:
Star Tree Response:
Unsupported Metric Operation via star-tree:
Defaults to original code-flow (verified by hits reported):
Approach:
Related Issues
#15257
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.