You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Brian Donaldson (JIRA)" <ji...@apache.org> on 2010/03/16 01:42:27 UTC
[jira] Created: (PIG-1300) PigStorage does not load tuples with
large #s.
PigStorage does not load tuples with large #s.
----------------------------------------------
Key: PIG-1300
URL: https://issues.apache.org/jira/browse/PIG-1300
Project: Pig
Issue Type: Bug
Components: data
Reporter: Brian Donaldson
Say I have a file 'a' with the following entry:
(30010401402)
grunt> A = LOAD 'a' AS (t:tuple(a:chararray));
grunt> DUMP A;
2010-03-15 17:37:23,333 [main] WARN org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigHadoopLogger - org.apache.pig.builtin.PigStorage: Unable to interpret value [B@353c375 in field being converted to type tuple, caught Exception <For input string: "30010401402"> field discarded
2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1345435162/tmp-308780808"
2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
2010-03-15 17:37:23,336 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
()
If I have another file 'b' with the following entry:
(30010401402L)
grunt> B = LOAD 'b' AS (t:tuple(a:chararray));
grunt> DUMP B;
2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1630850555/tmp1316256240"
2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
2010-03-15 17:39:10,052 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
((30010401402L))
Is there a way to get the load in the first example to work? Or do I need to start affixing an L to all my #s?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (PIG-1300) PigStorage does not load tuples with
large #s.
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Dai closed PIG-1300.
---------------------------
> PigStorage does not load tuples with large #s.
> ----------------------------------------------
>
> Key: PIG-1300
> URL: https://issues.apache.org/jira/browse/PIG-1300
> Project: Pig
> Issue Type: Bug
> Components: data
> Reporter: Brian Donaldson
> Fix For: 0.7.0
>
>
> Say I have a file 'a' with the following entry:
> (30010401402)
> grunt> A = LOAD 'a' AS (t:tuple(a:chararray));
> grunt> DUMP A;
> 2010-03-15 17:37:23,333 [main] WARN org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigHadoopLogger - org.apache.pig.builtin.PigStorage: Unable to interpret value [B@353c375 in field being converted to type tuple, caught Exception <For input string: "30010401402"> field discarded
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1345435162/tmp-308780808"
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:37:23,336 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ()
> If I have another file 'b' with the following entry:
> (30010401402L)
> grunt> B = LOAD 'b' AS (t:tuple(a:chararray));
> grunt> DUMP B;
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1630850555/tmp1316256240"
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:39:10,052 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ((30010401402L))
> Is there a way to get the load in the first example to work? Or do I need to start affixing an L to all my #s?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PIG-1300) PigStorage does not load tuples with
large #s.
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Dai resolved PIG-1300.
-----------------------------
Resolution: Fixed
Fix Version/s: 0.7.0
> PigStorage does not load tuples with large #s.
> ----------------------------------------------
>
> Key: PIG-1300
> URL: https://issues.apache.org/jira/browse/PIG-1300
> Project: Pig
> Issue Type: Bug
> Components: data
> Reporter: Brian Donaldson
> Fix For: 0.7.0
>
>
> Say I have a file 'a' with the following entry:
> (30010401402)
> grunt> A = LOAD 'a' AS (t:tuple(a:chararray));
> grunt> DUMP A;
> 2010-03-15 17:37:23,333 [main] WARN org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigHadoopLogger - org.apache.pig.builtin.PigStorage: Unable to interpret value [B@353c375 in field being converted to type tuple, caught Exception <For input string: "30010401402"> field discarded
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1345435162/tmp-308780808"
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:37:23,336 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ()
> If I have another file 'b' with the following entry:
> (30010401402L)
> grunt> B = LOAD 'b' AS (t:tuple(a:chararray));
> grunt> DUMP B;
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1630850555/tmp1316256240"
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:39:10,052 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ((30010401402L))
> Is there a way to get the load in the first example to work? Or do I need to start affixing an L to all my #s?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1300) PigStorage does not load tuples with
large #s.
Posted by "Brian Donaldson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845636#action_12845636 ]
Brian Donaldson commented on PIG-1300:
--------------------------------------
This is with version 0.5+11.1 (cloudera), and with the recently released 0.6.
> PigStorage does not load tuples with large #s.
> ----------------------------------------------
>
> Key: PIG-1300
> URL: https://issues.apache.org/jira/browse/PIG-1300
> Project: Pig
> Issue Type: Bug
> Components: data
> Reporter: Brian Donaldson
>
> Say I have a file 'a' with the following entry:
> (30010401402)
> grunt> A = LOAD 'a' AS (t:tuple(a:chararray));
> grunt> DUMP A;
> 2010-03-15 17:37:23,333 [main] WARN org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigHadoopLogger - org.apache.pig.builtin.PigStorage: Unable to interpret value [B@353c375 in field being converted to type tuple, caught Exception <For input string: "30010401402"> field discarded
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1345435162/tmp-308780808"
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:37:23,336 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ()
> If I have another file 'b' with the following entry:
> (30010401402L)
> grunt> B = LOAD 'b' AS (t:tuple(a:chararray));
> grunt> DUMP B;
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1630850555/tmp1316256240"
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:39:10,052 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ((30010401402L))
> Is there a way to get the load in the first example to work? Or do I need to start affixing an L to all my #s?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1300) PigStorage does not load tuples with
large #s.
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845628#action_12845628 ]
Daniel Dai commented on PIG-1300:
---------------------------------
Which version of Pig are you using? Can you try it on trunk? Looks like it should be fixed in PIG-613.
> PigStorage does not load tuples with large #s.
> ----------------------------------------------
>
> Key: PIG-1300
> URL: https://issues.apache.org/jira/browse/PIG-1300
> Project: Pig
> Issue Type: Bug
> Components: data
> Reporter: Brian Donaldson
>
> Say I have a file 'a' with the following entry:
> (30010401402)
> grunt> A = LOAD 'a' AS (t:tuple(a:chararray));
> grunt> DUMP A;
> 2010-03-15 17:37:23,333 [main] WARN org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigHadoopLogger - org.apache.pig.builtin.PigStorage: Unable to interpret value [B@353c375 in field being converted to type tuple, caught Exception <For input string: "30010401402"> field discarded
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1345435162/tmp-308780808"
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:37:23,336 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ()
> If I have another file 'b' with the following entry:
> (30010401402L)
> grunt> B = LOAD 'b' AS (t:tuple(a:chararray));
> grunt> DUMP B;
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1630850555/tmp1316256240"
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:39:10,052 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ((30010401402L))
> Is there a way to get the load in the first example to work? Or do I need to start affixing an L to all my #s?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1300) PigStorage does not load tuples with
large #s.
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845641#action_12845641 ]
Daniel Dai commented on PIG-1300:
---------------------------------
I just tried, it works in trunk. The fix will come with next release (0.7).
> PigStorage does not load tuples with large #s.
> ----------------------------------------------
>
> Key: PIG-1300
> URL: https://issues.apache.org/jira/browse/PIG-1300
> Project: Pig
> Issue Type: Bug
> Components: data
> Reporter: Brian Donaldson
> Fix For: 0.7.0
>
>
> Say I have a file 'a' with the following entry:
> (30010401402)
> grunt> A = LOAD 'a' AS (t:tuple(a:chararray));
> grunt> DUMP A;
> 2010-03-15 17:37:23,333 [main] WARN org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigHadoopLogger - org.apache.pig.builtin.PigStorage: Unable to interpret value [B@353c375 in field being converted to type tuple, caught Exception <For input string: "30010401402"> field discarded
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1345435162/tmp-308780808"
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:37:23,335 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:37:23,336 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ()
> If I have another file 'b' with the following entry:
> (30010401402L)
> grunt> B = LOAD 'b' AS (t:tuple(a:chararray));
> grunt> DUMP B;
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Successfully stored result in: "file:/tmp/temp-1630850555/tmp1316256240"
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Records written : 1
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Bytes written : 0
> 2010-03-15 17:39:10,051 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - 100% complete!
> 2010-03-15 17:39:10,052 [main] INFO org.apache.pig.backend.local.executionengine.LocalPigLauncher - Success!!
> ((30010401402L))
> Is there a way to get the load in the first example to work? Or do I need to start affixing an L to all my #s?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.