Indeed. I did throw a comment on 11990 - not sure if that triggers emails
to those participants, but was hoping someone would take a look.
On Sat, Nov 5, 2016 at 2:26 AM, DuyHai Doan wrote:
> So from code review, the error message you get from the log is coming from
> the CASSANDRA-11990: http
Yep, already done: https://issues.apache.org/jira/browse/CASSANDRA-12877
On Fri, Nov 4, 2016 at 11:15 PM, Jonathan Haddad wrote:
> Can you file a Jira for this? Would be good to make sure 3.10 doesn't get
> released with this bug.
> On Fri, Nov 4, 2016 at 6:11 PM Voytek Jarnot
> wrote:
>
>> Tho
So from code review, the error message you get from the log is coming from
the CASSANDRA-11990:
https://github.com/ifesdjeen/cassandra/commit/dc4ae57f452e19adbe5a6a2c85f8a4b5a24d4103#diff-eae81aa3b81f9b1e07b109c446447a50R357
Now, it's just the consequence of the problem (throwing an assertion
erro
Can you file a Jira for this? Would be good to make sure 3.10 doesn't get
released with this bug.
On Fri, Nov 4, 2016 at 6:11 PM Voytek Jarnot
wrote:
> Thought I'd follow-up to myself, in case anyone else comes across this
> problem. I found a reasonably easy test case to reproduce the problem:
Thought I'd follow-up to myself, in case anyone else comes across this
problem. I found a reasonably easy test case to reproduce the problem:
This works in 3.9, but doesn't work in 3.10-snapshot:
CREATE KEYSPACE vjtest WITH replication = {'class': 'SimpleStrategy',
'replication_factor': '1'};
us
Wondering if anyone has encountered the same...
Full story and stacktraces below, short version is that creating a SASI
index fails for me when running a 3.10-SNAPSHOT build. One caveat: creating
the index on an empty table doesn't fail; however, soon after I start
pumping data into the table simi
