[
https://issues.apache.org/jira/browse/BEAM-12844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412328#comment-17412328
]
Jay Ghiya commented on BEAM-12844:
----------------------------------
Hi [~kenn] - Couple of things. So we use beam heavily as part of our batch
pipelines. 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, we got atleast 3x low
latency while using our own modified version of cassandra IO.
So Looks like both of them should be provided by cassandra IO.
* When User has primary keys
* When User does not have primary keys
We were planning to merge this ssl change in that modified cassandra io and
then make it open source. We already discussed this with scylla team and they
see a definite value in the modified version. So would want your
validation/review/support on making that cassandra IO merge with existing one.
Will that be feasible?
> 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
> Priority: P2
> 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.3.4#803005)
