[
https://issues.apache.org/jira/browse/CASSANDRA-19325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-19325:
----------------------------------
Fix Version/s: NA
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra-analytics/commit/b5ba5fad4df490d1b7d47889361db910589409b8
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> [Analytics] Fix range split and use open-closed range notation consistently
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-19325
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19325
> Project: Cassandra
> Issue Type: Bug
> Components: Analytics Library
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
> Fix For: NA
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> The ranges used in the analytics library do not have the consistent notation
> with Cassandra. The analytics library, as in the cassandra ecosystem, should
> use the open-closed range notation consistently, to avoid potential bugs in
> implementation.
> Besides that, during write process, the split sub-ranges are unordered. It
> does not seem to affect correctness, but can be confusing.
--
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
