You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (Created) (JIRA)" <ji...@apache.org> on 2012/01/24 21:46:40 UTC

[jira] [Created] (CASSANDRA-3778) KEY IN (...) queries do not work

KEY IN (...) queries do not work
--------------------------------

                 Key: CASSANDRA-3778
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
             Project: Cassandra
          Issue Type: Sub-task
    Affects Versions: 1.1
            Reporter: Eric Evans
             Fix For: 1.1


{{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Sylvain Lebresne (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194604#comment-13194604 ] 

Sylvain Lebresne commented on CASSANDRA-3778:
---------------------------------------------

bq. I am unable to reproduce with dtest because of a change to the Python driver that I am guessing hasn't been propagated.

I've created http://code.google.com/a/apache-extras.org/p/cassandra-dbapi2/issues/detail?id=14 but it wasn't reviewed yet by any of the driver committers (hint, hint :D).

bq. To reproduce this with scqeal

You're right, this is a bug. As it happens, the refactor done in CASSANDRA-3791 fixes that bug (among other benefits), so let's maybe just deal with that patch.
                
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Eric Evans (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195384#comment-13195384 ] 

Eric Evans commented on CASSANDRA-3778:
---------------------------------------

bq. I've created http://code.google.com/a/apache-extras.org/p/cassandra-dbapi2/issues/detail?id=14 but it wasn't reviewed yet by any of the driver committers (hint, hint ).

committed.

bq. You're right, this is a bug. As it happens, the refactor done in CASSANDRA-3791 fixes that bug (among other benefits), so let's maybe just deal with that patch.

OK, I'll add that to my list to have a look at (if no one beats me to it).
                
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Sylvain Lebresne (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne resolved CASSANDRA-3778.
-----------------------------------------

    Resolution: Fixed

Just confirmed that CASSANDRA-3791 did fix the test above so re-closing this one.
                
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Reopened] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Eric Evans (Reopened) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Evans reopened CASSANDRA-3778:
-----------------------------------


Sorry to backpedal, but now I'm not so sure.

The reason I couldn't reproduce earlier with my tests was because trunk is now defaulting to CQLv3, and I was not calling {{set_cql_version()}}.  Now that I am, the error has returned.

I am unable to reproduce with dtest because of a change to the Python driver that I am guessing hasn't been propagated.

{noformat}
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/nose/case.py", line 187, in runTest
    self.test(*self.arg)
  File "/home/eevans/dev/src/git/cassandra-dtest/cql_tests.py", line 20, in static_cf_test
    cursor = self.cql_connection(node1, version=cql_version).cursor()
  File "/home/eevans/dev/src/git/cassandra-dtest/dtest.py", line 110, in cql_connection
    con = cql.connect(host, port, keyspace=keyspace, cql_version=version)
TypeError: connect() got an unexpected keyword argument 'cql_version'
{noformat}

To reproduce this with scqeal (https://github.com/acunu/scqeal), try the following (point CASSANDRA_HOME to a built tree):

{noformat}
$ SET_CQL_VERSION=3.0.0 CQL_VERSION=3.0.0 CASSANDRA_HOME=/path/to/cassandra DEBUG=1 ./runtests -sv \
    scqeal.tests.test_select:TestSelect.test_key_in
{noformat}
                
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Sylvain Lebresne (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193018#comment-13193018 ] 

Sylvain Lebresne commented on CASSANDRA-3778:
---------------------------------------------

I just tried with code I just committed on trunk and the test above passes. Not sure when/what fixed it though. Are you still able to reproduce on the last code?
                
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Eric Evans (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194250#comment-13194250 ] 

Eric Evans commented on CASSANDRA-3778:
---------------------------------------

bq. I just tried with code I just committed on trunk and the test above passes. Not sure when/what fixed it though. Are you still able to reproduce on the last code?

Nope, it passes now.  High five?
                
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Issue Comment Edited] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Eric Evans (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194397#comment-13194397 ] 

Eric Evans edited comment on CASSANDRA-3778 at 1/27/12 3:24 AM:
----------------------------------------------------------------

Sorry to backpedal, but now I'm not so sure.

The reason I couldn't reproduce earlier with my tests was because trunk is now defaulting to CQLv2, and I was not calling {{set_cql_version()}}.  Now that I am, the error has returned.

I am unable to reproduce with dtest because of a change to the Python driver that I am guessing hasn't been propagated.

{noformat}
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/nose/case.py", line 187, in runTest
    self.test(*self.arg)
  File "/home/eevans/dev/src/git/cassandra-dtest/cql_tests.py", line 20, in static_cf_test
    cursor = self.cql_connection(node1, version=cql_version).cursor()
  File "/home/eevans/dev/src/git/cassandra-dtest/dtest.py", line 110, in cql_connection
    con = cql.connect(host, port, keyspace=keyspace, cql_version=version)
TypeError: connect() got an unexpected keyword argument 'cql_version'
{noformat}

To reproduce this with scqeal (https://github.com/acunu/scqeal), try the following (point CASSANDRA_HOME to a built tree):

{noformat}
$ SET_CQL_VERSION=3.0.0 CQL_VERSION=3.0.0 CASSANDRA_HOME=/path/to/cassandra DEBUG=1 ./runtests -sv \
    scqeal.tests.test_select:TestSelect.test_key_in
{noformat}

_Edit: Trunk is now defaulting to CQLv2, not v3_
                
      was (Author: urandom):
    Sorry to backpedal, but now I'm not so sure.

The reason I couldn't reproduce earlier with my tests was because trunk is now defaulting to CQLv3, and I was not calling {{set_cql_version()}}.  Now that I am, the error has returned.

I am unable to reproduce with dtest because of a change to the Python driver that I am guessing hasn't been propagated.

{noformat}
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/nose/case.py", line 187, in runTest
    self.test(*self.arg)
  File "/home/eevans/dev/src/git/cassandra-dtest/cql_tests.py", line 20, in static_cf_test
    cursor = self.cql_connection(node1, version=cql_version).cursor()
  File "/home/eevans/dev/src/git/cassandra-dtest/dtest.py", line 110, in cql_connection
    con = cql.connect(host, port, keyspace=keyspace, cql_version=version)
TypeError: connect() got an unexpected keyword argument 'cql_version'
{noformat}

To reproduce this with scqeal (https://github.com/acunu/scqeal), try the following (point CASSANDRA_HOME to a built tree):

{noformat}
$ SET_CQL_VERSION=3.0.0 CQL_VERSION=3.0.0 CASSANDRA_HOME=/path/to/cassandra DEBUG=1 ./runtests -sv \
    scqeal.tests.test_select:TestSelect.test_key_in
{noformat}
                  
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CASSANDRA-3778) KEY IN (...) queries do not work

Posted by "Eric Evans (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Evans resolved CASSANDRA-3778.
-----------------------------------

    Resolution: Fixed
      Assignee: Sylvain Lebresne
    
> KEY IN (...) queries do not work
> --------------------------------
>
>                 Key: CASSANDRA-3778
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3778
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 1.1
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.1
>
>
> {{...KEY IN (...)}} queries fail due to faulty validation.  A pull request for cassandra-dtest was opened that demonstrates this: https://github.com/riptano/cassandra-dtest/pull/2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira