Jing Huang commented on PIG-941:

Hi Yiping
I am trying to reproduce the scenario that you are having. 
Say I have a table t1 with two columns 'word' and 'count'.  I try load t1 with 
projection ('word,count,domain')   -- please not 'domain' is a non-existing 

Here is the result that I have got:


If i only query ('word,count'), 
I got result:

So I think zebra handles non-existing column correctly. 

Now I have a question, which zebra jar you are using?
I recall that some time back, we did have  a bug reports that  zebra handles 
wrong on querying  non existing column.


> [zebra] Loading non-existing column generates error
> ---------------------------------------------------
>                 Key: PIG-941
>                 URL: https://issues.apache.org/jira/browse/PIG-941
>             Project: Pig
>          Issue Type: Bug
>          Components: data
>            Reporter: Yiping Han
> Loading a column that does not exist generates the following error:
> 2009-09-01 21:29:15,161 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 
> 2999: Unexpected internal error. null
> Example is like this:
> STORE urls2 into '$output' using 
> org.apache.pig.table.pig.TableStorer('md5:string, url:string');
> and then in another pig script, I load the table:
> input = LOAD '$output' USING org.apache.pig.table.pig.TableLoader('md5,url, 
> domain');
> where domain is a column that does not exist.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to