You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Bill Graham (JIRA)" <ji...@apache.org> on 2011/02/25 22:35:21 UTC
[jira] Created: (PIG-1870) HBaseStorage doesn't project correctly
HBaseStorage doesn't project correctly
--------------------------------------
Key: PIG-1870
URL: https://issues.apache.org/jira/browse/PIG-1870
Project: Pig
Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Bill Graham
Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Status: Open (was: Patch Available)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Status: Open (was: Patch Available)
whoops :)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018447#comment-13018447 ]
Dmitriy V. Ryaboy commented on PIG-1870:
----------------------------------------
This is ready for review.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020392#comment-13020392 ]
Daniel Dai commented on PIG-1870:
---------------------------------
+1. Please commit if test pass.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020137#comment-13020137 ]
Dmitriy V. Ryaboy commented on PIG-1870:
----------------------------------------
Daniel, yeah, it's ready to go -- just waiting on another committer to +1 it.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Affects Version/s: (was: 0.8.0)
0.8.1
Fix Version/s: 0.8.1
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.1
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.8.1, 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.final.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Attachment: PIG_1870_for0.8.2.patch
patch for 0.8
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018721#comment-13018721 ]
Dmitriy V. Ryaboy commented on PIG-1870:
----------------------------------------
Are not.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Attachment: PIG_1870_for0.8.final.patch
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.final.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018736#comment-13018736 ]
Bill Graham commented on PIG-1870:
----------------------------------
Ok, my bad (embarrassed). Lesson learned: don't wget a patch from JIRA, then manually change the patch name to get another. You'll get something totally unexpected.
Verified that trunk and 0.8.0 branch tests pass for PIG_1870.3.patch and PIG_1870_for0.8.2.patch, respectively. Also verified ad-hoc Pig HBase jobs with projections now work against a cluster for both.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018563#comment-13018563 ]
Bill Graham commented on PIG-1870:
----------------------------------
Dmitriy, I was able to build with the new patches and the TestHBaseStorage test suite ran successfully with both trunk and 0.8.0. I'm getting failures when trying to run an HBase job against a distributed cluster though (version 0.90.0). This is similar to the issue I ran into in PIG-1782 that caused me to mess with how configs were initialized at one point.
These are the only values that I've overriden in {{$HBASE_CONF_DIR/hbase-site.xml}}:
{noformat}
hbase.rootdir
hbase.cluster.distributed
hbase.tmp.dir
hbase.zookeeper.quorum
hbase.zookeeper.property.dataDir
{noformat}
And this is the error I get trying to run any Pig job against HBase:
{noformat}
2011-04-11 13:36:58,659 [main] ERROR org.apache.hadoop.hbase.zookeeper.ZKConfig - no clientPort found in zoo.cfg
2011-04-11 13:36:58,665 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR 2017: Internal error creating job configuration.
{noformat}
I don't get this error running the PIG-1782 patch.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Status: Open (was: Patch Available)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Attachment: PIG_1870.patch
Attaching patch for trunk.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Attachments: PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Status: Patch Available (was: Open)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020133#comment-13020133 ]
Daniel Dai commented on PIG-1870:
---------------------------------
Hi, Dmitriy, do you still plan to commit this patch to 0.8?
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016001#comment-13016001 ]
Dmitriy V. Ryaboy commented on PIG-1870:
----------------------------------------
The problem isn't loadKey, it's that we set up a (static) TableInputFormat.SCAN in setLocation, which gets called multiple times, and not always after pushProjection; we wind up overwriting SCAN and "forgetting" we are pushing things. I am working on a patch.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Attachments: PIG_1870_1.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Attachment: PIG_1870_for0.8.patch
Attached patch for 0.8
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Attachments: PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to 0.8 branch and trunk.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.final.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018717#comment-13018717 ]
Bill Graham commented on PIG-1870:
----------------------------------
Either someone ran {{alias diff='echo -n ""'}} on my machine on April 1st, or all these patches are still the same. I think it's the latter. :)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051292#comment-13051292 ]
Dmitriy V. Ryaboy commented on PIG-1870:
----------------------------------------
it's in 8.1, I updated.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.1
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.8.1, 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.final.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Attachment: PIG_1870.2.patch
Thanks, Bill.
Attaching a patch that fixes the config confusion.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018640#comment-13018640 ]
Dmitriy V. Ryaboy commented on PIG-1870:
----------------------------------------
Forgot to click the apache license button -- i hereby submit this patch under the apache license, etc etc etc.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018697#comment-13018697 ]
Bill Graham commented on PIG-1870:
----------------------------------
Dymitriy, can you check that latest patch? PIG_1870.patch and PIG_1870.2.patch are the same.
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-1870) HBaseStorage doesn't project
correctly
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051174#comment-13051174 ]
Harsh J commented on PIG-1870:
------------------------------
Could someone please add the appropriate 0.8.x fix version here? Or if that's done when a release is tagged, np. Just thought it might help those following tickets here :)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.final.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy reassigned PIG-1870:
--------------------------------------
Assignee: Dmitriy V. Ryaboy
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Attachments: PIG_1870_1.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Status: Patch Available (was: Open)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Status: Patch Available (was: Open)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Attachment: PIG_1870.4.patch
Massively sped up tests for HBaseStorage by using local mode instead of mapreduce. About 10 secs / test now on my laptop (down from 50).
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Fix Version/s: 0.9.0
Status: Patch Available (was: Open)
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham updated PIG-1870:
-----------------------------
Attachment: PIG_1870_1.patch
Here's a patch with 5 new projection tests added to {{TestHBaseStorage}}, of which 4 fail. It's intended to be applied over PIG_1680 and it was generated from the git branch show here fyi:
https://github.com/billonahill/pig/commit/55561c23f209ca2f27e13ddd93146d7b2a2492e3
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Attachments: PIG_1870_1.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PIG-1870) HBaseStorage doesn't project correctly
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy updated PIG-1870:
-----------------------------------
Attachment: PIG_1870.3.patch
Patch for trunk
> HBaseStorage doesn't project correctly
> --------------------------------------
>
> Key: PIG-1870
> URL: https://issues.apache.org/jira/browse/PIG-1870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Bill Graham
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.9.0
>
> Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira