[jira] [Commented] (BEAM-11399) Cassandra sessions should be (cached) reused per keyspace per host

["Danny McCormick (Jira)" <ji...@apache.org>]

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

Danny McCormick commented on BEAM-11399:
----------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/20570

> Cassandra sessions should be (cached) reused per keyspace per host
> ------------------------------------------------------------------
>
>                 Key: BEAM-11399
>                 URL: https://issues.apache.org/jira/browse/BEAM-11399
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-cassandra
>            Reporter: Manoj Kumar Singh
>            Priority: P3
>
> According to the Datastax document for session "{color:#4c9aff}*As a given session can only be "logged" into one keyspace at a time (where the "logged" keyspace is the one used by queries that don't explicitly use a fully qualified table name), it can make sense to create one session per keyspace used. This is however not necessary when querying multiple keyspaces since it is always possible to use a single session with fully qualified table names in queries.*{color}"(source: [https://docs.datastax.com/en/drivers/java/3.0/com/datastax/driver/core/Session.html).] 
> The session fields in Mutator<T> class should be cached and reused for a keyspace and host. 
> [https://github.com/apache/beam/blob/master/sdks/java/io/cassandra/src/main/java/org/apache/beam/sdk/io/cassandra/CassandraIO.java#L1225] 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)