[
https://issues.apache.org/jira/browse/CASSANDRA-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577882#comment-17577882
]
Andres de la Peña commented on CASSANDRA-8877:
----------------------------------------------
Thanks for the review.
[~blerer] has pointed out that selectors are only serialized when they are part
of a {{GROUP BY}} clause, and we don't support {{writetime}}, {{maxwritetime}}
nor {{ttl}} on the {{GROUP BY}} clause. So we shouldn't have any problems in
mixed clusters because everything happens on the coordinator. Thus, I have
removed the rules forbidding using these functions on mixed clusters and
updated the upgrade test and the {{NEWS.txt}} entry.
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1739]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1979/workflows/a47241a2-6d5d-4dfa-b67c-8e3af48931ca]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1979/workflows/936319b5-e1a1-4e9e-9318-817d5ef90d86]|
> Ability to read the TTL and WRITE TIME of an element in a collection
> --------------------------------------------------------------------
>
> Key: CASSANDRA-8877
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8877
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/CQL
> Reporter: Drew Kutcharian
> Assignee: Andres de la Peña
> Priority: Low
> Fix For: 4.x
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Currently it's possible to set the TTL and WRITE TIME of an element in a
> collection using CQL, but there is no way to read them back.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
