[
https://issues.apache.org/jira/browse/CASSANDRA-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738756#comment-17738756
]
Andres de la Peña commented on CASSANDRA-18345:
-----------------------------------------------
Here are some runs based on {{cep-7-sai}} for reference:
*
[https://app.circleci.com/pipelines/github/adelapena/cassandra/2994/workflows/520107d4-6890-45d4-bf15-22cfec2e01f5]
*
[https://app.circleci.com/pipelines/github/adelapena/cassandra/2994/workflows/92cb9830-3ad0-42bc-9a5b-931108934360]
J17 looks more or less the same mess. I guess it will improve a bit with
rebase, but even trunk has quite a bunch of failures for j17, see this run for
small PR over current trunk:
[https://app.circleci.com/pipelines/github/adelapena/cassandra/2996/workflows/b6e8904f-6fbd-43b6-83af-3167c8e2040b/jobs/55699/tests]
I guess we can merge based on the j11 results?
> Enable streaming SAI components as part of repair
> -------------------------------------------------
>
> Key: CASSANDRA-18345
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18345
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/2i Index
> Reporter: Mike Adamson
> Assignee: Piotr Kolaczkowski
> Priority: Normal
> Labels: SAI
> Fix For: 5.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> SAI registers it's components with the SSTable descriptor expecting them to
> form part of the SSTable lifecycle, including streaming. This is not the case.
> The current SSTable format in Cassandra uses a fixed set of components
> (Components.STREAMING_COMPONENTS) when streaming SSTables. This needs to
> change to use the set of components that are registered with a specific
> SSTable by calls to SSTable.registerComponents.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
