You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Yiping Han (JIRA)" <ji...@apache.org> on 2009/09/01 23:33:32 UTC
[jira] Created: (PIG-941) [zebra] Loading non-existing column
generates error
[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.
[jira] Resolved: (PIG-941) [zebra] Loading non-existing column
generates error
Posted by "Yan Zhou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yan Zhou resolved PIG-941.
--------------------------
Resolution: Cannot Reproduce
Mark it as unproducible for lack of submitter's confirmation.
> [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.
[jira] Commented: (PIG-941) [zebra] Loading non-existing column
generates error
Posted by "Jing Huang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750677#action_12750677 ]
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 column.
Here is the result that I have got:
(this,2,)
(is,1,)
(a,4,)
(test,2,)
(hello,1,)
(world,3,)
======
If i only query ('word,count'),
I got result:
(this,2)
(is,1)
(a,4)
(test,2)
(hello,1)
(world,3)
=======
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.
Thanks
> [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.