[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Fix Version/s: 5.0.5
5.1
(was: 5.x)
(was: 5.0.x)
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.5, 5.1
>
> Attachments: ci_summary-1.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar.gz,
> test-histogram_with_changes.html, test-histogram_without.html
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Source Control Link:
https://github.com/apache/cassandra/commit/7a8335c2739c207b77e90c05897285b3cbaba166
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: ci_summary-1.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar.gz,
> test-histogram_with_changes.html, test-histogram_without.html
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Attachment: ci_summary-1.html
result_details.tar-1.gz
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: ci_summary-1.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar.gz,
> test-histogram_with_changes.html, test-histogram_without.html
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-20191:
--
Status: Ready to Commit (was: Review In Progress)
+1
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: ci_summary.html, result_details.tar.gz,
> test-histogram_with_changes.html, test-histogram_without.html
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-20191:
--
Reviewers: Caleb Rackliffe, David Capwell (was: Caleb Rackliffe)
Status: Review In Progress (was: Needs Committer)
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: ci_summary.html, result_details.tar.gz,
> test-histogram_with_changes.html, test-histogram_without.html
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Attachment: ci_summary.html
result_details.tar.gz
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: ci_summary.html, result_details.tar.gz,
> test-histogram_with_changes.html, test-histogram_without.html
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Status: Needs Committer (was: Review In Progress)
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: test-histogram_with_changes.html,
> test-histogram_without.html
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Status: Review In Progress (was: Patch Available)
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: test-histogram_with_changes.html,
> test-histogram_without.html
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Test and Documentation Plan: local perf tests, expanded testing around
clustering key restrictions and paging
Status: Patch Available (was: In Progress)
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: test-histogram_with_changes.html,
> test-histogram_without.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil Ramchandra Pawar updated CASSANDRA-20191:
---
Attachment: test-histogram_with_changes.html
test-histogram_without.html
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Attachments: test-histogram_with_changes.html,
> test-histogram_without.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Reviewers: Caleb Rackliffe
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Assignee: Sunil Ramchandra Pawar
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-20191) Optimize initial skipping logic for SAI queries on large partitions
[
https://issues.apache.org/jira/browse/CASSANDRA-20191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-20191:
Change Category: Performance
Complexity: Normal
Component/s: Feature/SAI
Fix Version/s: 5.0.x
5.x
Status: Open (was: Triage Needed)
> Optimize initial skipping logic for SAI queries on large partitions
> ---
>
> Key: CASSANDRA-20191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20191
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
>Reporter: Caleb Rackliffe
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> In {{StorageAttachedIndexSearcher.ResultRetriever}}, we skip all postings
> lists produced by queries on individual column indexes to the first partition
> in the provided {{DataRanges}}. This is an obvious and useful step, but for
> queries on large partitions, it might not go as far as it could. If paging or
> user restrictions on the clustering key space are in play, it is probably
> suboptimal to not even attempt to skip the postings, which are
> row-addressable, to the first row after the clustering prefix in the (likely
> single) {{DataRange}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
