You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yifan Cai (Jira)" <ji...@apache.org> on 2024/09/10 21:36:00 UTC

[jira] [Assigned] (CASSANDRA-19815) [Analytics] Decouple Cassandra types from Spark types so Cassandra types can be used independently from Spark

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

Yifan Cai reassigned CASSANDRA-19815:
-------------------------------------

    Assignee: James Berragan

> [Analytics] Decouple Cassandra types from Spark types so Cassandra types can be used independently from Spark
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19815
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19815
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Analytics Library
>            Reporter: James Berragan
>            Assignee: James Berragan
>            Priority: Normal
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> The Cassandra types and Spark types are tightly coupled in the same classes, making it difficult to deserialize Cassandra types without pulling in Spark as a dependency, We can split out the Spark types into a separate module by introducing a new TypeConverter that maps Cassandra types to Spark types. This enables use of the Cassandra types without pulling in Spark and also opens the possibility of other TypeConverters in the future beyond Spark.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org