[ https://issues.apache.org/jira/browse/CASSANDRA-18166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever updated CASSANDRA-18166: ------------------------------------------- Fix Version/s: 5.0-beta1 5.0 5.1 (was: 5.0-beta) Source Control Link: https://github.com/apache/cassandra/commit/0e42b77c9735d1124fe0a5766447f29c891cdb5b Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as https://github.com/apache/cassandra/commit/0e42b77c9735d1124fe0a5766447f29c891cdb5b > Improve the code model around IndexContext > ------------------------------------------ > > Key: CASSANDRA-18166 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18166 > Project: Cassandra > Issue Type: Improvement > Components: Feature/SAI > Reporter: Mike Adamson > Assignee: Mike Adamson > Priority: Normal > Labels: SAI > Fix For: 5.0-beta1, 5.0, 5.1 > > Time Spent: 8h 50m > Remaining Estimate: 0h > > We currently have a situation where we need to create an IndexContext that is > for a non-indexed column and therefore is never going to be used for indexing > or searching. This results in the IndexContext having to check for this at > points in the code with assertions. The reason for this that, even when the > column is non-indexed, we need to have information about the column for the > purpose of post-filtering. > It would make sense to split out the column / index information needed for > filtering from the indexing / searching requirements such that we could avoid > unnecessary assertions in the code. -- 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