Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 21 Sep 2013 02:30:51 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12609594.1348865524668.172541.1379730651875@arcas>
In-Reply-To: <JIRA.12609594.1348865524668@arcas>
References: <JIRA.12609594.1348865524668@arcas>
Subject: [jira] [Commented] (CASSANDRA-4736) Cassandra should expose a
 native existence check API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-4736:
-------------------------------------------

My point is that the performance difference between {{SELECT foo}} and {{SELECT exists(foo)}} is small, unless foo is a blob.
                
> Cassandra should expose a native existence check API
> ----------------------------------------------------
>
>                 Key: CASSANDRA-4736
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4736
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sankalp kohli
>            Priority: Minor
>              Labels: features
>
> Currently Cassandra does not have an existence check API. Because of this, data needs to be read and thats how you know whether data is present or not. 
> This is not optimal because one replica needs to provide data. Instead a new API could be exposed where each replica only sends out hash of the data. Repairs and other stuff can happen like a normal read call. 

--
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