Build failed in Hudson: Hive-trunk-h0.20 #478
See https://hudson.apache.org/hudson/job/Hive-trunk-h0.20/478/
--
[...truncated 7225 lines...]
[junit] o = [234, [firstString, secondString], {firstKey=1, secondKey=2},
-234, 1.0, -2.5]
[junit] Testing protocol: org.apache.thrift.protocol.TBinaryProtocol
[junit] TypeName =
struct_hello:int,2bye:arraystring,another:mapstring,int,nhello:int,d:double,nd:double
[junit] bytes
=x08xffxffx00x00x00xeax0fxffxfex0bx00x00x00x02x00x00x00x0bx66x69x72x73x74x53x74x72x69x6ex67x00x00x00x0cx73x65x63x6fx6ex64x53x74x72x69x6ex67x0dxffxfdx0bx08x00x00x00x02x00x00x00x08x66x69x72x73x74x4bx65x79x00x00x00x01x00x00x00x09x73x65x63x6fx6ex64x4bx65x79x00x00x00x02x08xffxfcxffxffxffx16x04xffxfbx3fxf0x00x00x00x00x00x00x04xffxfaxc0x04x00x00x00x00x00x00x00
[junit] o class = class java.util.ArrayList
[junit] o size = 6
[junit] o[0] class = class java.lang.Integer
[junit] o[1] class = class java.util.ArrayList
[junit] o[2] class = class java.util.HashMap
[junit] o = [234, [firstString, secondString], {firstKey=1, secondKey=2},
-234, 1.0, -2.5]
[junit] Testing protocol: org.apache.thrift.protocol.TJSONProtocol
[junit] TypeName =
struct_hello:int,2bye:arraystring,another:mapstring,int,nhello:int,d:double,nd:double
[junit] bytes
=x7bx22x2dx31x22x3ax7bx22x69x33x32x22x3ax32x33x34x7dx2cx22x2dx32x22x3ax7bx22x6cx73x74x22x3ax5bx22x73x74x72x22x2cx32x2cx22x66x69x72x73x74x53x74x72x69x6ex67x22x2cx22x73x65x63x6fx6ex64x53x74x72x69x6ex67x22x5dx7dx2cx22x2dx33x22x3ax7bx22x6dx61x70x22x3ax5bx22x73x74x72x22x2cx22x69x33x32x22x2cx32x2cx7bx22x66x69x72x73x74x4bx65x79x22x3ax31x2cx22x73x65x63x6fx6ex64x4bx65x79x22x3ax32x7dx5dx7dx2cx22x2dx34x22x3ax7bx22x69x33x32x22x3ax2dx32x33x34x7dx2cx22x2dx35x22x3ax7bx22x64x62x6cx22x3ax31x2ex30x7dx2cx22x2dx36x22x3ax7bx22x64x62x6cx22x3ax2dx32x2ex35x7dx7d
[junit] bytes in text
={-1:{i32:234},-2:{lst:[str,2,firstString,secondString]},-3:{map:[str,i32,2,{firstKey:1,secondKey:2}]},-4:{i32:-234},-5:{dbl:1.0},-6:{dbl:-2.5}}
[junit] o class = class java.util.ArrayList
[junit] o size = 6
[junit] o[0] class = class java.lang.Integer
[junit] o[1] class = class java.util.ArrayList
[junit] o[2] class = class java.util.HashMap
[junit] o = [234, [firstString, secondString], {firstKey=1, secondKey=2},
-234, 1.0, -2.5]
[junit] Testing protocol:
org.apache.hadoop.hive.serde2.thrift.TCTLSeparatedProtocol
[junit] TypeName =
struct_hello:int,2bye:arraystring,another:mapstring,int,nhello:int,d:double,nd:double
[junit] bytes
=x32x33x34x01x66x69x72x73x74x53x74x72x69x6ex67x02x73x65x63x6fx6ex64x53x74x72x69x6ex67x01x66x69x72x73x74x4bx65x79x03x31x02x73x65x63x6fx6ex64x4bx65x79x03x32x01x2dx32x33x34x01x31x2ex30x01x2dx32x2ex35
[junit] bytes in text
=234firstStringsecondStringfirstKey1secondKey2-2341.0-2.5
[junit] o class = class java.util.ArrayList
[junit] o size = 6
[junit] o[0] class = class java.lang.Integer
[junit] o[1] class = class java.util.ArrayList
[junit] o[2] class = class java.util.HashMap
[junit] o = [234, [firstString, secondString], {firstKey=1, secondKey=2},
-234, 1.0, -2.5]
[junit] Beginning Test testTBinarySortableProtocol:
[junit] Testing struct test { double hello}
[junit] Testing struct test { i32 hello}
[junit] Testing struct test { i64 hello}
[junit] Testing struct test { string hello}
[junit] Testing struct test { string hello, double another}
[junit] Test testTBinarySortableProtocol passed!
[junit] bytes in text =234 firstStringsecondString
firstKey1secondKey2
[junit] compare to=234 firstStringsecondString
firstKey1secondKey2
[junit] o class = class java.util.ArrayList
[junit] o size = 3
[junit] o[0] class = class java.lang.Integer
[junit] o[1] class = class java.util.ArrayList
[junit] o[2] class = class java.util.HashMap
[junit] o = [234, [firstString, secondString], {firstKey=1, secondKey=2}]
[junit] bytes in text =234 firstStringsecondString
firstKey1secondKey2
[junit] compare to=234 firstStringsecondString
firstKey1secondKey2
[junit] o class = class java.util.ArrayList
[junit] o size = 3
[junit] o = [234, null, {firstKey=1, secondKey=2}]
[junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.936 sec
[junit] Running org.apache.hadoop.hive.serde2.lazy.TestLazyArrayMapStruct
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.5 sec
[junit] Running org.apache.hadoop.hive.serde2.lazy.TestLazyPrimitive
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.339 sec
[junit] Running org.apache.hadoop.hive.serde2.lazy.TestLazySimpleSerDe
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.574 sec
[junit] Running org.apache.hadoop.hive.serde2.lazybinary.TestLazyBinarySerDe
[junit] Beginning Test TestLazyBinarySerDe:
[junit] Test TestLazyBinarySerDe passed!
[jira] Commented: (HIVE-1829) Fix intermittent failures in TestRemoteMetaStore
[
https://issues.apache.org/jira/browse/HIVE-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979773#action_12979773
]
John Sichi commented on HIVE-1829:
--
+1. Will commit when tests pass.
Fix intermittent failures in TestRemoteMetaStore
Key: HIVE-1829
URL: https://issues.apache.org/jira/browse/HIVE-1829
Project: Hive
Issue Type: Bug
Components: Metastore
Affects Versions: 0.6.0
Reporter: Edward Capriolo
Assignee: Carl Steinbach
Fix For: 0.7.0
Attachments: HIVE-1829.1.patch.txt
Notice how Running metastore! appears twice.
{noformat}
test:
[junit] Running org.apache.hadoop.hive.metastore.TestEmbeddedHiveMetaStore
[junit] BR.recoverFromMismatchedToken
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 36.697 sec
[junit] Running org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore
[junit] Running metastore!
[junit] Running metastore!
[junit] org.apache.thrift.transport.TTransportException: Could not create
ServerSocket on address 0.0.0.0/0.0.0.0:29083.
[junit] at
org.apache.thrift.transport.TServerSocket.init(TServerSocket.java:98)
[junit] at
org.apache.thrift.transport.TServerSocket.init(TServerSocket.java:79)
[junit] at
org.apache.hadoop.hive.metastore.TServerSocketKeepAlive.init(TServerSocketKeepAlive.java:34)
[junit] at
org.apache.hadoop.hive.metastore.HiveMetaStore.main(HiveMetaStore.java:2189)
[junit] at
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore$RunMS.run(TestRemoteHiveMetaStore.java:35)
[junit] at java.lang.Thread.run(Thread.java:619)
[junit] Running org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Test org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore
FAILED (crashed)
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-1906) Add Eclipse launch configurations for HiveServer and MetaStoreServer
Add Eclipse launch configurations for HiveServer and MetaStoreServer Key: HIVE-1906 URL: https://issues.apache.org/jira/browse/HIVE-1906 Project: Hive Issue Type: Task Components: Build Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1906) Add Eclipse launch configurations for HiveServer and MetaStoreServer
[ https://issues.apache.org/jira/browse/HIVE-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-1906: - Attachment: HIVE-1906.1.patch.txt * Add HiveServer launch configuration * Add MetaStoreServer launch configuration * Add ASF headers to all launch configuration files Add Eclipse launch configurations for HiveServer and MetaStoreServer Key: HIVE-1906 URL: https://issues.apache.org/jira/browse/HIVE-1906 Project: Hive Issue Type: Task Components: Build Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-1906.1.patch.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-78) Authorization infrastructure for Hive
[ https://issues.apache.org/jira/browse/HIVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979827#action_12979827 ] Ashutosh Chauhan commented on HIVE-78: -- John's latest comment on HIVE-1696 https://issues.apache.org/jira/browse/HIVE-1696?focusedCommentId=12978176page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12978176 seems to indicate that HIVE-1696 is blocked on this getting committed. Do we know how far we are on this issue and how long it may take before it gets committed? That will help to estimate commit date for HIVE-1696 Authorization infrastructure for Hive - Key: HIVE-78 URL: https://issues.apache.org/jira/browse/HIVE-78 Project: Hive Issue Type: New Feature Components: Metastore, Query Processor, Server Infrastructure Reporter: Ashish Thusoo Assignee: He Yongqiang Attachments: createuser-v1.patch, hive-78-metadata-v1.patch, hive-78-syntax-v1.patch, HIVE-78.1.nothrift.patch, HIVE-78.1.thrift.patch, HIVE-78.10.no_thrift.patch, HIVE-78.11.patch, HIVE-78.12.2.patch, HIVE-78.12.patch, HIVE-78.2.nothrift.patch, HIVE-78.2.thrift.patch, HIVE-78.4.complete.patch, HIVE-78.4.no_thrift.patch, HIVE-78.5.complete.patch, HIVE-78.5.no_thrift.patch, HIVE-78.6.complete.patch, HIVE-78.6.no_thrift.patch, HIVE-78.7.no_thrift.patch, HIVE-78.7.patch, HIVE-78.9.no_thrift.patch, HIVE-78.9.patch, hive-78.diff Allow hive to integrate with existing user repositories for authentication and authorization infromation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1903) Can't join HBase tables if one's name is the beginning of the other
[
https://issues.apache.org/jira/browse/HIVE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi updated HIVE-1903:
-
Attachment: HIVE-1903.1.patch
Can't join HBase tables if one's name is the beginning of the other
---
Key: HIVE-1903
URL: https://issues.apache.org/jira/browse/HIVE-1903
Project: Hive
Issue Type: Bug
Reporter: Jean-Daniel Cryans
Assignee: John Sichi
Fix For: 0.7.0
Attachments: HIVE-1903.1.patch
I tried joining two tables, let's call them table and table_a, but I'm
seeing an array of errors such as this:
{noformat}
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at
org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat.getRecordReader(HiveHBaseTableInputFormat.java:118)
at
org.apache.hadoop.hive.ql.io.HiveInputFormat.getRecordReader(HiveInputFormat.java:231)
{noformat}
The reason is that HiveInputFormat.pushProjectionsAndFilters matches the
aliases with startsWith so in my case the mappers for table_a were getting
the columns from table as well as its own (and since it had less column, it
was trying to get one too far in the array).
I don't know if just changing it to equals fill fix it, my guess is it
won't, since it may break RCFiles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1903) Can't join HBase tables if one's name is the beginning of the other
[
https://issues.apache.org/jira/browse/HIVE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi updated HIVE-1903:
-
Status: Patch Available (was: Open)
This should fix it generically for all non-native tables (without disturbing
the prefix-matching logic for native tables). I'm still running through
regression tests though.
Can't join HBase tables if one's name is the beginning of the other
---
Key: HIVE-1903
URL: https://issues.apache.org/jira/browse/HIVE-1903
Project: Hive
Issue Type: Bug
Reporter: Jean-Daniel Cryans
Assignee: John Sichi
Fix For: 0.7.0
Attachments: HIVE-1903.1.patch
I tried joining two tables, let's call them table and table_a, but I'm
seeing an array of errors such as this:
{noformat}
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at
org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat.getRecordReader(HiveHBaseTableInputFormat.java:118)
at
org.apache.hadoop.hive.ql.io.HiveInputFormat.getRecordReader(HiveInputFormat.java:231)
{noformat}
The reason is that HiveInputFormat.pushProjectionsAndFilters matches the
aliases with startsWith so in my case the mappers for table_a were getting
the columns from table as well as its own (and since it had less column, it
was trying to get one too far in the array).
I don't know if just changing it to equals fill fix it, my guess is it
won't, since it may break RCFiles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-78) Authorization infrastructure for Hive
[ https://issues.apache.org/jira/browse/HIVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979868#action_12979868 ] Namit Jain commented on HIVE-78: All the tests are passing - we are blocked on the names of the new reserved words, we have introduced. We are trying to get it in asap Authorization infrastructure for Hive - Key: HIVE-78 URL: https://issues.apache.org/jira/browse/HIVE-78 Project: Hive Issue Type: New Feature Components: Metastore, Query Processor, Server Infrastructure Reporter: Ashish Thusoo Assignee: He Yongqiang Attachments: createuser-v1.patch, hive-78-metadata-v1.patch, hive-78-syntax-v1.patch, HIVE-78.1.nothrift.patch, HIVE-78.1.thrift.patch, HIVE-78.10.no_thrift.patch, HIVE-78.11.patch, HIVE-78.12.2.patch, HIVE-78.12.patch, HIVE-78.2.nothrift.patch, HIVE-78.2.thrift.patch, HIVE-78.4.complete.patch, HIVE-78.4.no_thrift.patch, HIVE-78.5.complete.patch, HIVE-78.5.no_thrift.patch, HIVE-78.6.complete.patch, HIVE-78.6.no_thrift.patch, HIVE-78.7.no_thrift.patch, HIVE-78.7.patch, HIVE-78.9.no_thrift.patch, HIVE-78.9.patch, hive-78.diff Allow hive to integrate with existing user repositories for authentication and authorization infromation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1903) Can't join HBase tables if one's name is the beginning of the other
[
https://issues.apache.org/jira/browse/HIVE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979872#action_12979872
]
Namit Jain commented on HIVE-1903:
--
+1
The changes look good
Can't join HBase tables if one's name is the beginning of the other
---
Key: HIVE-1903
URL: https://issues.apache.org/jira/browse/HIVE-1903
Project: Hive
Issue Type: Bug
Reporter: Jean-Daniel Cryans
Assignee: John Sichi
Fix For: 0.7.0
Attachments: HIVE-1903.1.patch
I tried joining two tables, let's call them table and table_a, but I'm
seeing an array of errors such as this:
{noformat}
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at
org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat.getRecordReader(HiveHBaseTableInputFormat.java:118)
at
org.apache.hadoop.hive.ql.io.HiveInputFormat.getRecordReader(HiveInputFormat.java:231)
{noformat}
The reason is that HiveInputFormat.pushProjectionsAndFilters matches the
aliases with startsWith so in my case the mappers for table_a were getting
the columns from table as well as its own (and since it had less column, it
was trying to get one too far in the array).
I don't know if just changing it to equals fill fix it, my guess is it
won't, since it may break RCFiles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-78) Authorization infrastructure for Hive
[ https://issues.apache.org/jira/browse/HIVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979892#action_12979892 ] Ashutosh Chauhan commented on HIVE-78: -- @Namit, Sounds good. Thanks for the info. Authorization infrastructure for Hive - Key: HIVE-78 URL: https://issues.apache.org/jira/browse/HIVE-78 Project: Hive Issue Type: New Feature Components: Metastore, Query Processor, Server Infrastructure Reporter: Ashish Thusoo Assignee: He Yongqiang Attachments: createuser-v1.patch, hive-78-metadata-v1.patch, hive-78-syntax-v1.patch, HIVE-78.1.nothrift.patch, HIVE-78.1.thrift.patch, HIVE-78.10.no_thrift.patch, HIVE-78.11.patch, HIVE-78.12.2.patch, HIVE-78.12.patch, HIVE-78.2.nothrift.patch, HIVE-78.2.thrift.patch, HIVE-78.4.complete.patch, HIVE-78.4.no_thrift.patch, HIVE-78.5.complete.patch, HIVE-78.5.no_thrift.patch, HIVE-78.6.complete.patch, HIVE-78.6.no_thrift.patch, HIVE-78.7.no_thrift.patch, HIVE-78.7.patch, HIVE-78.9.no_thrift.patch, HIVE-78.9.patch, hive-78.diff Allow hive to integrate with existing user repositories for authentication and authorization infromation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1862) Revive partition filtering in the Hive MetaStore
[ https://issues.apache.org/jira/browse/HIVE-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979911#action_12979911 ] Mac Yang commented on HIVE-1862: Ran the test again with the full dataset (~300k partitions in jdo2 table) and 10 concurrent processes. It ran for 30 hours without error. The test was run against a remote metastore server, with datanucleus 2.1.1 and the partition filtering code in place (pre HIVE-1853). MySQL version is 5.1.46. Revive partition filtering in the Hive MetaStore Key: HIVE-1862 URL: https://issues.apache.org/jira/browse/HIVE-1862 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.7.0 Reporter: Devaraj Das Fix For: 0.7.0 Attachments: HIVE-1862.1.patch.txt, invoke_runqry.sh, qry, qry-sch.Z, runqry HIVE-1853 downgraded the JDO version. This makes the feature of partition filtering in the metastore unusable. This jira is to keep track of the lost feature and discussing approaches to bring it back. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1862) Revive partition filtering in the Hive MetaStore
[ https://issues.apache.org/jira/browse/HIVE-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979926#action_12979926 ] John Sichi commented on HIVE-1862: -- I checked our server; it's MySQL 5.0.84. Also, we set the following hive-site.xml properties: datanucleus.transactionIsolation=repeatable-read datanucleus.valuegeneration.transactionIsolation=repeatable-read datanucleus.connectionPoolingType=none Revive partition filtering in the Hive MetaStore Key: HIVE-1862 URL: https://issues.apache.org/jira/browse/HIVE-1862 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.7.0 Reporter: Devaraj Das Fix For: 0.7.0 Attachments: HIVE-1862.1.patch.txt, invoke_runqry.sh, qry, qry-sch.Z, runqry HIVE-1853 downgraded the JDO version. This makes the feature of partition filtering in the metastore unusable. This jira is to keep track of the lost feature and discussing approaches to bring it back. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-78) Authorization infrastructure for Hive
[ https://issues.apache.org/jira/browse/HIVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] He Yongqiang updated HIVE-78: - Attachment: HIVE-78.12.3.patch John shared this link http://www.antlr.org/wiki/pages/viewpage.action?pageId=1741 offline to me. The new patch uses the first option in that link to solve the keyword conflict. Right now only did the work for keyword user and role. If needed, can open followup for others. But it will be better to try to import the second option to Hive. Or both depending on different cases. The second one is cleaner and can be default option. This can be further investigated in follow up jiras. Authorization infrastructure for Hive - Key: HIVE-78 URL: https://issues.apache.org/jira/browse/HIVE-78 Project: Hive Issue Type: New Feature Components: Metastore, Query Processor, Server Infrastructure Reporter: Ashish Thusoo Assignee: He Yongqiang Attachments: createuser-v1.patch, hive-78-metadata-v1.patch, hive-78-syntax-v1.patch, HIVE-78.1.nothrift.patch, HIVE-78.1.thrift.patch, HIVE-78.10.no_thrift.patch, HIVE-78.11.patch, HIVE-78.12.2.patch, HIVE-78.12.3.patch, HIVE-78.12.patch, HIVE-78.2.nothrift.patch, HIVE-78.2.thrift.patch, HIVE-78.4.complete.patch, HIVE-78.4.no_thrift.patch, HIVE-78.5.complete.patch, HIVE-78.5.no_thrift.patch, HIVE-78.6.complete.patch, HIVE-78.6.no_thrift.patch, HIVE-78.7.no_thrift.patch, HIVE-78.7.patch, HIVE-78.9.no_thrift.patch, HIVE-78.9.patch, hive-78.diff Allow hive to integrate with existing user repositories for authentication and authorization infromation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1903) Can't join HBase tables if one's name is the beginning of the other
[
https://issues.apache.org/jira/browse/HIVE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Namit Jain updated HIVE-1903:
-
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed. Thanks John
Can't join HBase tables if one's name is the beginning of the other
---
Key: HIVE-1903
URL: https://issues.apache.org/jira/browse/HIVE-1903
Project: Hive
Issue Type: Bug
Reporter: Jean-Daniel Cryans
Assignee: John Sichi
Fix For: 0.7.0
Attachments: HIVE-1903.1.patch
I tried joining two tables, let's call them table and table_a, but I'm
seeing an array of errors such as this:
{noformat}
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at
org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat.getRecordReader(HiveHBaseTableInputFormat.java:118)
at
org.apache.hadoop.hive.ql.io.HiveInputFormat.getRecordReader(HiveInputFormat.java:231)
{noformat}
The reason is that HiveInputFormat.pushProjectionsAndFilters matches the
aliases with startsWith so in my case the mappers for table_a were getting
the columns from table as well as its own (and since it had less column, it
was trying to get one too far in the array).
I don't know if just changing it to equals fill fix it, my guess is it
won't, since it may break RCFiles.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HIVE-1907) Store jobid in ExecDriver
Store jobid in ExecDriver - Key: HIVE-1907 URL: https://issues.apache.org/jira/browse/HIVE-1907 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain This will help in auditing - the usecase we have right now is to find out which tasks are for gathering stats -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1907) Store jobid in ExecDriver
[ https://issues.apache.org/jira/browse/HIVE-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-1907: - Attachment: hive.1907.1.patch Store jobid in ExecDriver - Key: HIVE-1907 URL: https://issues.apache.org/jira/browse/HIVE-1907 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.1907.1.patch This will help in auditing - the usecase we have right now is to find out which tasks are for gathering stats -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1907) Store jobid in ExecDriver
[ https://issues.apache.org/jira/browse/HIVE-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-1907: - Status: Patch Available (was: Open) Store jobid in ExecDriver - Key: HIVE-1907 URL: https://issues.apache.org/jira/browse/HIVE-1907 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.1907.1.patch This will help in auditing - the usecase we have right now is to find out which tasks are for gathering stats -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
