[
https://issues.apache.org/jira/browse/CASSANDRA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667352#comment-13667352
]
Aleksey Yeschenko commented on CASSANDRA-4450:
----------------------------------------------
Thanks.
In BatchStatement, not sure about picking the first ks/cf for the column specs.
I'd rather see surrogate ks/cf names here, like we do with [timestamp] and
[ttl] pseudocolumns - i.e. ks=[batch], cf=[batch].
nit?: maybe move everything but the validate() call in
Attributes.getTimeToLive() out of try/catch block?
> CQL3: Allow preparing the consistency level, timestamp and ttl
> --------------------------------------------------------------
>
> Key: CASSANDRA-4450
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4450
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: cql3
> Fix For: 2.0
>
>
> It could be useful to allow the preparation of the consitency level, the
> timestamp and the ttl. I.e. to allow:
> {noformat}
> UPDATE foo SET .. USING CONSISTENCY ? AND TIMESTAMP ? AND TTL ?
> {noformat}
> A slight concern is that when preparing a statement we return the names of
> the prepared variables, but none of timestamp, ttl and consistency are
> reserved names currently, so returning those as names could conflict with a
> column name. We can either:
> * make these reserved identifier (I have to add that I'm not a fan because at
> least for "timestamp", I think that's a potentially useful and common column
> name).
> * use some specific special character to indicate those are not column names,
> like returning "[timestamp]", "[ttl]", "[consistency]".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
