You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Niels Basjes (JIRA)" <ji...@apache.org> on 2015/04/30 13:00:22 UTC
[jira] [Updated] (PIG-4525) Clarify "Scalar has more than one row
in the output."
[ https://issues.apache.org/jira/browse/PIG-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niels Basjes updated PIG-4525:
------------------------------
Attachment: PIG-4525-2015-04-30-1115.patch
This patch simply changes the exception message from
{code}java.lang.Exception: org.apache.pig.backend.executionengine.ExecException: ERROR 0: Scalar has more than one row in the output. 1st : (key,1), 2nd :(key,2){code}
to
{code}java.lang.Exception: org.apache.pig.backend.executionengine.ExecException: ERROR 0: Scalar has more than one row in the output. 1st : (key,1), 2nd :(key,2) (common cause: "JOIN" then "FOREACH ... GENERATE foo.bar" should be "foo::bar" )
{code}
> Clarify "Scalar has more than one row in the output."
> -----------------------------------------------------
>
> Key: PIG-4525
> URL: https://issues.apache.org/jira/browse/PIG-4525
> Project: Pig
> Issue Type: Improvement
> Reporter: Niels Basjes
> Assignee: Niels Basjes
> Priority: Trivial
> Attachments: PIG-4525-2015-04-30-1115.patch
>
>
> The exception "Scalar has more than one row in the output." is correct yet is reason for many (starting) pig developers to search the internet for a solution.
> I propose (and I'll include a patch) to simply extend the exception message with a hint towards the right solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)