[
https://issues.apache.org/jira/browse/CASSANALYTICS-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004373#comment-18004373
]
Stefan Miklosovic commented on CASSANALYTICS-73:
------------------------------------------------
Hi [~liucao] , it is great you are involved in doing what you have described.
What I would like to see is that the feature you talk about would be purely
additive to the current implementations. What I mean by that is that the
behaviour from user's point of view should be the very same. I am already using
LocalDataLayer as well as CassandraDataLayer in other projects where I just
switch between data layers to do further logic, so I expect that the same would
be done about S3CassandraDataLayer if I want to read InternalRows from S3
directly. This would enable more use cases for external tools not necessarily
depending on Spark runtime.
> Simplify SidecarTableSizeProvider
> ---------------------------------
>
> Key: CASSANALYTICS-73
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-73
> Project: Apache Cassandra Analytics
> Issue Type: Improvement
> Components: Reader
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
> Fix For: 1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I have a small suggestion to simplify the recently added
> {{SidecarTableSizeProvider}} (added in CASSANALYTICS-36). This change will
> pass the port information directly without having to pass the entire client
> configuration object to the constructor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
