On Wed, Dec 12, 2012 at 8:04 AM, wrote:
> Hello Bill,
>
> The bug didn't block me or waste any time. Regarding the cast, I can't
> regenerate the bug right now because I'm running a script, but I can answer
> your questions:
>
> 1) describe of the relation passed to store returns the generated sc
What is the intention of the script?
foreach on the 'gruped' field here means you'll get only a single row
(because of GROUP .. ALL). the field features.f0 will be a bag.
mf0 is also a bag. Refer to
http://pig.apache.org/docs/r0.7.0/piglatin_ref2.html#Data+Types
Division of 2 bags doesnt make a lo
Looks like there are conflicting versions of Jackson jars in classpath.
On Wed, Dec 12, 2012 at 3:09 PM, Milind Vaidya wrote:
>
> org.codehaus.jackson.JsonFactory.enable(Lorg/codehaus/jackson/JsonParser$Feature;)Lorg/codehaus/jackson/JsonFactory;
>
Eh sorry
nf0 = foreach gruped generate features.id,features.f0/mf0;
Should be
nf0 = foreach gruped generate data.id,data.f0/mf0;
-- Forwarded message --
From: jamal sasha
Date: Wednesday, December 12, 2012
Subject: error
To: "user@pig.apache.org"
mf0 = LOAD 'max.txt’ AS (maxi
Glad you got to the bottom of it, and thanks for letting us know what fixed
it!
2012/12/12 James Schappet
> I was able to resolve this issue.
>
>
> Taking Hadoop out of my .profile, resolved the issue.
> PATH included: /Library/hadoop-1.0.2/bin, once removed I am able to
> connect Cassandra.
>
I'm a little vague on what you want to do. Can you provide an example?
2012/12/11 Prashant Kommireddi
> Here is a snippet of how schema is applied to tuples
>
> String serializedSchema = p.getProperty(signature + SCHEMA_FILE);
> if (serializedSchema != null) {
>
I was able to resolve this issue.
Taking Hadoop out of my .profile, resolved the issue.
PATH included: /Library/hadoop-1.0.2/bin, once removed I am able to
connect Cassandra.
Thanks for pointing me in the right direction.
On 12/11/12 1:13 PM, "James Schappet" wrote:
>This is what pig_cassa
Hello Bill,
The bug didn't block me or waste any time. Regarding the cast, I can't
regenerate the bug right now because I'm running a script, but I can
answer your questions:
1) describe of the relation passed to store returns the generated
schema name for the tuple, as described in:
ht
