[jira] [Commented] (CASSANDRA-4476) Support 2ndary index queries with only non-EQ clauses

2014-10-19 Thread Alexey Filippov (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176444#comment-14176444
 ] 

Alexey Filippov commented on CASSANDRA-4476:


Talking about {{Type.allowsIndexQuery}}, what operations do we want to support 
index queries now? {{LT, LTE, GTE, GT}} seem to work just fine; what about 
{{IN}} and {{NEQ}}? 


> Support 2ndary index queries with only non-EQ clauses
> -
>
> Key: CASSANDRA-4476
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4476
> Project: Cassandra
>  Issue Type: Improvement
>  Components: API, Core
>Reporter: Sylvain Lebresne
>Priority: Minor
>  Labels: cql
> Fix For: 2.1.2
>
>
> Currently, a query that uses 2ndary indexes must have at least one EQ clause 
> (on an indexed column). Given that indexed CFs are local (and use 
> LocalPartitioner that order the row by the type of the indexed column), we 
> should extend 2ndary indexes to allow querying indexed columns even when no 
> EQ clause is provided.
> As far as I can tell, the main problem to solve for this is to update 
> KeysSearcher.highestSelectivityPredicate(). I.e. how do we estimate the 
> selectivity of non-EQ clauses? I note however that if we can do that estimate 
> reasonably accurately, this might provide better performance even for index 
> queries that both EQ and non-EQ clauses, because some non-EQ clauses may have 
> a much better selectivity than EQ ones (say you index both the user country 
> and birth date, for SELECT * FROM users WHERE country = 'US' AND birthdate > 
> 'Jan 2009' AND birtdate < 'July 2009', you'd better use the birthdate index 
> first).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (CASSANDRA-5964) cqlsh raises a ValueError when connecting to Cassandra running in Eclipse

2014-05-01 Thread Alexey Filippov (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987021#comment-13987021
 ] 

Alexey Filippov edited comment on CASSANDRA-5964 at 5/1/14 9:42 PM:


That's interesting, the HEAD at the moment of writing 
([c2579b92|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=c2579b92bf2e721c099720a27b5d9e56be66e49c])
 seems to fail exactly as described in the ticket, with the only difference 
that the line numbering was changed:
{code}
$ ./cqlsh
Traceback (most recent call last):
  File "./cqlsh", line 1855, in 
main(*read_options(sys.argv[1:], os.environ))
  File "./cqlsh", line 1841, in main
ssl=options.ssl)
  File "./cqlsh", line 490, in __init__
self.get_connection_versions()
  File "./cqlsh", line 578, in get_connection_versions
self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
1)[0].split('.')[:3]))
ValueError: invalid literal for int() with base 10: 'Unknown'
{code}

So it does not appear to be fixed in HEAD or, it seems, 2.1.


was (Author: alf239):
That's interesting, the HEAD at the moment of writing 
([c2579b92|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=c2579b92bf2e721c099720a27b5d9e56be66e49c]):
{code}
$ ./cqlsh
Traceback (most recent call last):
  File "./cqlsh", line 1855, in 
main(*read_options(sys.argv[1:], os.environ))
  File "./cqlsh", line 1841, in main
ssl=options.ssl)
  File "./cqlsh", line 490, in __init__
self.get_connection_versions()
  File "./cqlsh", line 578, in get_connection_versions
self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
1)[0].split('.')[:3]))
ValueError: invalid literal for int() with base 10: 'Unknown'
{code}

So it does not appear to be fixed in HEAD or, it seems, 2.1.

> cqlsh raises a ValueError when connecting to Cassandra running in Eclipse
> -
>
> Key: CASSANDRA-5964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5964
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Greg DeAngelis
>Assignee: Dave Brosius
>Priority: Minor
> Fix For: 2.0.1
>
> Attachments: 5964.txt
>
>
> The release_version is set to 'Unknown' in system.local so the version 
> parsing logic fails.
> Traceback (most recent call last):
>   File "./cqlsh", line 2027, in 
> main(*read_options(sys.argv[1:], os.environ))
>   File "./cqlsh", line 2013, in main
> display_float_precision=options.float_precision)
>   File "./cqlsh", line 486, in __init__
> self.get_connection_versions()
>   File "./cqlsh", line 580, in get_connection_versions
> self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
> 1)[0].split('.')[:3]))
> ValueError: invalid literal for int() with base 10: 'Unknown'



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Comment Edited] (CASSANDRA-5964) cqlsh raises a ValueError when connecting to Cassandra running in Eclipse

2014-05-01 Thread Alexey Filippov (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987021#comment-13987021
 ] 

Alexey Filippov edited comment on CASSANDRA-5964 at 5/1/14 9:42 PM:


That's interesting, the HEAD at the moment of writing 
([c2579b92|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=c2579b92bf2e721c099720a27b5d9e56be66e49c]):
{code}
$ ./cqlsh
Traceback (most recent call last):
  File "./cqlsh", line 1855, in 
main(*read_options(sys.argv[1:], os.environ))
  File "./cqlsh", line 1841, in main
ssl=options.ssl)
  File "./cqlsh", line 490, in __init__
self.get_connection_versions()
  File "./cqlsh", line 578, in get_connection_versions
self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
1)[0].split('.')[:3]))
ValueError: invalid literal for int() with base 10: 'Unknown'
{code}

So it does not appear to be fixed in HEAD or, it seems, 2.1.


was (Author: alf239):
That's interesting, the HEAD at the moment of writing 
(c2579b92bf2e721c099720a27b5d9e56be66e49c):
{code}
$ ./cqlsh
Traceback (most recent call last):
  File "./cqlsh", line 1855, in 
main(*read_options(sys.argv[1:], os.environ))
  File "./cqlsh", line 1841, in main
ssl=options.ssl)
  File "./cqlsh", line 490, in __init__
self.get_connection_versions()
  File "./cqlsh", line 578, in get_connection_versions
self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
1)[0].split('.')[:3]))
ValueError: invalid literal for int() with base 10: 'Unknown'
{code}

So it does not appear to be fixed in HEAD or, it seems, 2.1.

> cqlsh raises a ValueError when connecting to Cassandra running in Eclipse
> -
>
> Key: CASSANDRA-5964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5964
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Greg DeAngelis
>Assignee: Dave Brosius
>Priority: Minor
> Fix For: 2.0.1
>
> Attachments: 5964.txt
>
>
> The release_version is set to 'Unknown' in system.local so the version 
> parsing logic fails.
> Traceback (most recent call last):
>   File "./cqlsh", line 2027, in 
> main(*read_options(sys.argv[1:], os.environ))
>   File "./cqlsh", line 2013, in main
> display_float_precision=options.float_precision)
>   File "./cqlsh", line 486, in __init__
> self.get_connection_versions()
>   File "./cqlsh", line 580, in get_connection_versions
> self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
> 1)[0].split('.')[:3]))
> ValueError: invalid literal for int() with base 10: 'Unknown'



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CASSANDRA-5964) cqlsh raises a ValueError when connecting to Cassandra running in Eclipse

2014-05-01 Thread Alexey Filippov (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987021#comment-13987021
 ] 

Alexey Filippov commented on CASSANDRA-5964:


That's interesting, the HEAD at the moment of writing 
(c2579b92bf2e721c099720a27b5d9e56be66e49c):
{code}
$ ./cqlsh
Traceback (most recent call last):
  File "./cqlsh", line 1855, in 
main(*read_options(sys.argv[1:], os.environ))
  File "./cqlsh", line 1841, in main
ssl=options.ssl)
  File "./cqlsh", line 490, in __init__
self.get_connection_versions()
  File "./cqlsh", line 578, in get_connection_versions
self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
1)[0].split('.')[:3]))
ValueError: invalid literal for int() with base 10: 'Unknown'
{code}

So it does not appear to be fixed in HEAD or, it seems, 2.1.

> cqlsh raises a ValueError when connecting to Cassandra running in Eclipse
> -
>
> Key: CASSANDRA-5964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5964
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Greg DeAngelis
>Assignee: Dave Brosius
>Priority: Minor
> Fix For: 2.0.1
>
> Attachments: 5964.txt
>
>
> The release_version is set to 'Unknown' in system.local so the version 
> parsing logic fails.
> Traceback (most recent call last):
>   File "./cqlsh", line 2027, in 
> main(*read_options(sys.argv[1:], os.environ))
>   File "./cqlsh", line 2013, in main
> display_float_precision=options.float_precision)
>   File "./cqlsh", line 486, in __init__
> self.get_connection_versions()
>   File "./cqlsh", line 580, in get_connection_versions
> self.cass_ver_tuple = tuple(map(int, vers['build'].split('-', 
> 1)[0].split('.')[:3]))
> ValueError: invalid literal for int() with base 10: 'Unknown'



--
This message was sent by Atlassian JIRA
(v6.2#6252)