[
https://issues.apache.org/jira/browse/CASSANDRA-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-4217:
----------------------------------------
Attachment: 4217.txt
I'll agree with Jonathan that general functions support is more work than I
want to put here. Nor is it my top priority either to be honest (I don't see
that as a necessity for a final version of CQL 3.0.0).
Anyway, attaching patch for this. For the timestamp, I've picked writetime(x)
currently, though thinking of it now I realize it is slightly incoherent with
the fact that we use 'USING TIMESTAMP' to specify it at insert time, so maybe
timestampof is better. Anyway, that will be trivial to change to whatever we
settle for.
> Easy access to column timestamps (and maybe ttl) during queries
> ---------------------------------------------------------------
>
> Key: CASSANDRA-4217
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4217
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
> Affects Versions: 1.1.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.1.1
>
> Attachments: 4217.txt
>
>
> It would be interesting to allow accessing the timestamp/ttl of a column
> though some syntax like
> {noformat}
> SELECT key, value, timestamp(value) FROM foo;
> {noformat}
> and the same for ttl.
> I'll note that currently timestamp and ttl are returned in the resultset
> because it includes thrift Column object, but adding such syntax would make
> our future protocol potentially simpler as we wouldn't then have to care
> about timestamps explicitely (and more compact in general as we would only
> return timestamps when asked)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
