True, but my concern is that you might see performance issues with a new
connection each time, especially if the same value(s) come in many times in
a row (i.e. choosing the same connection config). Having a small cache
might afford you some speedups.
Regards,
Matt
On Sun, Mar 10, 2024 at 9:17
I got through quite a bit of work to enable 4.x…
The 3.x pieces that were not backwards compatible is very edge use case and
could have been done slightly differently but with work around.
https://github.com/steven-matison/nifi/tree/nifi-10120-1
On Fri, Mar 15, 2024 at 2:30 PM Matt Burgess
Oops used the wrong email address so if there have been responses to the
Cassandra thread since mine I missed them, my bad!
On Fri, Mar 15, 2024 at 2:00 PM Matt Burgess wrote:
> I believe the CQL protocol is backwards compatible but the Java API is
> not. For example
I believe the CQL protocol is backwards compatible but the Java API is not.
For example "com.datastax.driver.core.Session" is now
"com.datastax.oss.driver.api.core.session.Session" and there is no more
"Cluster" class. Might be fairly trivial to fix though, if that's the path
of least resistance.
Matt
I dont know a ton about Cassandra but when I looked at client/driver notes
for 4+ it said it was compatible all the way back to 3.x. Not sure what
that means but it surely seems worth exploring. Also I dont know if the
4.x drivers get rid of the vulnerable bits.
Thanks
On Fri, Mar 15,
At the very least we should upgrade to Cassandra 3.11.6:
https://github.com/apache/cassandra/blob/cassandra-3.11.16/CHANGES.txt
On Fri, Mar 15, 2024 at 1:31 PM Matt Burgess wrote:
> If the community agrees to get rid of Cassandra 3 that'll save me effort
> on the refactor after I add Cassandra
If the community agrees to get rid of Cassandra 3 that'll save me effort on
the refactor after I add Cassandra 4 :) Otherwise those
vulnerabilities would only be in a "new" Cassandra 3 services NAR that
would not be included in the convenience binary.
On Fri, Mar 15, 2024 at 1:28 PM Joe Witt
Mike, Matt,
Happy to hear you both have active efforts or are interested in doing so.
Can you help me understand more specifically what that means for the
current set of components?
The CVE hits are concerning and long standing. Supporting Cassandra 3
implies the current set of dependencies
I'm actively working this, I pushed my branch up in case anyone wants to
take a look [1]. The idea is to abstract the Cassandra API "up a couple
levels" and provide implementations for Cassandra 3, 4, and eventually 5.
For JDBC-like interfaces this is a PITA because of the API (Statement,
That’s been on my todo list for a little while but things kept coming up. I
think I could get started on that now. Based on my initial research it appears
that scylla uses the exact same api as datastax so supporting both in a cql
bundle should theoretically be fairly easy.
Sent from my
10 matches
Mail list logo
