-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CASSANDRA-18078 trunk: Remove maxwritetime function #2032
base: trunk
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments, but it looks good to me
CHANGES.txt
Outdated
@@ -80,7 +80,6 @@ | |||
* Add guardrail to allow disabling of SimpleStrategy (CASSANDRA-17647) | |||
* Change default directory permission to 750 in packaging (CASSANDRA-17470) | |||
* Adding support for TLS client authentication for internode communication (CASSANDRA-17513) | |||
* Add new CQL function maxWritetime (CASSANDRA-17425) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to add a new line mentioning the removal of the CQL function instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure. If we take this file as a record of code changes, it makes sense to keep the removed line and add a new one about the removal of the function. If we take this file as a list of what is different from previous release, then having both entries only adds noise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My intuition is that CHANGES is append-only.. Also quoting from https://cassandra.apache.org/_/development/index.html
Please note that only user-impacting items should be listed in CHANGES.txt.
Removing a function is user impacting.
@@ -73,25 +74,23 @@ public void testWritetimeOrTTLDuringUpgrade() throws Throwable | |||
|
|||
private void assertPre42Behaviour(ICoordinator coordinator) | |||
{ | |||
// regular column, supported except for maxwritetime | |||
// regular column, supported except for max writetime |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to update this comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
Assertions.assertThat((Integer) coordinator.execute(withKeyspace("SELECT ttl(v) FROM %s.t"), ALL)[0][0]) | ||
.isLessThanOrEqualTo(2000).isGreaterThan(2000 - 300); // margin of error of 5 minutes since TTLs decrease | ||
|
||
// frozen collection, supported except for maxwritetime | ||
// frozen collection, supported except for max writetime |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to update this comment as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
ce139d0
to
f8cfdfc
Compare
4b52b9f
to
7fbb3ac
Compare
@Override | ||
public ByteBuffer execute(ProtocolVersion protocolVersion, List<ByteBuffer> parameters) | ||
{ | ||
return parameters.get(0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this does not work in current 5.0 anymore.
Thanks for sending a pull request! Here are some tips if you're new here:
Commit messages should follow the following format:
The Cassandra Jira