That is cool but this still does not show / explain how it would look like
when it comes to dependencies needed for actually talking to storages like
s3.

Maybe I am missing something here and please explain when I am mistaken but
If I understand that correctly, for talking to s3 we would need to use a
library like this, right? (1). So that would be added among Cassandra
dependencies? Hence Cassandra starts to be biased against s3? Why s3? Every
time somebody comes up with a new remote storage support, that would be
added to classpath as well? How are these dependencies going to play with
each other and with Cassandra in general? Will all these storage
provider libraries for arbitrary clouds be even compatible with Cassandra
licence-wise?

I am sorry I keep repeating these questions but this part of that I just
don't get at all.

We can indeed add an API for this, sure sure, why not. But for people who
do not want to deal with this at all and just be OK with a FS mounted, why
would we block them doing that?

(1) https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-s3/pom.xml

On Wed, Mar 5, 2025 at 3:28 PM Mick Semb Wever <m...@apache.org> wrote:

>    .
>
>
> It’s not an area where I can currently dedicate engineering effort. But if
>> others are interested in contributing a feature like this, I’d see it as
>> valuable for the project and would be happy to collaborate on
>> design/architecture/goals.
>>
>
>
> Jake mentioned 17 months ago a custom FileSystemProvider we could offer.
>
> None of us at DataStax has gotten around to providing that, but to quickly
> throw something over the wall this is it:
>
> https://github.com/datastax/cassandra/blob/main/src/java/org/apache/cassandra/io/storage/StorageProvider.java
>
>   (with a few friend classes under o.a.c.io.util)
>
> We then have a RemoteStorageProvider, private in another repo, that
> implements that and also provides the RemoteFileSystemProvider that Jake
> refers to.
>
> Hopefully that's a start to get people thinking about CEP level details,
> while we get a cleaned abstract of RemoteStorageProvider and friends to
> offer.
>
>

Reply via email to