cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4920) Add collation semantics to abstract type to provide standard sort order for Strings
Date Thu, 22 Jun 2017 16:34:14 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeremy Hanna updated CASSANDRA-4920:
------------------------------------
    Component/s: Materialized Views

> Add collation semantics to abstract type to provide standard sort order for Strings
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4920
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4920
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL, Materialized Views
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Sidharth
>            Priority: Minor
>              Labels: cassandra
>
> Adding a way to sort UTF8 based on below described collation semantics can be useful.

> Use case: Say for example you have wide rows where you cannot use cassandra's standard
indexes(secondary/primary index). Lets say each column had a string value that was either
one of alphanumeric or purely numeric and you wanted an index by value. MOre specifically
you want to slice range over a bunch of column values and say "get me all the ID's associated
with value ABC to XYZ ". As usual I would index these values in a materialized views  
> More specifically I create an index CF; And add these values into a CompositeType column
and SliceRange over them for the indexing to work and I dont really care weather its a alpha
or a numeric as long as its ordered by the following collation semantics as follows:
> 1) If the string is a numeric then it should be comparable like a numeric
> 2) If its a alpha then it should be comparable like a normal string. 
> 3) If its a alhpa-numeric then a contiguos sequence of numbers in the string should be
compared as numbers like "c10" > "c2".
> 4) UTF8 type strings assumed everywhere.
> How this helps?:
> 1) You dont end up creating multiple CF for different value types. 
> 2) You dont have to write boiler plate to do complicated type detection and do this manually
in the application. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message