It would be nice for that message (and there is one more like it in the
driver) to say something more specific about how/where exactly to "report"
the situation. I mean, should users file Jira tickets for those two
scenarios or simply email to the Java (or other driver) email lists? The
message sho
OK. Thanks.
On Tue, Mar 22, 2016 at 12:56 PM Alex Popescu wrote:
> Hi Thunder,
>
> This would be better sent to the Java mailing list
> https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user.
> A quick search revealed https://datastax-oss.atlassian.net/browse/JAVA-603
> whi
Hi Thunder,
This would be better sent to the Java mailing list
https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user.
A quick search revealed https://datastax-oss.atlassian.net/browse/JAVA-603
which seem to match the Cassandra/DataStax community version but not the
driver v
Hi guys,
So, quick background, we are using Outworkers (previously WebSudos) Phantom
v 1.22.0 Which appears to be using DataStax driver 3.0.0. We are running
scala 2.10 inside Samza on Yarn (CDH 5.4.4) with Oracle JDK 8.
This is all pointing at a 3 node dev cluster of DataStax Community v 2.1.13