Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 27 May 2013 07:24:20 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12599435.1342691450466.24844.1369639460951@arcas>
In-Reply-To: <JIRA.12599435.1342691450466@arcas>
References: <JIRA.12599435.1342691450466@arcas>
Subject: [jira] [Commented] (CASSANDRA-4450) CQL3: Allow preparing the
 consistency level, timestamp and ttl
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667515#comment-13667515 ] 

Sylvain Lebresne commented on CASSANDRA-4450:
---------------------------------------------

bq. I'd rather see surrogate ks/cf names here

I hesitated. But yeah, you're probably right that it's better. I've pushed an additional commit on the branch with that.
                
> 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