Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 6 Jul 2015 15:47:05 +0000 (UTC)
From: "Christopher Batey (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12842877.1436187621000.106373.1436197625495@Atlassian.JIRA>
In-Reply-To: <JIRA.12842877.1436187621000@Atlassian.JIRA>
References: <JIRA.12842877.1436187621000@Atlassian.JIRA>
 <JIRA.12842877.1436187621447@arcas>
Subject: [jira] [Commented] (CASSANDRA-9735) Add ignore extra fields for
 inserting JSON?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Batey commented on CASSANDRA-9735:
----------------------------------------------

I don't think silently dropping is a good idea, i think it should be explicit in the insert. Say you're storing a response from another system but don't want to keep all the fields or break if they add a field you aren't interested in.

> Add ignore extra fields for inserting JSON?
> -------------------------------------------
>
>                 Key: CASSANDRA-9735
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9735
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>            Reporter: Christopher Batey
>            Priority: Minor
>
> One of the use cases I see for the INSERT into JSON ... syntax is for when incoming data matches their schema. It would be nice to allow extra fields as to not be too brittle.
> However I think strict validation should be the default so maybe the insert or table can include an extra flag?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)