[
https://issues.apache.org/jira/browse/CASSANDRA-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344438#comment-15344438
]
Alex Petrov commented on CASSANDRA-11911:
-----------------------------------------
Thank you for the review!
I've addressed the problems you've listed and re-ran the tests:
||[trunk|https://github.com/ifesdjeen/cassandra/tree/11911-trunk]|[utest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-11911-trunk-testall/]|[dtest|https://cassci.datastax.com/view/Dev/view/ifesdjeen/job/ifesdjeen-11911-trunk-dtest/]|
> CQLSSTableWriter should allow for unset fields
> ----------------------------------------------
>
> Key: CASSANDRA-11911
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11911
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Cassandra 3.0.6
> Reporter: Matt Kopit
> Assignee: Alex Petrov
> Labels: lhf
>
> If you are using CQLSSTableWriter to bulk load data into sstables the only
> way to handle fields without values is by setting them to NULL, which results
> in the generation of a tombstoned field in the resulting sstable. For a large
> dataset this can result in a large number of tombstones.
> CQLSSTableWriter is currently instantiated with a single INSERT statement, so
> it's not an option to modify the insert statement to specify different fields
> on a per-row basis.
> Here are three potential solutions to this problem:
> 1. Change the default behavior of how NULLs are handled so those fields are
> treated as UNSET and will never be written to the sstable.
> 2. Create a configuration option for CQLSSTableWriter that governs whether
> NULLs should be ignored.
> 3. Invent a new constant that represents an UNSET value which can be used in
> place of NULL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
