Github user jeffjirsa commented on the issue:
https://github.com/apache/cassandra/pull/98
Looks like this was committed as 0eebc6e6b7cd7fc801579e57701608e7bf155ee0 -
please do close the PR when you can (the project is unable to close it for you,
which is one of the reasons we tend
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
If anything is missing please let me know and I will fix it asap...
Den 13. mar. 2017 3.09 PM skrev "Mikkel Andersen" <
mikkel.t.ander...@gmail.com>:
> Thanks Benjamin
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
I will see what you have already then : )
On Mon, Mar 13, 2017 at 1:44 PM, Benjamin Lerer
wrote:
> @MikkelTAndersen
Github user blerer commented on the issue:
https://github.com/apache/cassandra/pull/98
@MikkelTAndersen Could you also add some unit tests to your patch?
---
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
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
Ahh sorry - it seems to complicated, its a simple null check - any chance
you can add it Alex ? I have attached the patch.
On Mon, Mar 13, 2017 at 1:38 PM, Alex Petrov
Github user ifesdjeen commented on the issue:
https://github.com/apache/cassandra/pull/98
Hi @MikkelTAndersen. Cassandra does not use pull requests for Apache
Cassandra. Please use JIRA directly.
You can get more information on the contribution process here
Github user MikkelTAndersen commented on the issue:
https://github.com/apache/cassandra/pull/98
This is a simple fix for when you query with CONTAINS and the collection is
empty (which ends up as null in the database) ... this is a blocking issue for
my company so would appreciate if