[ 
https://issues.apache.org/jira/browse/CASSANALYTICS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANALYTICS-88:
-------------------------------------------
    Description: 
The latest patch which introduces bridge modules for Cassandra 5 does not work 
when writing to Cassandra 5 clusters with storage_compatibility_mode = 
CASSANDRA_4 (which is default), *however it does work when 
storage_compatibility_mode is either NONE or UPGRADING*. The write job itself 
indicates that it's successful but the data does not exist on the cluster. 

To replicate, use the latest build of cassandra-analytics and trigger a write 
job against a Cassandra 5.0.5 cluster with storage_compatibility_mode: 
CASSANDRA_4

  was:
The latest patch which introduces bridge modules for Cassandra 5 does not work 
when writing to Cassandra 5 clusters with storage_compatibility_mode = 
CASSANDRA_4, *however it does work when storage_compatibility_mode is either 
NONE or UPGRADING*. The write job itself indicates that it's successful but the 
data does not exist on the cluster. 

To replicate, use the latest build of cassandra-analytics and trigger a write 
job against a Cassandra 5.0.5 cluster with storage_compatibility_mode: 
CASSANDRA_4


> Cassandra bulk writing fails when using Cassandra 5 with 
> storage_compatibility_mode = CASSANDRA_4
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANALYTICS-88
>                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-88
>             Project: Apache Cassandra Analytics
>          Issue Type: Bug
>          Components: Writer
>            Reporter: Andrew Johnson
>            Priority: Normal
>
> The latest patch which introduces bridge modules for Cassandra 5 does not 
> work when writing to Cassandra 5 clusters with storage_compatibility_mode = 
> CASSANDRA_4 (which is default), *however it does work when 
> storage_compatibility_mode is either NONE or UPGRADING*. The write job itself 
> indicates that it's successful but the data does not exist on the cluster. 
> To replicate, use the latest build of cassandra-analytics and trigger a write 
> job against a Cassandra 5.0.5 cluster with storage_compatibility_mode: 
> CASSANDRA_4



--
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