[
https://issues.apache.org/jira/browse/CASSANALYTICS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANALYTICS-81:
-----------------------------------
Fix Version/s: 0.2
Source Control Link:
https://github.com/apache/cassandra-analytics/commit/2210e8be93b162bb201ea0b89131ea555bd4e7e1
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Unique restoreJobId per write target
> -------------------------------------
>
> Key: CASSANALYTICS-81
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-81
> Project: Apache Cassandra Analytics
> Issue Type: Bug
> Components: Writer
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
> Fix For: 0.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In CASSANALYTICS-75, coordinated write can run against the different DCs of
> the same cluster. However, each restore job will be created using the same
> job ID, which fails the job due to restore job ID conflict. This patch adds
> the fix by generating unique ID per write target.
--
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
