[
https://issues.apache.org/jira/browse/CASSANDRA-16613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16613:
--------------------------------------------
Description:
While working on CASSANDRA-16567, [~adelapena] observed that
_ProtocolVersion.V4_ is used in _ViewTest_.
I decided to do a quick grep and observed a list of places where we still refer
to V4 and it seems at least in many of the tests that was left not
intentionally.
This ticket is to verify the usage of _ProtocolVersion.V4_ in the codebase and
bump it to V5 or default version, similar to what was done in CASSANDRA-16567,
wherever there is a need.
was:
While working on CASSANDRA-16567, [~adelapena] observed that ProtocolVersion.V4
is used in _ViewTest_.
I decided to do a quick grep and observed a list of places where we still refer
to V4 and it seems at least in many of the tests that was left not
intentionally.
This ticket is to verify the usage of _ProtocolVersion.V4_ in the codebase and
bump it to V5 or default version, similar to what was done in CASSANDRA-16567
> ProtocolVersion.V4 is still used in places in the code
> ------------------------------------------------------
>
> Key: CASSANDRA-16613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16613
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
>
> While working on CASSANDRA-16567, [~adelapena] observed that
> _ProtocolVersion.V4_ is used in _ViewTest_.
> I decided to do a quick grep and observed a list of places where we still
> refer to V4 and it seems at least in many of the tests that was left not
> intentionally.
> This ticket is to verify the usage of _ProtocolVersion.V4_ in the codebase
> and bump it to V5 or default version, similar to what was done in
> CASSANDRA-16567, wherever there is a need.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
