[ 
https://issues.apache.org/jira/browse/CASSANDRA-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570716#comment-14570716
 ] 

Benedict commented on CASSANDRA-9071:
-------------------------------------

bq. there is no need to keep the whole previous CF, and can consume more memory 
if the CF has many columns

This wouldn't be a problem, since the CF is retained anyway. The more piercing 
criticism of my patch is that I addressed the opposite end of the situation 
(even missing the obvious intent from the prior naming of the variables). In 
fact while it looked to me like the last record written to could be empty, we 
only ever flush after at least one cell is present, so that isn't a risk.

Thanks for pointing out your patch. I've pushed it to my github repository to 
await continuous integration results.

> CQLSSTableWriter gives java.lang.AssertionError: Empty partition
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-9071
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9071
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: java 7 / 8
> cassandra 2.1.3 snapshot build locally with last commit 
> https://github.com/apache/cassandra/commit/6ee4b0989d9a3ae3e704918622024fa57fdf63e7
> macos Yosemite 10.10.2
>            Reporter: Ajit Joglekar
>            Assignee: Fabien Rousseau
>             Fix For: 2.1.x
>
>         Attachments: EmailWriter.java, Screen Shot 2015-04-15 at 11.14.40 
> PM.png, cassandra-2.1-9071.txt, data.csv.gz
>
>
> I am always getting the following error:
> Exception in thread "main" java.lang.AssertionError: Empty partition
> at 
> org.apache.cassandra.io.sstable.SSTableSimpleUnsortedWriter$DiskWriter.run(SSTableSimpleUnsortedWriter.java:228)
> It happens at a certain point that seems to be repeatable. Only issue is I am 
> converting 400 million records into multiple SSTables and creating small test 
> is a challenge
> Last comment from Benedict looks relevant here 
> https://issues.apache.org/jira/browse/CASSANDRA-8619
> Is there a work around, quick fix, fix that I can try out locally?
> Thanks,
> -Ajit



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to