[
https://issues.apache.org/jira/browse/CASSANDRA-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102568#comment-14102568
]
Aleksey Yeschenko commented on CASSANDRA-7405:
----------------------------------------------
bq. Specifically, why do we handle null values specially for clustering
columns? Also, why do we insert an empty binary when the type doesn't support
it? Why do we insert empty binaries at all instead of nulls (when we have
something that matches nullval)?
I think I wrote that. The reason is that a clustering column can obviously not
contain null, but it can contain an empty value (esp. with default nullval
being '').
Also, every type supports empty binaries.
> Optimize cqlsh COPY TO and COPY FROM
> ------------------------------------
>
> Key: CASSANDRA-7405
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7405
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Aleksey Yeschenko
> Assignee: Mikhail Stepura
> Fix For: 2.1.1
>
> Attachments: CASSANDRA-2.1-7405.patch
>
>
> Now that we are using native proto via python-driver, we can, and should, at
> the very least:
> 1. Use proto paging in COPY TO
> 2. Use async writes in COPY FROM
--
This message was sent by Atlassian JIRA
(v6.2#6252)
