[jira] [Created] (HIVE-3785) Core hive changes for HiveServer2 implementation
Prasad Mujumdar created HIVE-3785: - Summary: Core hive changes for HiveServer2 implementation Key: HIVE-3785 URL: https://issues.apache.org/jira/browse/HIVE-3785 Project: Hive Issue Type: Sub-task Components: Authentication, Build Infrastructure, Configuration, Thrift API Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar The subtask to track changes in the core hive components for HiveServer2 implementation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3785) Core hive changes for HiveServer2 implementation
[ https://issues.apache.org/jira/browse/HIVE-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3785: -- Attachment: HS2-changed-files-only.patch Core hive changes for HiveServer2 implementation Key: HIVE-3785 URL: https://issues.apache.org/jira/browse/HIVE-3785 Project: Hive Issue Type: Sub-task Components: Authentication, Build Infrastructure, Configuration, Thrift API Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HS2-changed-files-only.patch The subtask to track changes in the core hive components for HiveServer2 implementation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3785) Core hive changes for HiveServer2 implementation
[ https://issues.apache.org/jira/browse/HIVE-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3785: -- Status: Patch Available (was: Open) Core hive changes for HiveServer2 implementation Key: HIVE-3785 URL: https://issues.apache.org/jira/browse/HIVE-3785 Project: Hive Issue Type: Sub-task Components: Authentication, Build Infrastructure, Configuration, Thrift API Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HS2-changed-files-only.patch The subtask to track changes in the core hive components for HiveServer2 implementation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2935) Implement HiveServer2
[ https://issues.apache.org/jira/browse/HIVE-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2935: -- Attachment: HS2-with-thrift-patch-rebased.patch HS2-changed-files-only.patch Implement HiveServer2 - Key: HIVE-2935 URL: https://issues.apache.org/jira/browse/HIVE-2935 Project: Hive Issue Type: New Feature Components: Server Infrastructure Reporter: Carl Steinbach Assignee: Carl Steinbach Labels: HiveServer2 Attachments: beelinepositive.tar.gz, HIVE-2935.1.notest.patch.txt, HIVE-2935.2.notest.patch.txt, HIVE-2935.2.nothrift.patch.txt, HS2-changed-files-only.patch, HS2-with-thrift-patch-rebased.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3764) Support metastore version consistency check
Prasad Mujumdar created HIVE-3764: - Summary: Support metastore version consistency check Key: HIVE-3764 URL: https://issues.apache.org/jira/browse/HIVE-3764 Project: Hive Issue Type: Improvement Components: Metastore Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Today there's no version/compatibility information stored in hive metastore. Also the datanucleus configuration property to automatically create missing tables is enabled by default. If you happen to start an older or newer hive or don't run the correct upgrade scripts during migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient to upgrade metastore when migrating to newer release. It's not supported with all databases. Besides the migration often involves altering existing table, changing or moving data etc. Hence it's very useful to have some consistency check to make sure that hive is using correct metastore and for production systems the schema is not automatically by running hive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3764) Support metastore version consistency check
[ https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3764: -- Attachment: HIVE-3764-1.patch Support metastore version consistency check --- Key: HIVE-3764 URL: https://issues.apache.org/jira/browse/HIVE-3764 Project: Hive Issue Type: Improvement Components: Metastore Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3764-1.patch Today there's no version/compatibility information stored in hive metastore. Also the datanucleus configuration property to automatically create missing tables is enabled by default. If you happen to start an older or newer hive or don't run the correct upgrade scripts during migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient to upgrade metastore when migrating to newer release. It's not supported with all databases. Besides the migration often involves altering existing table, changing or moving data etc. Hence it's very useful to have some consistency check to make sure that hive is using correct metastore and for production systems the schema is not automatically by running hive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3764) Support metastore version consistency check
[ https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3764: -- Fix Version/s: 0.10.0 Status: Patch Available (was: Open) The metastore version is set the in code and a new table is created in metastore to store it on the disk. The schema creation and upgrade scripts add the version string to the metastore. The version is verified while opening the metastore. A new property hive.metastore.schema.verification (disabled by default) is added to enable this verification. Setting this property also disables autoCreateSchema and enables fixedDataStore for datanucleus. Support metastore version consistency check --- Key: HIVE-3764 URL: https://issues.apache.org/jira/browse/HIVE-3764 Project: Hive Issue Type: Improvement Components: Metastore Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3764-1.patch Today there's no version/compatibility information stored in hive metastore. Also the datanucleus configuration property to automatically create missing tables is enabled by default. If you happen to start an older or newer hive or don't run the correct upgrade scripts during migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient to upgrade metastore when migrating to newer release. It's not supported with all databases. Besides the migration often involves altering existing table, changing or moving data etc. Hence it's very useful to have some consistency check to make sure that hive is using correct metastore and for production systems the schema is not automatically by running hive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3764) Support metastore version consistency check
[ https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508609#comment-13508609 ] Prasad Mujumdar commented on HIVE-3764: --- Code review request on https://reviews.apache.org/r/8314/ Support metastore version consistency check --- Key: HIVE-3764 URL: https://issues.apache.org/jira/browse/HIVE-3764 Project: Hive Issue Type: Improvement Components: Metastore Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3764-1.patch Today there's no version/compatibility information stored in hive metastore. Also the datanucleus configuration property to automatically create missing tables is enabled by default. If you happen to start an older or newer hive or don't run the correct upgrade scripts during migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient to upgrade metastore when migrating to newer release. It's not supported with all databases. Besides the migration often involves altering existing table, changing or moving data etc. Hence it's very useful to have some consistency check to make sure that hive is using correct metastore and for production systems the schema is not automatically by running hive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3764) Support metastore version consistency check
[ https://issues.apache.org/jira/browse/HIVE-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509144#comment-13509144 ] Prasad Mujumdar commented on HIVE-3764: --- @Asuthosh, Thanks for the comments. HiveServer2 patch already has a mechanism to extract the version. I didn't want to duplicate that again here, so its using a hardcoded version for time being. I will change it based on what that code. Support metastore version consistency check --- Key: HIVE-3764 URL: https://issues.apache.org/jira/browse/HIVE-3764 Project: Hive Issue Type: Improvement Components: Metastore Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3764-1.patch Today there's no version/compatibility information stored in hive metastore. Also the datanucleus configuration property to automatically create missing tables is enabled by default. If you happen to start an older or newer hive or don't run the correct upgrade scripts during migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient to upgrade metastore when migrating to newer release. It's not supported with all databases. Besides the migration often involves altering existing table, changing or moving data etc. Hence it's very useful to have some consistency check to make sure that hive is using correct metastore and for production systems the schema is not automatically by running hive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3742) The derby metastore schema script for 0.10.0 doesn't run
[ https://issues.apache.org/jira/browse/HIVE-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504051#comment-13504051 ] Prasad Mujumdar commented on HIVE-3742: --- @Ashutosh, thanks for catching that. Looks like this column INTEGER_IDX should included in the primary key of SKEWED_STRING_LIST_VALUES. Rest of the 0.10 schema scripts, mysql, oracle and postgres look fine. The derby metastore schema script for 0.10.0 doesn't run Key: HIVE-3742 URL: https://issues.apache.org/jira/browse/HIVE-3742 Project: Hive Issue Type: Bug Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3742-2.patch, HIVE-3742.patch The hive-schema-0.10.0.derby.sql contains incorrect alter statement for SKEWED_STRING_LIST which causes the script execution to fail -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3742) The derby metastore schema script for 0.10.0 doesn't run
[ https://issues.apache.org/jira/browse/HIVE-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3742: -- Attachment: HIVE-3742-2.patch Additional patch per review comment The derby metastore schema script for 0.10.0 doesn't run Key: HIVE-3742 URL: https://issues.apache.org/jira/browse/HIVE-3742 Project: Hive Issue Type: Bug Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3742-2.patch, HIVE-3742.patch The hive-schema-0.10.0.derby.sql contains incorrect alter statement for SKEWED_STRING_LIST which causes the script execution to fail -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3742) The derby metastore schema script for 0.10.0 doesn't run
Prasad Mujumdar created HIVE-3742: - Summary: The derby metastore schema script for 0.10.0 doesn't run Key: HIVE-3742 URL: https://issues.apache.org/jira/browse/HIVE-3742 Project: Hive Issue Type: Bug Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3742.patch The hive-schema-0.10.0.derby.sql contains incorrect alter statement for SKEWED_STRING_LIST which causes the script execution to fail -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3742) The derby metastore schema script for 0.10.0 doesn't run
[ https://issues.apache.org/jira/browse/HIVE-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3742: -- Attachment: HIVE-3742.patch The derby metastore schema script for 0.10.0 doesn't run Key: HIVE-3742 URL: https://issues.apache.org/jira/browse/HIVE-3742 Project: Hive Issue Type: Bug Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3742.patch The hive-schema-0.10.0.derby.sql contains incorrect alter statement for SKEWED_STRING_LIST which causes the script execution to fail -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3742) The derby metastore schema script for 0.10.0 doesn't run
[ https://issues.apache.org/jira/browse/HIVE-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3742: -- Status: Patch Available (was: Open) The derby metastore schema script for 0.10.0 doesn't run Key: HIVE-3742 URL: https://issues.apache.org/jira/browse/HIVE-3742 Project: Hive Issue Type: Bug Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3742.patch The hive-schema-0.10.0.derby.sql contains incorrect alter statement for SKEWED_STRING_LIST which causes the script execution to fail -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2693) Add DECIMAL data type
[ https://issues.apache.org/jira/browse/HIVE-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2693: -- Attachment: HIVE-2693-10.patch Here's the updated patch with test updates, additional patches for failed tests and JDBC support - There were a few tests still failing, like clientnegative/invalid_cast_from_binary_[1-6] which required out file updates. The patch 78 removed decimal round function which breaks things like round(int/int) and also round(decimal), so its added back. Also added JDBC support for handling decimal type data and metadata which was missing in Josh's original patch. I will log a separate ticket for HiveServer2 driver once both the patches are committed. I think the outstanding issue is the implicit type conversion for UDFs. Firstly this changes expressions like (int/int) from double to decimal. This could be a problem of existing clients like ODBC, perl and python which expect this to be a double. Besides this leads to inconsistent behavior on division by 0, for example 1.1/0.0 stays NaN but 1/0 throws exception since it gets promoted by division of decimal which behaves differently from double. The BigDecimal throws an exception in case of division by 0. I added a couple of patches and modified the udf_round_2 test so that it returns NULL (which is also MySQL default behavior). Perhaps we should change the other cases also to from NaN to NULL and support a configuration option to fall back to old behavior (which can be done in a separate patch). @Vikram, we can collaborate on this. You can add your new changes on top of it and update on reviewboard. Add DECIMAL data type - Key: HIVE-2693 URL: https://issues.apache.org/jira/browse/HIVE-2693 Project: Hive Issue Type: New Feature Components: Query Processor, Types Affects Versions: 0.10.0 Reporter: Carl Steinbach Assignee: Prasad Mujumdar Attachments: 2693_7.patch, 2693_8.patch, 2693_fix_all_tests1.patch, HIVE-2693-10.patch, HIVE-2693-1.patch.txt, HIVE-2693-all.patch, HIVE-2693-fix.patch, HIVE-2693.patch, HIVE-2693-take3.patch, HIVE-2693-take4.patch Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice template for how to do this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: HIVE-3563-7.patch Revised patch with cascade db drop fix in metastore client Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-3.patch, HIVE-3563-4.patch, HIVE-3563-6.patch, HIVE-3563-7.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3651) bucketmapjoin? tests fail with hadoop 0.23
Prasad Mujumdar created HIVE-3651: - Summary: bucketmapjoin? tests fail with hadoop 0.23 Key: HIVE-3651 URL: https://issues.apache.org/jira/browse/HIVE-3651 Project: Hive Issue Type: Bug Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar The hive.log show error in MR job - Task failed! Task ID: Stage-1 The job log has following error - 2012-11-01 15:51:20,253 WARN mapred.LocalJobRunner (LocalJobRunner.java:run(479)) - job_local_0001 java.lang.Exception: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:400) Caused by: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:161) at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54) at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334) at org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:232) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3651) bucketmapjoin? tests fail with hadoop 0.23
[ https://issues.apache.org/jira/browse/HIVE-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13489146#comment-13489146 ] Prasad Mujumdar commented on HIVE-3651: --- The problem is similar to HIVE-3257. The hashtable file prefix is causing the file name comparison to fail bucketmapjoin? tests fail with hadoop 0.23 -- Key: HIVE-3651 URL: https://issues.apache.org/jira/browse/HIVE-3651 Project: Hive Issue Type: Bug Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar The hive.log show error in MR job - Task failed! Task ID: Stage-1 The job log has following error - 2012-11-01 15:51:20,253 WARN mapred.LocalJobRunner (LocalJobRunner.java:run(479)) - job_local_0001 java.lang.Exception: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:400) Caused by: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:161) at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54) at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334) at org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:232) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3651) bucketmapjoin?.q tests fail with hadoop 0.23
[ https://issues.apache.org/jira/browse/HIVE-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3651: -- Summary: bucketmapjoin?.q tests fail with hadoop 0.23 (was: bucketmapjoin? tests fail with hadoop 0.23) bucketmapjoin?.q tests fail with hadoop 0.23 - Key: HIVE-3651 URL: https://issues.apache.org/jira/browse/HIVE-3651 Project: Hive Issue Type: Bug Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar The hive.log show error in MR job - Task failed! Task ID: Stage-1 The job log has following error - 2012-11-01 15:51:20,253 WARN mapred.LocalJobRunner (LocalJobRunner.java:run(479)) - job_local_0001 java.lang.Exception: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:400) Caused by: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:161) at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54) at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334) at org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:232) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3651) bucketmapjoin?.q tests fail with hadoop 0.23
[ https://issues.apache.org/jira/browse/HIVE-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3651: -- Attachment: HIVE-3651-1.patch bucketmapjoin?.q tests fail with hadoop 0.23 - Key: HIVE-3651 URL: https://issues.apache.org/jira/browse/HIVE-3651 Project: Hive Issue Type: Bug Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3651-1.patch The hive.log show error in MR job - Task failed! Task ID: Stage-1 The job log has following error - 2012-11-01 15:51:20,253 WARN mapred.LocalJobRunner (LocalJobRunner.java:run(479)) - job_local_0001 java.lang.Exception: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:400) Caused by: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:161) at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54) at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334) at org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:232) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3651) bucketmapjoin?.q tests fail with hadoop 0.23
[ https://issues.apache.org/jira/browse/HIVE-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3651: -- Status: Patch Available (was: Open) Review request on https://reviews.apache.org/r/7829/ bucketmapjoin?.q tests fail with hadoop 0.23 - Key: HIVE-3651 URL: https://issues.apache.org/jira/browse/HIVE-3651 Project: Hive Issue Type: Bug Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3651-1.patch The hive.log show error in MR job - Task failed! Task ID: Stage-1 The job log has following error - 2012-11-01 15:51:20,253 WARN mapred.LocalJobRunner (LocalJobRunner.java:run(479)) - job_local_0001 java.lang.Exception: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:400) Caused by: java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: /home/prasadm/repos/apache/hive-patches/build/ql/scratchdir/local/hive_2012-11-01_15-51-06_176_6704298995984162430/-local-10003/HashTable-Stage-1/MapJoin-b-11-srcbucket21.txt.hashtable (No such file or directory) at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:161) at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54) at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:399) at org.apache.hadoop.mapred.MapTask.run(MapTask.java:334) at org.apache.hadoop.mapred.LocalJobRunner$Job$MapTaskRunnable.run(LocalJobRunner.java:232) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: HIVE-3563-4.patch Rebased the patch Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-3.patch, HIVE-3563-4.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: HIVE-3563-6.patch Patch with test fixes Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-3.patch, HIVE-3563-4.patch, HIVE-3563-6.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: (was: HIVE-3563-1.patch) Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-3.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: HIVE-3563-3.patch Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-3.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483327#comment-13483327 ] Prasad Mujumdar commented on HIVE-3563: --- Attached the latest patch Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-3.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: (was: HIVE-3563-2.patch) Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-3.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: HIVE-3563-2.patch Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-1.patch, HIVE-3563-2.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13478218#comment-13478218 ] Prasad Mujumdar commented on HIVE-3563: --- Review request on https://reviews.apache.org/r/7517/ Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-1.patch, HIVE-3563-2.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Status: Patch Available (was: Open) Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-1.patch, HIVE-3563-2.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3213) ODBC API enhancements
[ https://issues.apache.org/jira/browse/HIVE-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3213: -- Status: Patch Available (was: Open) ODBC API enhancements - Key: HIVE-3213 URL: https://issues.apache.org/jira/browse/HIVE-3213 Project: Hive Issue Type: Sub-task Components: ODBC Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-1101-source.patch, HIVE-1101-source-with-thrift.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3213) ODBC API enhancements
[ https://issues.apache.org/jira/browse/HIVE-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13477151#comment-13477151 ] Prasad Mujumdar commented on HIVE-3213: --- Review request on https://reviews.apache.org/r/5685/ ODBC API enhancements - Key: HIVE-3213 URL: https://issues.apache.org/jira/browse/HIVE-3213 Project: Hive Issue Type: Sub-task Components: ODBC Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-1101-source.patch, HIVE-1101-source-with-thrift.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
Prasad Mujumdar created HIVE-3563: - Summary: Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Attachment: HIVE-3563-1.patch Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-1.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3563: -- Status: Patch Available (was: Open) Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-1.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3563) Drop database cascade fails when there are indexes on any tables
[ https://issues.apache.org/jira/browse/HIVE-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473572#comment-13473572 ] Prasad Mujumdar commented on HIVE-3563: --- Review request on https://reviews.apache.org/r/7517/ Drop database cascade fails when there are indexes on any tables Key: HIVE-3563 URL: https://issues.apache.org/jira/browse/HIVE-3563 Project: Hive Issue Type: Bug Components: Indexing, Metastore Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-3563-1.patch Drop database cascade fails if any of the table has index. create database db2; use db2; create table tab1 (id int, name string); create index idx1 on table tab1(id) as 'COMPACT' with DEFERRED REBUILD; drop database db2 cascade; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3100: -- Attachment: (was: HIVE-3100.patch) Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3100-9.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3100: -- Attachment: HIVE-3100-9.patch Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3100-9.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3100: -- Fix Version/s: 0.10.0 Status: Patch Available (was: Open) Attached the reviewed patch Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3100-9.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-975) Hive ODBC driver for Windows
[ https://issues.apache.org/jira/browse/HIVE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar reassigned HIVE-975: Assignee: Prasad Mujumdar Hive ODBC driver for Windows Key: HIVE-975 URL: https://issues.apache.org/jira/browse/HIVE-975 Project: Hive Issue Type: New Feature Components: Clients Environment: Windows Reporter: Carl Steinbach Assignee: Prasad Mujumdar The current Hive ODBC driver (HIVE-187) is limited to *NIX systems. We need to provide an ODBC driver that is compatible with Windows and the Windows ODBC driver manager. It appears that it may be possible to build the current unixODBC driver on Windows: http://mailman.unixodbc.org/pipermail/unixodbc-support/2008-June/001779.html The other blocker is THRIFT-591: Windows compatible Thrift C++ runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (HIVE-1101) Extend Hive ODBC to support more functions
[ https://issues.apache.org/jira/browse/HIVE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar reopened HIVE-1101: --- Assignee: Prasad Mujumdar (was: Ning Zhang) Extend Hive ODBC to support more functions -- Key: HIVE-1101 URL: https://issues.apache.org/jira/browse/HIVE-1101 Project: Hive Issue Type: New Feature Components: ODBC Reporter: Ning Zhang Assignee: Prasad Mujumdar Attachments: HIVE-1101.patch, unixODBC-2.2.14-p2-HIVE-1101.tar.gz Currently Hive ODBC driver only support a a minimum list of functions to ensure some application work. Some other applications require more function support. These functions include: *SQLCancel *SQLFetchScroll *SQLGetData *SQLGetInfo *SQLMoreResults *SQLRowCount *SQLSetConnectAtt *SQLSetStmtAttr *SQLEndTran *SQLPrepare *SQLNumParams *SQLDescribeParam *SQLBindParameter *SQLGetConnectAttr *SQLSetEnvAttr *SQLPrimaryKeys (not ODBC API? Hive does not support primary keys yet) *SQLForeignKeys (not ODBC API? Hive does not support foreign keys yet) We should support as many of them as possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1101) Extend Hive ODBC to support more functions
[ https://issues.apache.org/jira/browse/HIVE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-1101: -- Attachment: odbc-src.patch odbc-build.patch Initial patch of the ODBC driver with additional ODBC API support, ported on with Linux and window. Extend Hive ODBC to support more functions -- Key: HIVE-1101 URL: https://issues.apache.org/jira/browse/HIVE-1101 Project: Hive Issue Type: New Feature Components: ODBC Reporter: Ning Zhang Assignee: Prasad Mujumdar Attachments: HIVE-1101.patch, odbc-build.patch, odbc-src.patch, unixODBC-2.2.14-p2-HIVE-1101.tar.gz Currently Hive ODBC driver only support a a minimum list of functions to ensure some application work. Some other applications require more function support. These functions include: *SQLCancel *SQLFetchScroll *SQLGetData *SQLGetInfo *SQLMoreResults *SQLRowCount *SQLSetConnectAtt *SQLSetStmtAttr *SQLEndTran *SQLPrepare *SQLNumParams *SQLDescribeParam *SQLBindParameter *SQLGetConnectAttr *SQLSetEnvAttr *SQLPrimaryKeys (not ODBC API? Hive does not support primary keys yet) *SQLForeignKeys (not ODBC API? Hive does not support foreign keys yet) We should support as many of them as possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3212) ODBC build framework on Linux and windows
Prasad Mujumdar created HIVE-3212: - Summary: ODBC build framework on Linux and windows Key: HIVE-3212 URL: https://issues.apache.org/jira/browse/HIVE-3212 Project: Hive Issue Type: Sub-task Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3213) ODBC API enhancements
Prasad Mujumdar created HIVE-3213: - Summary: ODBC API enhancements Key: HIVE-3213 URL: https://issues.apache.org/jira/browse/HIVE-3213 Project: Hive Issue Type: Sub-task Components: ODBC Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3212) ODBC build framework on Linux and windows
[ https://issues.apache.org/jira/browse/HIVE-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3212: -- Component/s: ODBC ODBC build framework on Linux and windows - Key: HIVE-3212 URL: https://issues.apache.org/jira/browse/HIVE-3212 Project: Hive Issue Type: Sub-task Components: ODBC Affects Versions: 0.10.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400773#comment-13400773 ] Prasad Mujumdar commented on HIVE-3100: --- New Review request: https://reviews.apache.org/r/5554/ Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar Attachments: HIVE-3100.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3166) The Hive JDBC driver should accept hive conf and hive variables via connection URL
[ https://issues.apache.org/jira/browse/HIVE-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3166: -- Attachment: HIVE-3166-3.patch Attaching the reviewed patch The Hive JDBC driver should accept hive conf and hive variables via connection URL -- Key: HIVE-3166 URL: https://issues.apache.org/jira/browse/HIVE-3166 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3166-3.patch The JDBC driver supports running embedded hive. The Hive CLI can accept configuration and hive settings on command line that can be passed down. But the JDBC driver currently doesn't support this. Its also required for SQLLine CLI support since that is a JDBC application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3166) The Hive JDBC driver should accept hive conf and hive variables via connection URL
[ https://issues.apache.org/jira/browse/HIVE-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3166: -- Fix Version/s: 0.10.0 Affects Version/s: 0.9.0 Hadoop Flags: Reviewed Status: Patch Available (was: Open) The Hive JDBC driver should accept hive conf and hive variables via connection URL -- Key: HIVE-3166 URL: https://issues.apache.org/jira/browse/HIVE-3166 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.9.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.10.0 Attachments: HIVE-3166-3.patch The JDBC driver supports running embedded hive. The Hive CLI can accept configuration and hive settings on command line that can be passed down. But the JDBC driver currently doesn't support this. Its also required for SQLLine CLI support since that is a JDBC application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3166) The Hive JDBC driver should accept hive conf and hive variables via connection URL
Prasad Mujumdar created HIVE-3166: - Summary: The Hive JDBC driver should accept hive conf and hive variables via connection URL Key: HIVE-3166 URL: https://issues.apache.org/jira/browse/HIVE-3166 Project: Hive Issue Type: Bug Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar The JDBC driver supports running embedded hive. The Hive CLI can accept configuration and hive settings on command line that can be passed down. But the JDBC driver currently doesn't support this. Its also required for SQLLine CLI support since that is a JDBC application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3121) JDBC driver's getCatalogs() method returns schema/db information
[ https://issues.apache.org/jira/browse/HIVE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397391#comment-13397391 ] Prasad Mujumdar commented on HIVE-3121: --- Looks fine to me overall. A few minor comments/suggestions - getSchemaTerm() should return schema - getCatalogTerm() should return - I think it would be helpful to rename the getTableCatalog() in JdbcColumn and JdbcTable classes JDBC driver's getCatalogs() method returns schema/db information Key: HIVE-3121 URL: https://issues.apache.org/jira/browse/HIVE-3121 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.9.0 Reporter: Carl Steinbach Attachments: hive-3121.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3100: -- Attachment: HIVE-3100.patch Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar Attachments: HIVE-3100.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3100: -- Status: Patch Available (was: Open) Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar Attachments: HIVE-3100.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3100: -- Attachment: HIVE-3100.patch Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar Attachments: HIVE-3100.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3100) Add HiveCLI that runs over JDBC
[ https://issues.apache.org/jira/browse/HIVE-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-3100: -- Attachment: (was: HIVE-3100.patch) Add HiveCLI that runs over JDBC --- Key: HIVE-3100 URL: https://issues.apache.org/jira/browse/HIVE-3100 Project: Hive Issue Type: Bug Components: CLI, JDBC Reporter: Carl Steinbach Assignee: Prasad Mujumdar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2398) Hive server doesn't return schema for 'set' command
[ https://issues.apache.org/jira/browse/HIVE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2398: -- Attachment: HIVE-2398.patch.2 Hive server doesn't return schema for 'set' command --- Key: HIVE-2398 URL: https://issues.apache.org/jira/browse/HIVE-2398 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.7.1, 0.8.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-2398.patch, HIVE-2398.patch, HIVE-2398.patch.1, HIVE-2398.patch.2 The Hive server does process the CLI commands like 'set', 'set -v' sent by ODBC or JDBC clients. But currently only the data is returned to client but not schema for that resultset. This makes it unusable for a ODBC or JDBC client to use this option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2398) Hive server doesn't return schema for 'set' command
[ https://issues.apache.org/jira/browse/HIVE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2398: -- Attachment: HIVE-2398.patch.1 New patch that with changes per review comments. Hive server doesn't return schema for 'set' command --- Key: HIVE-2398 URL: https://issues.apache.org/jira/browse/HIVE-2398 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.7.1, 0.8.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-2398.patch, HIVE-2398.patch, HIVE-2398.patch.1 The Hive server does process the CLI commands like 'set', 'set -v' sent by ODBC or JDBC clients. But currently only the data is returned to client but not schema for that resultset. This makes it unusable for a ODBC or JDBC client to use this option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2398) Hive server doesn't return schema for 'set' command
[ https://issues.apache.org/jira/browse/HIVE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2398: -- Status: Patch Available (was: Open) HIVE-2398.patch.1 is the new patch Hive server doesn't return schema for 'set' command --- Key: HIVE-2398 URL: https://issues.apache.org/jira/browse/HIVE-2398 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.7.1, 0.8.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-2398.patch, HIVE-2398.patch, HIVE-2398.patch.1 The Hive server does process the CLI commands like 'set', 'set -v' sent by ODBC or JDBC clients. But currently only the data is returned to client but not schema for that resultset. This makes it unusable for a ODBC or JDBC client to use this option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2398) Hive server doesn't return schema for 'set' command
[ https://issues.apache.org/jira/browse/HIVE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2398: -- Attachment: HIVE-2398.patch Hive server doesn't return schema for 'set' command --- Key: HIVE-2398 URL: https://issues.apache.org/jira/browse/HIVE-2398 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.7.1, 0.8.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Attachments: HIVE-2398.patch, HIVE-2398.patch The Hive server does process the CLI commands like 'set', 'set -v' sent by ODBC or JDBC clients. But currently only the data is returned to client but not schema for that resultset. This makes it unusable for a ODBC or JDBC client to use this option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2398) Hive server doesn't return schema for 'set' command
Hive server doesn't return schema for 'set' command --- Key: HIVE-2398 URL: https://issues.apache.org/jira/browse/HIVE-2398 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.7.1, 0.8.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar The Hive server does process the CLI commands like 'set', 'set -v' sent by ODBC or JDBC clients. But currently only the data is returned to client but not schema for that resultset. This makes it unusable for a ODBC or JDBC client to use this option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2398) Hive server doesn't return schema for 'set' command
[ https://issues.apache.org/jira/browse/HIVE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2398: -- Fix Version/s: 0.8.0 Status: Patch Available (was: Open) Review request - https://reviews.apache.org/r/1605/ Hive server doesn't return schema for 'set' command --- Key: HIVE-2398 URL: https://issues.apache.org/jira/browse/HIVE-2398 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.7.1, 0.8.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.8.0 Attachments: HIVE-2398.patch The Hive server does process the CLI commands like 'set', 'set -v' sent by ODBC or JDBC clients. But currently only the data is returned to client but not schema for that resultset. This makes it unusable for a ODBC or JDBC client to use this option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2398) Hive server doesn't return schema for 'set' command
[ https://issues.apache.org/jira/browse/HIVE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Mujumdar updated HIVE-2398: -- Attachment: HIVE-2398.patch Hive server doesn't return schema for 'set' command --- Key: HIVE-2398 URL: https://issues.apache.org/jira/browse/HIVE-2398 Project: Hive Issue Type: Bug Components: Server Infrastructure Affects Versions: 0.7.1, 0.8.0 Reporter: Prasad Mujumdar Assignee: Prasad Mujumdar Fix For: 0.8.0 Attachments: HIVE-2398.patch The Hive server does process the CLI commands like 'set', 'set -v' sent by ODBC or JDBC clients. But currently only the data is returned to client but not schema for that resultset. This makes it unusable for a ODBC or JDBC client to use this option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2110) Hive Client is indefenitely waiting for reading from Socket
[
https://issues.apache.org/jira/browse/HIVE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Mujumdar updated HIVE-2110:
--
Fix Version/s: 0.8.0
Status: Patch Available (was: Open)
Hive Client is indefenitely waiting for reading from Socket
---
Key: HIVE-2110
URL: https://issues.apache.org/jira/browse/HIVE-2110
Project: Hive
Issue Type: Bug
Components: JDBC
Affects Versions: 0.5.0
Environment: Hadoop 0.20.1, Hive0.5.0 and SUSE Linux Enterprise
Server 10 SP2 (i586) - Kernel 2.6.16.60-0.21-smp (5).
Reporter: Chinna Rao Lalam
Assignee: Prasad Mujumdar
Fix For: 0.8.0
Hive Client is indefenitely waiting for reading from Socket. Thread dump i
added below.
Cause is:
In the HiveClient, when client socket is created, the read timeout is
mentioned is 0. So the socket will indefinetly wait when the machine where
Hive Server is running is shutdown or network is unplugged. The same may
not happen if the HiveServer alone is killed or gracefully shutdown. At this
time, client will get connection reset exception.
Code in HiveConnection
---
{noformat}
transport = new TSocket(host, port);
TProtocol protocol = new TBinaryProtocol(transport);
client = new HiveClient(protocol);
{noformat}
In the Client side, they send the query and wait for the response
send_execute(query,id); recv_execute(); // place where client waiting is
initiated
Thread dump:
{noformat}
main prio=10 tid=0x40111000 nid=0x3641 runnable [0x7f0d73f29000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
locked 0x7f0d5d3f0828 (a java.io.BufferedInputStream)
at
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:125)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:314)
at
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:262)
at
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:192)
at
org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:130)
at
org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:109)
locked 0x7f0d5d3f0878 (a org.apache.thrift.transport.TSocket)
at
org.apache.hadoop.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:218)
at
org.apache.hadoop.hive.jdbc.HiveStatement.execute(HiveStatement.java:154)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2110) Hive Client is indefenitely waiting for reading from Socket
[
https://issues.apache.org/jira/browse/HIVE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Mujumdar updated HIVE-2110:
--
Attachment: HIVE-2110.patch
Hive Client is indefenitely waiting for reading from Socket
---
Key: HIVE-2110
URL: https://issues.apache.org/jira/browse/HIVE-2110
Project: Hive
Issue Type: Bug
Components: JDBC
Affects Versions: 0.5.0
Environment: Hadoop 0.20.1, Hive0.5.0 and SUSE Linux Enterprise
Server 10 SP2 (i586) - Kernel 2.6.16.60-0.21-smp (5).
Reporter: Chinna Rao Lalam
Assignee: Prasad Mujumdar
Fix For: 0.8.0
Attachments: HIVE-2110.patch
Hive Client is indefenitely waiting for reading from Socket. Thread dump i
added below.
Cause is:
In the HiveClient, when client socket is created, the read timeout is
mentioned is 0. So the socket will indefinetly wait when the machine where
Hive Server is running is shutdown or network is unplugged. The same may
not happen if the HiveServer alone is killed or gracefully shutdown. At this
time, client will get connection reset exception.
Code in HiveConnection
---
{noformat}
transport = new TSocket(host, port);
TProtocol protocol = new TBinaryProtocol(transport);
client = new HiveClient(protocol);
{noformat}
In the Client side, they send the query and wait for the response
send_execute(query,id); recv_execute(); // place where client waiting is
initiated
Thread dump:
{noformat}
main prio=10 tid=0x40111000 nid=0x3641 runnable [0x7f0d73f29000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
locked 0x7f0d5d3f0828 (a java.io.BufferedInputStream)
at
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:125)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:314)
at
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:262)
at
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:192)
at
org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:130)
at
org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:109)
locked 0x7f0d5d3f0878 (a org.apache.thrift.transport.TSocket)
at
org.apache.hadoop.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:218)
at
org.apache.hadoop.hive.jdbc.HiveStatement.execute(HiveStatement.java:154)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-2110) Hive Client is indefenitely waiting for reading from Socket
[
https://issues.apache.org/jira/browse/HIVE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Mujumdar reassigned HIVE-2110:
-
Assignee: Prasad Mujumdar
Hive Client is indefenitely waiting for reading from Socket
---
Key: HIVE-2110
URL: https://issues.apache.org/jira/browse/HIVE-2110
Project: Hive
Issue Type: Bug
Components: JDBC
Affects Versions: 0.5.0
Environment: Hadoop 0.20.1, Hive0.5.0 and SUSE Linux Enterprise
Server 10 SP2 (i586) - Kernel 2.6.16.60-0.21-smp (5).
Reporter: Chinna Rao Lalam
Assignee: Prasad Mujumdar
Hive Client is indefenitely waiting for reading from Socket. Thread dump i
added below.
Cause is:
In the HiveClient, when client socket is created, the read timeout is
mentioned is 0. So the socket will indefinetly wait when the machine where
Hive Server is running is shutdown or network is unplugged. The same may
not happen if the HiveServer alone is killed or gracefully shutdown. At this
time, client will get connection reset exception.
Code in HiveConnection
---
{noformat}
transport = new TSocket(host, port);
TProtocol protocol = new TBinaryProtocol(transport);
client = new HiveClient(protocol);
{noformat}
In the Client side, they send the query and wait for the response
send_execute(query,id); recv_execute(); // place where client waiting is
initiated
Thread dump:
{noformat}
main prio=10 tid=0x40111000 nid=0x3641 runnable [0x7f0d73f29000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
locked 0x7f0d5d3f0828 (a java.io.BufferedInputStream)
at
org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:125)
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:314)
at
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:262)
at
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:192)
at
org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:130)
at
org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:109)
locked 0x7f0d5d3f0878 (a org.apache.thrift.transport.TSocket)
at
org.apache.hadoop.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:218)
at
org.apache.hadoop.hive.jdbc.HiveStatement.execute(HiveStatement.java:154)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
