[jira] [Created] (PIG-4960) Split followed by order by/skewed join is skewed

Rohini Palaniswamy created PIG-4960: --- Summary: Split followed by order by/skewed join is skewed Key: PIG-4960 URL: https://issues.apache.org/jira/browse/PIG-4960 Project: Pig Issue Type: Bu

[jira] [Created] (PIG-4961) LIMIT operation drop data from result

Sergey Svinarchuk created PIG-4961: -- Summary: LIMIT operation drop data from result Key: PIG-4961 URL: https://issues.apache.org/jira/browse/PIG-4961 Project: Pig Issue Type: Bug Affects

[jira] [Updated] (PIG-4961) LIMIT operation drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Svinarchuk updated PIG-4961: --- Attachment: script.pig input1.zip Attached script and sample data for reproduce

[jira] [Updated] (PIG-4960) Split followed by order by/skewed join is skewed

[ https://issues.apache.org/jira/browse/PIG-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4960: Description: Sampling is not done right. Split is a special case as EOP is returned after eac

[jira] [Updated] (PIG-4960) Split followed by order by/skewed join is skewed

[ https://issues.apache.org/jira/browse/PIG-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4960: Attachment: PIG-4960-1.patch > Split followed by order by/skewed join is skewed >

[jira] [Commented] (PIG-4961) LIMIT operation drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391962#comment-15391962 ] Sergey Svinarchuk commented on PIG-4961: If revert changes from src/org/apache/pig/

[jira] [Commented] (PIG-4957) See "Received kill signal" message for a normal run after PIG-4921

[ https://issues.apache.org/jira/browse/PIG-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392533#comment-15392533 ] Daniel Dai commented on PIG-4957: - +1 > See "Received kill signal" message for a normal run

[jira] [Commented] (PIG-4958) Tez autoparallelism estimation for order by is higher than mapreduce

[ https://issues.apache.org/jira/browse/PIG-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392540#comment-15392540 ] Rohini Palaniswamy commented on PIG-4958: - The above approach in the patch which mak

[jira] [Comment Edited] (PIG-4958) Tez autoparallelism estimation for order by is higher than mapreduce

[ https://issues.apache.org/jira/browse/PIG-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392540#comment-15392540 ] Rohini Palaniswamy edited comment on PIG-4958 at 7/25/16 7:30 PM:

[jira] [Commented] (PIG-4961) LIMIT operation drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392544#comment-15392544 ] Daniel Dai commented on PIG-4961: - Yes, I can reproduce. [~rohini], I don't feel the POLimit

[jira] [Commented] (PIG-4958) Tez autoparallelism estimation for order by is higher than mapreduce

[ https://issues.apache.org/jira/browse/PIG-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392591#comment-15392591 ] Bikas Saha commented on PIG-4958: - Also this might overload the RM in case there are many su

[jira] [Updated] (PIG-4961) LIMIT operation drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4961: Assignee: Rohini Palaniswamy It was just an optimization. Will check. Need to determine what

[jira] [Resolved] (PIG-4852) Add accumulator implementation for MaxTupleBy1stField

[ https://issues.apache.org/jira/browse/PIG-4852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai resolved PIG-4852. - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 0.17.0 Patch committed to trunk. Thanks

Build failed in Jenkins: Pig-trunk-commit #2357

See Changes: [daijy] PIG-4852: Add accumulator implementation for MaxTupleBy1stField [rohini] PIG-4957: See Received kill signal message for a normal run after PIG-4921 (rohini) -- [...truncat

Build failed in Jenkins: Pig-trunk #1931

See Changes: [daijy] PIG-4852: Add accumulator implementation for MaxTupleBy1stField [rohini] PIG-4957: See Received kill signal message for a normal run after PIG-4921 (rohini) -- [...truncated 2715

[jira] [Commented] (PIG-4958) Tez autoparallelism estimation for order by is higher than mapreduce

[ https://issues.apache.org/jira/browse/PIG-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392880#comment-15392880 ] Siddharth Seth commented on PIG-4958: - bq. If there are multiple outputs in sampler vert

[jira] [Commented] (PIG-4960) Split followed by order by/skewed join is skewed

[ https://issues.apache.org/jira/browse/PIG-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393036#comment-15393036 ] Rohini Palaniswamy commented on PIG-4960: - int rand = randGen.nextInt(rowProcessed +

[jira] [Updated] (PIG-4957) See "Received kill signal" message for a normal run after PIG-4921

[ https://issues.apache.org/jira/browse/PIG-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4957: Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Availabl

[jira] [Commented] (PIG-4961) LIMIT operation drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393118#comment-15393118 ] Rohini Palaniswamy commented on PIG-4961: - It is not a problem with the limit change

[jira] [Updated] (PIG-4952) Calculate the value of parallism for spark mode

[ https://issues.apache.org/jira/browse/PIG-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyunzhang_intel updated PIG-4952: -- Summary: Calculate the value of parallism for spark mode (was: Parallism is not set as correct va

[jira] [Updated] (PIG-4952) Calculate the value of parallism for spark mode

[ https://issues.apache.org/jira/browse/PIG-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liyunzhang_intel updated PIG-4952: -- Description: Calculate the value of parallism for spark mode like what org.apache.pig.backend.hado

[jira] [Updated] (PIG-4961) LIMIT operation drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4961: Attachment: PIG-4961-1.patch > LIMIT operation drop data from result > ---

[jira] [Updated] (PIG-4961) CROSS followed by LIMIT inside nested foreach drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4961: Affects Version/s: (was: 0.16.0) (was: 0.15.0)

[jira] [Updated] (PIG-4961) CROSS followed by LIMIT inside nested foreach drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4961: Fix Version/s: 0.16.1 0.17.0 > CROSS followed by LIMIT inside nested foreac

[jira] [Updated] (PIG-4960) Split followed by order by/skewed join is skewed

[ https://issues.apache.org/jira/browse/PIG-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4960: Status: Patch Available (was: Open) > Split followed by order by/skewed join is skewed >

[jira] [Updated] (PIG-4961) CROSS followed by LIMIT inside nested foreach drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated PIG-4961: Status: Patch Available (was: Open) > CROSS followed by LIMIT inside nested foreach drop data

[jira] [Commented] (PIG-4958) Tez autoparallelism estimation for order by is higher than mapreduce

[ https://issues.apache.org/jira/browse/PIG-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393203#comment-15393203 ] Rohini Palaniswamy commented on PIG-4958: - bq. Also this might overload the RM in ca

[jira] [Commented] (PIG-4961) CROSS followed by LIMIT inside nested foreach drop data from result

[ https://issues.apache.org/jira/browse/PIG-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393274#comment-15393274 ] Daniel Dai commented on PIG-4961: - +1 > CROSS followed by LIMIT inside nested foreach drop

[jira] [Commented] (PIG-4960) Split followed by order by/skewed join is skewed

[ https://issues.apache.org/jira/browse/PIG-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393277#comment-15393277 ] Daniel Dai commented on PIG-4960: - +1 > Split followed by order by/skewed join is skewed >

[jira] Subscription: PIG patch available

Issue Subscription Filter: PIG patch available (30 issues) Subscriber: pigdaily Key Summary PIG-4961CROSS followed by LIMIT inside nested foreach drop data from result https://issues.apache.org/jira/browse/PIG-4961 PIG-4960Split followed by order by/skewed join is skew