-
Notifications
You must be signed in to change notification settings - Fork 33
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
support shard level split on read path #402
Conversation
Signed-off-by: Peng Huo <[email protected]>
Signed-off-by: Peng Huo <[email protected]>
Signed-off-by: Peng Huo <[email protected]>
Signed-off-by: Peng Huo <[email protected]>
Signed-off-by: Peng Huo <[email protected]>
* @param query DSL query. DSL query is null means match_all | ||
* @return {@link FlintReader}. | ||
*/ | ||
FlintReader createReader(String indexName, String shardId, String query); |
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.
Is shardId
concept binding to FlintOpenSearchClient
implementation or generic?
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.
bind to OpenSearch
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.
We can abstract this task/split info later.
* @param metadata | ||
* Metadata of the table. | ||
*/ | ||
case class OpenSearchTable(tableName: String, metadata: Map[String, FlintMetadata]) { |
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.
Is using FlintMetadata
temporary for only fetching index setting? Or is there hard dependency between OS table and Flint index in future?
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.
only for index setting and mapping, not binding to real index
Description
Test
preference:_shard:
paramaters.Benchmark
Single Index with 5 shards
The table below presents the p90 query latency results for both the partitioned and non-partitioned test cases. Across all queries, the results with partitioning show significantly lower times compared to the non-partitioned results.
logs-181998
logs-181998
WHERE status <> 0;logs-181998
;logs-181998
;@timestamp
), MAX(@timestamp
) FROM dev.default.logs-181998
;Multiple Indices, each index has 5 shards
The table below presents the p90 query latency results for both the partitioned and non-partitioned test cases when query index wildcard. Across all queries, the results with partitioning show significantly lower times compared to the non-partitioned results.
Issues Resolved
#396
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.