Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Pig >> mail # dev >> Problem with "GROUP" reserved word


Copy link to this message
-
RE: Problem with "GROUP" reserved word
Pi,

Let me check it out. The implicit alias 'group' in a group/cogroup
works. However, I have seen when 'group' is used as an explicit alias, I
have seen parser errors. I just saw your JIRA update. I will check it
out.

Thanks,
Santhosh

-----Original Message-----
From: pi song [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 04, 2008 5:05 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem with "GROUP" reserved word

Not even in type branch but just in my local changes. Sorry for any
confusion.

On Wed, Jun 4, 2008 at 9:57 PM, pi song <[EMAIL PROTECTED]> wrote:

> Interestingly this just doesn't work in the type branch. I will report
it
> in Jira.
>
>
> On Tue, Jun 3, 2008 at 10:27 PM, pi song <[EMAIL PROTECTED]> wrote:
>
>> If I have a query like this:-
>>
>> A = load 'a' as (field1: int, field2: long);
>> B = group a by field1 ;
>>
>> The output schema of B would be:-
>>
>> group:int, a: bag{tuple1:tuple(field1: int,field2: long)}
>>
>> We define "GROUP" as a reserved word but we also use it as an
alias!!!
>> Users cannot refer to this field because they cannot use a reserved
word
>> as alias!!!
>>
>> I think one has to go.
>>
>> Any thought?
>>
>> Pi
>>
>
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB