[
https://issues.apache.org/jira/browse/CASSANDRA-18398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718487#comment-17718487
]
Branimir Lambov commented on CASSANDRA-18398:
---------------------------------------------
bq. This is more venting than constructive feedback, but there are certainly
parts of this patch that would be simpler without early open in play. Are there
any active proposals to remove it for 5.0?
At this point there is little hope to achieve what early open does without it.
bq. RE checksumming on the partition/row index files, would a reasonable path
forward for now be to spin off a separate Jira where we look into at least
verifying integrity on startup (and streaming?), sort of like what we do w/
DIGEST?
Let's make it a separate JIRA; this can be done post 5.0. If it is a startup
check (which may have the side effect of warming up the cache for indexes), the
CRCs can be in a different file. If not, they need to be stored with the page
to avoid costly additional page fetches.
> CEP-25: Trie-indexed SSTable format
> -----------------------------------
>
> Key: CASSANDRA-18398
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18398
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/SSTable
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 27h 10m
> Remaining Estimate: 0h
>
> Implementation of Big Trie-Indexed (BTI) SSTable format, per
> [CEP-25|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format].
--
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
