cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-4605) Pig should use the default comparator for slice_start/end
Date Wed, 19 Sep 2012 12:01:07 GMT

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

Brandon Williams resolved CASSANDRA-4605.
-----------------------------------------

       Resolution: Later
    Fix Version/s:     (was: 1.1.6)

I remember why I did this now.  We don't have an opportunity to grab the schema at this point
without doing something pretty hackish like just parsing the ks/cf from the url, then calling
initSchema an extra time with thrift setup/teardown to figure out the comparator.
                
> Pig should use the default comparator for slice_start/end
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-4605
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4605
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>
> Pig allows specifying slice start and end, but by default uses a BytesType comparator
for this, though it allows overriding with a 'comparator' param.
> I believe this came from a time before pig was fully schema-aware, and made it more convenient
if you had timeuuid, since writing the hex form 'EA' was easier than '\\u234' which then you'd
have to url escape.
> Instead, pig should use the default comparator from the schema, but still allow overriding.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message