[CASSANDRA-19716] [Analytics] Invalid mapping when timestamp is used as a partition key during bulk writes

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: NA
• Component/s: Analytics Library
• Bug Category: Correctness - Unrecoverable Corruption / Loss
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra-analytics/commit/8dce35f1cb3c204be669548ee286055b12e67fe9

Test and Documentation Plan

Added tests that cover all the mappings for the PK.

• Assignee: Francisco Guerrero
• Reporter: Francisco Guerrero

Authors

Francisco Guerrero

Reviewers

Francisco Guerrero, Yifan Cai

• Created: 17/Jun/24 23:43
• Updated: 20/Jun/24 21:45
• Resolved: 20/Jun/24 21:45

Description

When Cassandra has a table with a schema that includes a timestamp PK, i.e CREATE TABLE (a timestamp, b text, c text, PRIMARY KEY (a)), bulk writer maps the timestamp to a LongType. This causes the bulk writer job to produce a class cast exception when building the composite key during repartition and sorting of data in the spark job

Issue Links

• links to: GitHub Pull Request #60