[
https://issues.apache.org/jira/browse/CASSANDRA-8830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327248#comment-14327248
]
Pierre commented on CASSANDRA-8830:
-----------------------------------
When I use .sorted() (SSTableSimpleWriter writer) I have no issue.
Another strange behiavior is if I use .sorted() and I *insert unordered
clustering columns* for a same partition, it doesn't throw ex and the resulting
sstable is correct and have *clustering columns sorted*. The doc specify it
should throw an ex in this case.
{quote}
* If this option is used, the resulting writer will expect rows to be
* added in SSTable sorted order (and an exception will be thrown if
that
* is not the case during insertion). The SSTable sorted order means
that
* rows are added such that their partition key respect the partitioner
* order and for a given partition, that the rows respect the clustering
* columns order.
{quote}
> CQLSSTableWriter addRow doesn't throw ex on error
> -------------------------------------------------
>
> Key: CASSANDRA-8830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8830
> Project: Cassandra
> Issue Type: Bug
> Reporter: Pierre
> Attachments: OOM.java
>
>
> When I add to much row for a same partition key on a CQLSSTableWriter the
> writer doesn't throw an exception but fail silently. I think it's linked to
> buffer size because when I use a bigger withBufferSizeInMB() the bug doesn't
> trigger. shouldn't It throw an exception ?
> Moreover it fails randomly between two states :
> 1/ the sstable directory is fully deleted and Thread.exit()
> or
> 2/ the sstable is corrupted and when you upload data to cluster you have
> inconsistant data
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
