Closed gilcesarf closed 4 years ago
Revisiting tests found something wrong.... Will take a look and post news soon
Actually everything is fine. I misinterpreted some output logs from tests. In fact, what I have seen are some errors during protocol negotiation between datastax driver and in memory cassandra. Since tests uses an old version of cassandra which supports only v3 protocol, the driver first try v4 and fail, reporting errors. After that retries with v3 protocol which succeeds and all tests go fine.
Upgraded to storm 1.0.2 and cassandra datastax driver 3.1.3. All tests reported OK.
The main changes were on package names imported. A few was moving from MockTridentTuple to TridentTupleView within some of test classes