[
https://issues.apache.org/jira/browse/BEAM-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805143#comment-16805143
]
Ismaël Mejía commented on BEAM-6324:
------------------------------------
You are right, this is error prone but a consequence of earlier API design
mistakes. We could add a validation that detects that if the user set the query
then the tablespace and the table name should be part of the query to fail
eagerly. Would you be up to work on that fix? I created BEAM-6940 feel free to
sel assign if you can help us to fix it and thanks for reporting.
Notice that the we need the keyspace and table to be explicit to find the token
ranges, otherwise we should extract that from the query and that's a way
trickier problem.
> CassandraIO.Read - Add the ability to provide a filter to the query
> -------------------------------------------------------------------
>
> Key: BEAM-6324
> URL: https://issues.apache.org/jira/browse/BEAM-6324
> Project: Beam
> Issue Type: Improvement
> Components: io-java-cassandra
> Reporter: Shahar Frank
> Assignee: Shahar Frank
> Priority: Major
> Labels: performance, pull-request-available, triaged
> Fix For: Not applicable
>
> Time Spent: 12h 50m
> Remaining Estimate: 0h
>
> CassandraIO.Read doesn't support using WHERE to filter the input at the
> source (In Cassandra) which might provide great performance boost.
> Already implemented by:
> https://github.com/apache/beam/pull/7340
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
