cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12471) Allow for some form of "unset" in CQL's COPY command.
Date Tue, 23 Aug 2016 01:48:20 GMT

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

Stefania commented on CASSANDRA-12471:
--------------------------------------

Thanks for the clarification.

UNSET values were introduced by CASSANDRA-7304 and [PYTHON-317|https://datastax-oss.atlassian.net/browse/PYTHON-317].


I checked the cqlsh COPY code, and it is passing {{None}} for prepared statements, and {{None}}
does not get converted to {{Query.UNSET}} by the driver. So we should be able to change this,
by adding a new option. If this option is set, it should be sufficient to change the return
value for prepared statements of [this method|https://github.com/stef1927/cassandra/blob/cassandra-2.2/pylib/cqlshlib/copyutil.py#L1977].




> Allow for some form of "unset" in CQL's COPY command.
> -----------------------------------------------------
>
>                 Key: CASSANDRA-12471
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12471
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: CQL
>            Reporter: Nate Sanders
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> Currently, it looks like there's no way to get "unset" values via the COPY command, say,
for example with empty string fields.  Instead, these create tombstones.



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

Mime
View raw message