Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 15 Jun 2011 22:56:47 +0000 (UTC)
From: "Jeremy Hanna (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <537845087.8921.1308178607375.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1152952579.8878.1308177890475.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-2777) Pig storage handler should
 implement LoadMetadata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeremy Hanna updated CASSANDRA-2777:
------------------------------------

    Reviewer: jeromatron

> 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
>         Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira