[
https://issues.apache.org/jira/browse/CASSANDRA-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431015#comment-15431015
]
Nate Sanders commented on CASSANDRA-12471:
------------------------------------------
It's my understanding that in Cassandra protocol v4 (2.2 and above), we have a
special value called "unset". In the Python driver, it's
cassandra.query.UNSET_VALUE, for example. AFAICT, COPY FROM doesn't use these
at all -- it just inserts nulls, which create tombstones.
It seems that there should be a way to inform COPY FROM that you'd like to map,
for example, the empty string to unset instead of null. I haven't thought this
through carefully. It does seem to me that COPY FROM should be able to
generate unset values in some cases, and currently I'm not sure this is
possible.
> 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)
