You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Steeve Morin (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/10/03 14:54:34 UTC

[jira] [Issue Comment Edited] (CASSANDRA-2777) Pig storage handler should implement LoadMetadata

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

Steeve Morin edited comment on CASSANDRA-2777 at 10/3/11 12:54 PM:
-------------------------------------------------------------------

Fixed it for me on Pig -0.9- 0.8.3 and Cassandra 0.8.6 (Brisk).

Pig 0.9 complains:
{{2011-10-03 14:41:21,033 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 1200: <file test.pig, line 8, column 78>  mismatched input ')' expecting IDENTIFIER_L}}
                
      was (Author: steeve):
    Fixed it for me on Pig 0.9 and Cassandra 0.8.6 (Brisk).
                  
> Pig storage handler should implement LoadMetadata
> -------------------------------------------------
>
>                 Key: CASSANDRA-2777
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2777
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Contrib
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 0.8.7
>
>         Attachments: 2777-v2.txt, 2777.txt
>
>
> The reason for this is many builtin functions like SUM won't work on longs (you can workaround using LongSum, but that's lame) because the query planner doesn't know about the types beforehand, even though we are casting to native longs.
> There is some impact to this, though.  With LoadMetadata implemented, existing scripts that specify schema will need to remove it (since LM is doing it for them) and they will need to conform to LM's terminology (key, columns, name, value) within the script.  This is trivial to change, however, and the increased functionality is worth the switch.

--
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