[
https://issues.apache.org/jira/browse/FLINK-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608662#comment-15608662
]
ASF GitHub Bot commented on FLINK-4497:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2633
Look pretty good.
I think it would be good to try to make the Cassandra Module to the user
Scala independent. That way, we don't introduce a hard requirement for Scala
versioning and make this Scala version independent as soon as Flink's runtime
is Scala Version independent.
We can do that the following way:
- Set the Scala dependency to "provided". Flink pulls Scala anyways,
Scala users have Scala anyways always as a dependency. Users that use Scala
from Java can always add an additional Scala dependency in their project.
- Add the Scala library as a test dependency
- Drop the Scala compiler plugin
- Use a case class for the tests that comes in the Scala library (such as
Tuple2)
- Migrate the test to Java - the sink class is in Java anyways
What do you think about that?
> Add support for Scala tuples and case classes to Cassandra sink
> ---------------------------------------------------------------
>
> Key: FLINK-4497
> URL: https://issues.apache.org/jira/browse/FLINK-4497
> Project: Flink
> Issue Type: Improvement
> Components: Cassandra Connector
> Affects Versions: 1.1.0
> Reporter: Elias Levy
> Assignee: Chesnay Schepler
>
> The new Cassandra sink only supports streams of Flink Java tuples and Java
> POJOs that have been annotated for use by Datastax Mapper. The sink should
> be extended to support Scala types and case classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
