[ 
https://issues.apache.org/jira/browse/CASSANALYTICS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024272#comment-18024272
 ] 

Lukasz Antoniak edited comment on CASSANALYTICS-27 at 10/3/25 3:03 PM:
-----------------------------------------------------------------------

CI link: 
[https://app.circleci.com/pipelines/github/lukasz-antoniak/cassandra-analytics/169/workflows/cb9273e6-bc0d-4199-9685-8b304b88fc28]

!image-2025-10-03-17-02-46-311.png|width=836,height=401!


was (Author: lukasz.antoniak):
CI link: 
[https://app.circleci.com/pipelines/github/lukasz-antoniak/cassandra-analytics/165/workflows/bcadea2d-ec87-408e-9654-e696ee3df3c0]

!image-2025-10-02-15-17-23-723.png|width=1006,height=426!

> Support for Trie-Indexed SSTables (BtiFormat)
> ---------------------------------------------
>
>                 Key: CASSANALYTICS-27
>                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-27
>             Project: Apache Cassandra Analytics
>          Issue Type: Task
>          Components: Bridge, Reader, Writer
>            Reporter: Doug Rohrer
>            Assignee: Lukasz Antoniak
>            Priority: Normal
>             Fix For: 1.0
>
>         Attachments: image-2025-10-02-15-17-23-723.png, 
> image-2025-10-03-17-02-46-311.png
>
>          Time Spent: 8h
>  Remaining Estimate: 0h
>
> Writer needs to support writing BTI formats (which will require a small 
> change in {{CQLSSTableWriter}} to support choosing a format). Then we'll need 
> to query the cluster via Sidecar to figure out which kind of SSTable it wants 
> and use the correct format.
> Reader needs to be able to read BTI format SSTables, which is likely a larger 
> effort and needs some additional analysis and development, and may require 
> some changes to the Cassandra-side code as well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to