[CASSANDRA-19325] [Analytics] Fix range split and use open-closed range notation consistently

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: NA
• Component/s: Analytics Library
• Bug Category: Code
• Severity: Normal
• Complexity: Normal
• Discovered By: Code Inspection
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra-analytics/commit/b5ba5fad4df490d1b7d47889361db910589409b8

Test and Documentation Plan

unit; ci

• Assignee: Yifan Cai
• Reporter: Yifan Cai

Authors

Yifan Cai

Reviewers

Arjun Ashok, Francisco Guerrero

• Created: 25/Jan/24 01:35
• Updated: 30/Jan/24 20:08
• Resolved: 30/Jan/24 20:08

Description

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.

Issue Links

• links to: GitHub Pull Request #34