[jira] Updated: (PIG-366) PigPen - Eclipse plugin for a graphical PigLatin editor
[ https://issues.apache.org/jira/browse/PIG-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gibbon updated PIG-366: -- Attachment: org.apache.pig.pigpen-0.7.1.tar.gz Syntax highlighting and validation, and can launch a job on the cluster too. PigPen - Eclipse plugin for a graphical PigLatin editor --- Key: PIG-366 URL: https://issues.apache.org/jira/browse/PIG-366 Project: Pig Issue Type: New Feature Reporter: Shubham Chopra Assignee: Daniel Dai Priority: Minor Attachments: org.apache.pig.pigpen-0.7.0.tar.gz, org.apache.pig.pigpen-0.7.1.tar.gz, org.apache.pig.pigpen_0.0.1.jar, org.apache.pig.pigpen_0.0.1.tgz, org.apache.pig.pigpen_0.0.4.jar, pigpen.patch, pigPen.patch, PigPen.tgz This is an Eclipse plugin that provides a GUI that can help users create PigLatin scripts and see the example generator outputs on the fly and submit the jobs to hadoop clusters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-366) PigPen - Eclipse plugin for a graphical PigLatin editor
[ https://issues.apache.org/jira/browse/PIG-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gibbon updated PIG-366: -- Attachment: org.apache.pig.pigpen_0.7.1.jar The binary for the plugin. Place in the plugins subdirectory of eclipse. PigPen - Eclipse plugin for a graphical PigLatin editor --- Key: PIG-366 URL: https://issues.apache.org/jira/browse/PIG-366 Project: Pig Issue Type: New Feature Reporter: Shubham Chopra Assignee: Daniel Dai Priority: Minor Attachments: org.apache.pig.pigpen-0.7.0.tar.gz, org.apache.pig.pigpen-0.7.1.tar.gz, org.apache.pig.pigpen_0.0.1.jar, org.apache.pig.pigpen_0.0.1.tgz, org.apache.pig.pigpen_0.0.4.jar, org.apache.pig.pigpen_0.7.1.jar, pigpen.patch, pigPen.patch, PigPen.tgz This is an Eclipse plugin that provides a GUI that can help users create PigLatin scripts and see the example generator outputs on the fly and submit the jobs to hadoop clusters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1604) 'relation as scalar' does not work with complex types
[ https://issues.apache.org/jira/browse/PIG-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated PIG-1604: --- Fix Version/s: 0.8.0 Affects Version/s: 0.8.0 'relation as scalar' does not work with complex types -- Key: PIG-1604 URL: https://issues.apache.org/jira/browse/PIG-1604 Project: Pig Issue Type: Bug Affects Versions: 0.8.0 Reporter: Thejas M Nair Fix For: 0.8.0 Statement such as sclr = limit b 1; d = foreach a generate name, age/(double)sclr.mapcol#'it' as some_sum; Results in the following parse error: ERROR 1000: Error during parsing. Non-atomic field expected but found atomic field -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (PIG-1604) 'relation as scalar' does not work with complex types
'relation as scalar' does not work with complex types -- Key: PIG-1604 URL: https://issues.apache.org/jira/browse/PIG-1604 Project: Pig Issue Type: Bug Reporter: Thejas M Nair Statement such as sclr = limit b 1; d = foreach a generate name, age/(double)sclr.mapcol#'it' as some_sum; Results in the following parse error: ERROR 1000: Error during parsing. Non-atomic field expected but found atomic field -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1604) 'relation as scalar' does not work with complex types
[ https://issues.apache.org/jira/browse/PIG-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated PIG-1604: --- Status: Patch Available (was: Open) 'relation as scalar' does not work with complex types -- Key: PIG-1604 URL: https://issues.apache.org/jira/browse/PIG-1604 Project: Pig Issue Type: Bug Affects Versions: 0.8.0 Reporter: Thejas M Nair Assignee: Thejas M Nair Fix For: 0.8.0 Attachments: PIG-1604.1.patch Statement such as sclr = limit b 1; d = foreach a generate name, age/(double)sclr.mapcol#'it' as some_sum; Results in the following parse error: ERROR 1000: Error during parsing. Non-atomic field expected but found atomic field -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1604) 'relation as scalar' does not work with complex types
[ https://issues.apache.org/jira/browse/PIG-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated PIG-1604: --- Attachment: PIG-1604.1.patch Patch passes unit tests. Pasting result of test-patch - [exec] +1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. 'relation as scalar' does not work with complex types -- Key: PIG-1604 URL: https://issues.apache.org/jira/browse/PIG-1604 Project: Pig Issue Type: Bug Affects Versions: 0.8.0 Reporter: Thejas M Nair Assignee: Thejas M Nair Fix For: 0.8.0 Attachments: PIG-1604.1.patch Statement such as sclr = limit b 1; d = foreach a generate name, age/(double)sclr.mapcol#'it' as some_sum; Results in the following parse error: ERROR 1000: Error during parsing. Non-atomic field expected but found atomic field -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1603) dependency created by 'relation as scalar' not captured in graph
[ https://issues.apache.org/jira/browse/PIG-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated PIG-1603: --- Attachment: PIG-1603.2.patch Daniel pointed out that changes are required in more Visitors. Attaching new patch with the changes. Changes have not yet been in PruneColumns, so it might not work with -Dpig.usenewlogicalplan=false . dependency created by 'relation as scalar' not captured in graph Key: PIG-1603 URL: https://issues.apache.org/jira/browse/PIG-1603 Project: Pig Issue Type: Bug Reporter: Thejas M Nair Assignee: Thejas M Nair Fix For: 0.8.0 Attachments: PIG-1603.1.patch, PIG-1603.2.patch The LogicalOperator that has a ReadScalar udf has a dependency on the relation that is provides the input to scalar variables. But this is not captured in the graph representation, and as a result DependencyOrderWalker does not traverse the graph in the real dependency order. The testcase TestFRJoin2.testConcatenateJobForScalar3 fails as a result of this issue. (It has been commented out for now.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1604) 'relation as scalar' does not work with complex types
[ https://issues.apache.org/jira/browse/PIG-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908096#action_12908096 ] Daniel Dai commented on PIG-1604: - +1, patch looks good. 'relation as scalar' does not work with complex types -- Key: PIG-1604 URL: https://issues.apache.org/jira/browse/PIG-1604 Project: Pig Issue Type: Bug Affects Versions: 0.8.0 Reporter: Thejas M Nair Assignee: Thejas M Nair Fix For: 0.8.0 Attachments: PIG-1604.1.patch Statement such as sclr = limit b 1; d = foreach a generate name, age/(double)sclr.mapcol#'it' as some_sum; Results in the following parse error: ERROR 1000: Error during parsing. Non-atomic field expected but found atomic field -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1604) 'relation as scalar' does not work with complex types
[ https://issues.apache.org/jira/browse/PIG-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated PIG-1604: --- Status: Resolved (was: Patch Available) Hadoop Flags: [Reviewed] Resolution: Fixed Patch committed to 0.8 branch and trunk. 'relation as scalar' does not work with complex types -- Key: PIG-1604 URL: https://issues.apache.org/jira/browse/PIG-1604 Project: Pig Issue Type: Bug Affects Versions: 0.8.0 Reporter: Thejas M Nair Assignee: Thejas M Nair Fix For: 0.8.0 Attachments: PIG-1604.1.patch Statement such as sclr = limit b 1; d = foreach a generate name, age/(double)sclr.mapcol#'it' as some_sum; Results in the following parse error: ERROR 1000: Error during parsing. Non-atomic field expected but found atomic field -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (PIG-1605) Adding soft link to plan to solve input file dependency
Adding soft link to plan to solve input file dependency --- Key: PIG-1605 URL: https://issues.apache.org/jira/browse/PIG-1605 Project: Pig Issue Type: Bug Components: impl Affects Versions: 0.8.0 Reporter: Daniel Dai Assignee: Daniel Dai Fix For: 0.8.0 In scalar implementation, we need to deal with implicit dependencies. [PIG-1603|https://issues.apache.org/jira/browse/PIG-1603] is trying to solve the problem by adding a LOScalar operator. Here is a different approach. We will add a soft link to the plan, and soft link is only visible to the walkers. All other part of the logical plan does not know the existence of the soft link. The benefits are: 1. Logical plan do not need to deal with LOScalar, this makes logical plan cleaner 2. Conceptually scalar dependency is different. Regular link represent a data flow in pipeline. In scalar, the dependency means an operator depends on a file generated by the other operator. It's different type of data dependency. 3. Soft link can solve other dependency problem in the future. If we introduce another UDF dependent on a file generated by another operator, we can use this mechanism to solve it. Currently, there are two cases we can use soft link: 1. scalar dependency, where ReadScalar UDF will use a file generate by a LOStore 2. store-load dependency, where we will load a file which is generated by a store in the same script. This happens in multi-store case. Currently we solve it by regular link. It is better to use a soft link. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1605) Adding soft link to plan to solve input file dependency
[ https://issues.apache.org/jira/browse/PIG-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-1605: Description: In scalar implementation, we need to deal with implicit dependencies. [PIG-1603|https://issues.apache.org/jira/browse/PIG-1603] is trying to solve the problem by adding a LOScalar operator. Here is a different approach. We will add a soft link to the plan, and soft link is only visible to the walkers. By doing this, we can make sure we visit LOStore which generate scalar first, and then LOForEach which use the scalar. All other part of the logical plan does not know the existence of the soft link. The benefits are: 1. Logical plan do not need to deal with LOScalar, this makes logical plan cleaner 2. Conceptually scalar dependency is different. Regular link represent a data flow in pipeline. In scalar, the dependency means an operator depends on a file generated by the other operator. It's different type of data dependency. 3. Soft link can solve other dependency problem in the future. If we introduce another UDF dependent on a file generated by another operator, we can use this mechanism to solve it. Currently, there are two cases we can use soft link: 1. scalar dependency, where ReadScalar UDF will use a file generate by a LOStore 2. store-load dependency, where we will load a file which is generated by a store in the same script. This happens in multi-store case. Currently we solve it by regular link. It is better to use a soft link. was: In scalar implementation, we need to deal with implicit dependencies. [PIG-1603|https://issues.apache.org/jira/browse/PIG-1603] is trying to solve the problem by adding a LOScalar operator. Here is a different approach. We will add a soft link to the plan, and soft link is only visible to the walkers. All other part of the logical plan does not know the existence of the soft link. The benefits are: 1. Logical plan do not need to deal with LOScalar, this makes logical plan cleaner 2. Conceptually scalar dependency is different. Regular link represent a data flow in pipeline. In scalar, the dependency means an operator depends on a file generated by the other operator. It's different type of data dependency. 3. Soft link can solve other dependency problem in the future. If we introduce another UDF dependent on a file generated by another operator, we can use this mechanism to solve it. Currently, there are two cases we can use soft link: 1. scalar dependency, where ReadScalar UDF will use a file generate by a LOStore 2. store-load dependency, where we will load a file which is generated by a store in the same script. This happens in multi-store case. Currently we solve it by regular link. It is better to use a soft link. Adding soft link to plan to solve input file dependency --- Key: PIG-1605 URL: https://issues.apache.org/jira/browse/PIG-1605 Project: Pig Issue Type: Bug Components: impl Affects Versions: 0.8.0 Reporter: Daniel Dai Assignee: Daniel Dai Fix For: 0.8.0 In scalar implementation, we need to deal with implicit dependencies. [PIG-1603|https://issues.apache.org/jira/browse/PIG-1603] is trying to solve the problem by adding a LOScalar operator. Here is a different approach. We will add a soft link to the plan, and soft link is only visible to the walkers. By doing this, we can make sure we visit LOStore which generate scalar first, and then LOForEach which use the scalar. All other part of the logical plan does not know the existence of the soft link. The benefits are: 1. Logical plan do not need to deal with LOScalar, this makes logical plan cleaner 2. Conceptually scalar dependency is different. Regular link represent a data flow in pipeline. In scalar, the dependency means an operator depends on a file generated by the other operator. It's different type of data dependency. 3. Soft link can solve other dependency problem in the future. If we introduce another UDF dependent on a file generated by another operator, we can use this mechanism to solve it. Currently, there are two cases we can use soft link: 1. scalar dependency, where ReadScalar UDF will use a file generate by a LOStore 2. store-load dependency, where we will load a file which is generated by a store in the same script. This happens in multi-store case. Currently we solve it by regular link. It is better to use a soft link. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1578) PigServer.executeBatch does not return status of failed job for native mapreduce statement
[
https://issues.apache.org/jira/browse/PIG-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated PIG-1578:
---
Summary: PigServer.executeBatch does not return status of failed job for
native mapreduce statement (was: PigServer.executeBatch does not return status
of failed job)
I tried a different query that fails, which does not use mapreduce statement ,
and the expected ExecJob is returned. Changing the summary to reflect that.
PigServer.executeBatch does not return status of failed job for native
mapreduce statement
--
Key: PIG-1578
URL: https://issues.apache.org/jira/browse/PIG-1578
Project: Pig
Issue Type: Bug
Reporter: Thejas M Nair
Assignee: Richard Ding
Fix For: 0.8.0
For failed job PigServer.executeBatch does not return ExecJob .
ExecJobs are created using output statistics, and the output statistics for
jobs that failed does not seem to exist.
The query i tried was a native mapreduce job, where the output file of the
native mr job already exists causing that job to fail.
{code}
A = load ' + INPUT_FILE + ';
B = mapreduce ' + jarFileName + ' +
Store A into 'table_testNativeMRJobSimple_input' +
Load 'table_testNativeMRJobSimple_output' +
`WordCount table_testNativeMRJobSimple_input + INPUT_FILE +
`;);
Store B into 'table_testNativeMRJobSimpleDir';);
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1600) Pig 080 Documentation
[ https://issues.apache.org/jira/browse/PIG-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Corinne Chandel updated PIG-1600: - Attachment: pig080-2-2.patch Pig080 Patch2-2 (patch2, second version) Incorporate review feedback. Pig 080 Documentation - Key: PIG-1600 URL: https://issues.apache.org/jira/browse/PIG-1600 Project: Pig Issue Type: Task Components: documentation Affects Versions: 0.8.0 Reporter: Corinne Chandel Assignee: Corinne Chandel Priority: Blocker Fix For: 0.8.0 Attachments: pig080-1.patch, pig080-2-2.patch, pig080-2.patch Pig 080 documentation - new features, updates, an fixes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1600) Pig 080 Documentation
[ https://issues.apache.org/jira/browse/PIG-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908139#action_12908139 ] Olga Natkovich commented on PIG-1600: - I have reviewed the patch and will be committing it to trunk and 0.7 branch as soon as I have a successful doc build. Thanks, Corinne! Pig 080 Documentation - Key: PIG-1600 URL: https://issues.apache.org/jira/browse/PIG-1600 Project: Pig Issue Type: Task Components: documentation Affects Versions: 0.8.0 Reporter: Corinne Chandel Assignee: Corinne Chandel Priority: Blocker Fix For: 0.8.0 Attachments: pig080-1.patch, pig080-2-2.patch, pig080-2.patch Pig 080 documentation - new features, updates, an fixes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1600) Pig 080 Documentation
[ https://issues.apache.org/jira/browse/PIG-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908150#action_12908150 ] Olga Natkovich commented on PIG-1600: - pig080-2-2.patch committed to both trunk and 0.8 branch Pig 080 Documentation - Key: PIG-1600 URL: https://issues.apache.org/jira/browse/PIG-1600 Project: Pig Issue Type: Task Components: documentation Affects Versions: 0.8.0 Reporter: Corinne Chandel Assignee: Corinne Chandel Priority: Blocker Fix For: 0.8.0 Attachments: pig080-1.patch, pig080-2-2.patch, pig080-2.patch Pig 080 documentation - new features, updates, an fixes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1479) Embed Pig in scripting languages
[
https://issues.apache.org/jira/browse/PIG-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Ding updated PIG-1479:
--
Attachment: PIG-1479.patch
Thanks Julien. I rebased the patch with the latest trunk and added an option
(-greek) in the Main class.
Now one can run a PIG-Greek script with following command:
{code}
java -cp pig.jar:jython jar:hadoop config dir org.apache.pig.Main -g
pig-greek script
{code}
or in local mode:
{code}
java -cp pig.jar:jython jar org.apache.pig.Main -x local -g pig-greek script
{code}
Embed Pig in scripting languages
Key: PIG-1479
URL: https://issues.apache.org/jira/browse/PIG-1479
Project: Pig
Issue Type: New Feature
Reporter: Julien Le Dem
Attachments: PIG-1479.patch, pig-greek.tgz
It should be possible to embed Pig calls in a scripting language and let
functions defined in the same script available as UDFs.
This is a spin off of https://issues.apache.org/jira/browse/PIG-928 which
lets users define UDFs in scripting languages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (PIG-1606) flatten documentation does not discuss flatten of empty bag
flatten documentation does not discuss flatten of empty bag
---
Key: PIG-1606
URL: https://issues.apache.org/jira/browse/PIG-1606
Project: Pig
Issue Type: Bug
Components: documentation
Reporter: Thejas M Nair
From the existing flatten documentation, it is not clear that flatten of an
empty bag results in that row being discarded .
For example the following query gives no output -
{code}
grunt cat /tmp/empty.bag
{} 1
grunt l = load '/tmp/empty.bag' as (b : bag{}, i : int);
grunt f = foreach l generate flatten(b), i;
grunt dump f;
grunt
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (PIG-1608) pig should always include pig-default.properties and pig.properties in the pig.jar
pig should always include pig-default.properties and pig.properties in the pig.jar -- Key: PIG-1608 URL: https://issues.apache.org/jira/browse/PIG-1608 Project: Pig Issue Type: Bug Reporter: niraj rai Assignee: niraj rai pig should always include pig-default.properties and pig.properties as a part of the pig.jar file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-1606) flatten documentation does not discuss flatten of empty bag
[
https://issues.apache.org/jira/browse/PIG-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olga Natkovich updated PIG-1606:
Fix Version/s: 0.9.0
flatten documentation does not discuss flatten of empty bag
---
Key: PIG-1606
URL: https://issues.apache.org/jira/browse/PIG-1606
Project: Pig
Issue Type: Bug
Components: documentation
Reporter: Thejas M Nair
Fix For: 0.9.0
From the existing flatten documentation, it is not clear that flatten of an
empty bag results in that row being discarded .
For example the following query gives no output -
{code}
grunt cat /tmp/empty.bag
{} 1
grunt l = load '/tmp/empty.bag' as (b : bag{}, i : int);
grunt f = foreach l generate flatten(b), i;
grunt dump f;
grunt
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1608) pig should always include pig-default.properties and pig.properties in the pig.jar
[ https://issues.apache.org/jira/browse/PIG-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908249#action_12908249 ] Olga Natkovich commented on PIG-1608: - pig-default is the only one we include. The other one is for users. pig should always include pig-default.properties and pig.properties in the pig.jar -- Key: PIG-1608 URL: https://issues.apache.org/jira/browse/PIG-1608 Project: Pig Issue Type: Bug Reporter: niraj rai Assignee: niraj rai pig should always include pig-default.properties and pig.properties as a part of the pig.jar file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1606) flatten documentation does not discuss flatten of empty bag
[
https://issues.apache.org/jira/browse/PIG-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908250#action_12908250
]
Olga Natkovich commented on PIG-1606:
-
Is this even the semantics we want. I would expect a single row with an empty
field.
flatten documentation does not discuss flatten of empty bag
---
Key: PIG-1606
URL: https://issues.apache.org/jira/browse/PIG-1606
Project: Pig
Issue Type: Bug
Components: documentation
Reporter: Thejas M Nair
Fix For: 0.9.0
From the existing flatten documentation, it is not clear that flatten of an
empty bag results in that row being discarded .
For example the following query gives no output -
{code}
grunt cat /tmp/empty.bag
{} 1
grunt l = load '/tmp/empty.bag' as (b : bag{}, i : int);
grunt f = foreach l generate flatten(b), i;
grunt dump f;
grunt
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PIG-1606) flatten documentation does not discuss flatten of empty bag
[
https://issues.apache.org/jira/browse/PIG-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12908259#action_12908259
]
Alan Gates commented on PIG-1606:
-
flatten of an empty bag has to be a black hole else cogroup + foreach != inner
join, which we claim it does.
flatten documentation does not discuss flatten of empty bag
---
Key: PIG-1606
URL: https://issues.apache.org/jira/browse/PIG-1606
Project: Pig
Issue Type: Bug
Components: documentation
Reporter: Thejas M Nair
Fix For: 0.9.0
From the existing flatten documentation, it is not clear that flatten of an
empty bag results in that row being discarded .
For example the following query gives no output -
{code}
grunt cat /tmp/empty.bag
{} 1
grunt l = load '/tmp/empty.bag' as (b : bag{}, i : int);
grunt f = foreach l generate flatten(b), i;
grunt dump f;
grunt
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (PIG-1609) 'union onschema' should give a more useful error message when schema of one of the relations has null column name
'union onschema' should give a more useful error message when schema of one of
the relations has null column name
-
Key: PIG-1609
URL: https://issues.apache.org/jira/browse/PIG-1609
Project: Pig
Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Thejas M Nair
Assignee: Thejas M Nair
Fix For: 0.8.0
A better error message needs to be given in this case -
{code}
grunt l = load '/tmp/empty.bag' as (i : int);
grunt f = foreach l generate i+1;
grunt describe f;
f: {int}
grunt u = union onschema l , f;
2010-09-10 18:08:13,000 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
1000: Error during parsing. Error merging
schemas for union operator
Details at logfile: /Users/tejas/pig_nmr_syn/trunk/pig_1284167020897.log
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
