> The reason is described here:
https://issues.apache.org/jira/browse/CASSANDRA-5371?focusedCommentId=13621679&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13621679
>
> /Marcus
"...a lot of the work you've done you will redo when you compact your now
bigger L0 ssta
The reason is described here:
https://issues.apache.org/jira/browse/CASSANDRA-5371?focusedCommentId=13621679&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13621679
/Marcus
On Wed, Nov 23, 2016 at 6:31 PM, Jeff Jirsa
wrote:
> What you’re describing seems very clos
Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/86
I guess that you did not really intend to create that pull request.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project do
GitHub user quemilk opened a pull request:
https://github.com/apache/cassandra/pull/86
pull
aa
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/quemilk/cassandra trunk
Alternatively you can review and apply these changes as th
