[
https://issues.apache.org/jira/browse/CASSANDRA-18058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651421#comment-17651421
]
Caleb Rackliffe commented on CASSANDRA-18058:
---------------------------------------------
[~mike_tr_adamson] [~adelapena] One thing we might want to resolve is whether
we think there's enough duplication between the {{IndexQuerySupport}}
(hand-crafted, covers stages of the write path, paging, fetch size, etc.) and
{{IndexingTypeSupport}} (randomized) frameworks that we can remove the former
entirely, or perhaps try to migrate enough to {{IndexingTypeSupport}} that we
can ditch {{IndexQuerySupport}}. They both try to cover all the relevant
indexable data types, and should be able to query data as it moves through the
write path from memory to disk, but they validate very differently. (IIRC, one
validates against equivalent filtering queries, while the other validates
against the randomly generated model.)
WDYT?
> In-memory index and query path
> ------------------------------
>
> Key: CASSANDRA-18058
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18058
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/SAI
> Reporter: Mike Adamson
> Assignee: Mike Adamson
> Priority: Normal
> Fix For: 5.x
>
>
> An in-memory index using the in-memory trie structure introduced with
> CASSANDRA-17240 along with a query path implementation to perform index
> queries from the in-memory index.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
