Provides support to increase developer productivity in Java when using Apache Cassandra. Uses familiar Spring concepts such as a template classes for core API usage and lightweight repository style data access.
ReactiveCassandraOperations provides methods accepting streams of entities Publisher<T> that are flatmapped to the according operations.
While this pattern is handy, it hides the aspect that Cassandra does not support bulk write operations other than batches. A batch resides in memory until its sent to Cassandra. We have a dedicated batch API and don't want to mix different approaches. Batches should require explicit opt-in.
We don't want to set expectations to support a streaming feature that isn't natively supported.
The repository API continues to accept Publisher<T> and adopt the store behavior on a best-effort basis
Mark Paluch opened DATACASS-474 and commented
ReactiveCassandraOperations
provides methods accepting streams of entitiesPublisher<T>
that are flatmapped to the according operations.While this pattern is handy, it hides the aspect that Cassandra does not support bulk write operations other than batches. A batch resides in memory until its sent to Cassandra. We have a dedicated batch API and don't want to mix different approaches. Batches should require explicit opt-in.
We don't want to set expectations to support a streaming feature that isn't natively supported. The repository API continues to accept
Publisher<T>
and adopt the store behavior on a best-effort basisReferenced from: pull request https://github.com/spring-projects/spring-data-cassandra/pull/110