[
https://issues.apache.org/jira/browse/BEAM-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531929#comment-17531929
]
vincent marquez commented on BEAM-12844:
----------------------------------------
[~kenn] [~bumblebee] Apologies I should have been more clear.
??One of the biggest shortcoming of apache beam cassandra IO is that it does
not provide any api for doing concurrent queries based on primary keys. For
Example: We have 1000 keys. So instead of doing a full scan across
scylla/cassandra system table to find out token ranges??
This is what I was responding to. readAll now allows for specifying individual
keys to query instead of doing a table scan.
SSL is still not supported I believe.
> Cassandra IO Does not work with ssl enabled Cassandra/Cosmos DB on Azure
> ------------------------------------------------------------------------
>
> Key: BEAM-12844
> URL: https://issues.apache.org/jira/browse/BEAM-12844
> Project: Beam
> Issue Type: New Feature
> Components: io-java-cassandra
> Affects Versions: 2.32.0
> Environment: Azure AKS.
> Reporter: Jay Ghiya
> Assignee: vincent marquez
> Priority: P3
> Labels: cloud, feature-request
>
> Not Able to use cassandra Io with ssl enabled cosmos db or cassandra as
> cassandra IO does not expose cluster builder options. This looks like a basic
> feature set. It would be great to resolve this as early as possible to avoid
> organizations rejecting it due to missing ssl feature.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
