cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11911) CQLSSTableWriter should allow for unset fields
Date Mon, 20 Jun 2016 18:37:57 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joshua McKenzie updated CASSANDRA-11911:
----------------------------------------
    Reviewer: Benjamin Lerer

> 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)

Mime
View raw message