Open smigfu opened 6 years ago
Some more details:
=> all of the above happens intermittently only if I don't add any of the indexed fields to the SELECT clause (in my search case I am only interested in the primary keys which aren't indexed). As soon as I add the indexed fields to my SELECT all of the symptoms above disappear.
That said: Is it a requirement to add the indexed fields to your SELECT? Or do I always need to also add the primary keys to the index?
Hi @smigfu Could you please tell me wich versions(cassandras and index) are you using?. And also, a complete test in CQL?
I will try to put something together. As said this is an intermittent issue. Would it help if I provide you with the files the index writes to the filesystem?
As for the version of C*: I have seen this with 3.0.10, 3.10.0, 3.11.0 and 3.11.1 (custom build of the plugin)
I am hitting this too.
Hi,
during my unit tests I create a lot of tables with a lucene index applied to it, perform some operations and delete the table afterwards. Quite often but intermittently these test do fail and even impact other tests which don't use the index. This is due to the exception thrown on the server closing active connections on the client side.
Is there a way to more gracefully handle the case in the plugin? I have seen this issue for c* (https://issues.apache.org/jira/browse/CASSANDRA-13868) and tried with a combination of 3.11.1 and a custom build of lucene but the error still persited.
Cheers, Philipp