You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Fabien Rousseau (JIRA)" <ji...@apache.org> on 2018/11/16 12:53:00 UTC

[jira] [Updated] (BEAM-6078) CassandraIO.read() should use builder's keyspace by default

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

Fabien Rousseau updated BEAM-6078:
----------------------------------
    Description: 
Currently for CassandraIO.read(), it connects to the cluster without using the keyspace specified in the builder. (For writes it already does this).

This would allow to not specify the keyspace in the mapped object (it can be useful if the object is used in more than one keyspace).

I'll provide a PR shortly

  was:
Currently for CassandraIO.reads(), it connects to the cluster without using the keyspace specified in the builder. (For writes it already does this).

This would allow to not specify the keyspace in the mapped object (it can be useful if the object is used in more than one keyspace).

I'll provide a PR shortly


> CassandraIO.read() should use builder's keyspace by default
> -----------------------------------------------------------
>
>                 Key: BEAM-6078
>                 URL: https://issues.apache.org/jira/browse/BEAM-6078
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-cassandra
>            Reporter: Fabien Rousseau
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>
> Currently for CassandraIO.read(), it connects to the cluster without using the keyspace specified in the builder. (For writes it already does this).
> This would allow to not specify the keyspace in the mapped object (it can be useful if the object is used in more than one keyspace).
> I'll provide a PR shortly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)