[
https://issues.apache.org/jira/browse/CASSANDRA-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989706#comment-14989706
]
Sylvain Lebresne commented on CASSANDRA-9543:
---------------------------------------------
bq. Which means you aren't able to test things under the same conditions you
application will be under.
I'm not convinced. Because with all do respect to stress, I doubt it's
currently expressive enough to allow you to simulate a real application
workload so precisely that a small difference in the java driver version will
somehow make think completely unreliable. But also because you're assuming
application will use a an alpha version of the 3.0 driver. What about users
that uses the driver version we currently ship with 2.2 so they get their
stress to behave like their application? You'd be screwing those people over.
Anyway, I'm unconvinced this is justification enough to make an exception in
our usual rule (of avoiding upgrades of dependencies in minor updates). The
fact that the 3.0 driver is currently only in alpha definitively doesn't help
the case for that matter.
> Integrate release 2.2 java driver
> ---------------------------------
>
> Key: CASSANDRA-9543
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9543
> Project: Cassandra
> Issue Type: Task
> Reporter: Robert Stupp
> Assignee: Jeremiah Jordan
> Fix For: 2.2.x
>
>
> Follow-up of CASSANDRA-9493.
> Hint: cleanup {{build.xml}} for commented out {{çassandra-driver-core}} maven
> dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
