[ 
https://issues.apache.org/jira/browse/FLINK-19930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408346#comment-17408346
 ] 

Arseniy Tashoyan commented on FLINK-19930:
------------------------------------------

It would be convenient to configure the settings of flink-connector-cassandra 
via standard Flink configuration file: flink-conf.yaml.
Currently there is only API to configure programmatically: 
https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/connectors/datastream/cassandra/#configurations
This means that users need to propagate Flink-specific settings to the 
application level settings.

For example, in order to configure the maximum number of concurrent requests, 
user needs to
- Make an application-level configuration parameter 
"flink-cassandra-connector-max-concurrent-requests"
- Propagate this parameter to the code that creates and configures 
CassandraSink: setMaxConcurrentRequests(...)
It would be better to set this parameter in the configuration file 
flink-conf.yaml, as any other Flink parameter:

cassandra.connector.max.concurrent.requests = 100
cassandra.connector.max.concurrent.requests.timeout = "1 min"

We have to make a difference between the flink-connector-cassandra settings and 
the Cassandra Java driver settings. The settings for the Cassandra Java driver 
are configured via Typesafe Config: 
https://github.com/datastax/java-driver/tree/4.x/manual/core/configuration - we 
should not duplicate those settings in the Flink config file.

> Upgrade cassandra-driver-core to 4.X
> ------------------------------------
>
>                 Key: FLINK-19930
>                 URL: https://issues.apache.org/jira/browse/FLINK-19930
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Cassandra
>            Reporter: Chesnay Schepler
>            Priority: Minor
>              Labels: auto-deprioritized-major
>
> Our current cassandra driver version is 3.0.0, which by now is 4 years old.
> We may want to investigate switching to the re-branded 
> com.datastax.oss:java-driver-core 4.9.0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to