[jira] [Updated] (HIVE-2748) Upgrade Hbase and ZK dependcies
[ https://issues.apache.org/jira/browse/HIVE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2748: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Patch committed to trunk. Thanks, Enis for your persistence on this one. Upgrade Hbase and ZK dependcies --- Key: HIVE-2748 URL: https://issues.apache.org/jira/browse/HIVE-2748 Project: Hive Issue Type: Task Affects Versions: 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.9.0 Reporter: Ashutosh Chauhan Assignee: Enis Soztutar Fix For: 0.9.0 Attachments: HIVE-2748.3.patch, HIVE-2748.D1431.1.patch, HIVE-2748.D1431.2.patch, HIVE-2748_v4.patch, HIVE-2748_v5.patch, HIVE-2748_v6.patch, HIVE-2748_v7.patch, HIVE-2748_v8.patch Both softwares have moved forward with significant improvements. Lets bump compile time dependency to keep up -- 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-2870) Throw an error when a nonexistent partition is accessed in strict mode
[ https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13229971#comment-13229971 ] Phabricator commented on HIVE-2870: --- akramer has commented on the revision HIVE-2870 [jira] Throw an error when a nonexistent partition is accessed in strict mode. ...is the clarification that this is a strict mode restriction automatically included in the error message? INLINE COMMENTS ql/src/java/org/apache/hadoop/hive/ql/parse/ErrorMsg.java:82 partitions should be plural REVISION DETAIL https://reviews.facebook.net/D2319 Throw an error when a nonexistent partition is accessed in strict mode -- Key: HIVE-2870 URL: https://issues.apache.org/jira/browse/HIVE-2870 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Lucian Adrian Grijincu Priority: Minor Attachments: HIVE-2870.D2319.1.patch Original Estimate: 24h Remaining Estimate: 24h When a table does not exist and someone tries to read from it in a query, Hive throws an error. But if a partition is directly accessed that does not exist, an error is not thrown. This is inconsistent and also leads to a lot of confused users who get no output. This task is to cause Hive to throw an error when the partition pruner for a query eliminates ALL existing partitions for some table when running in strict mode. -- 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-2870) Throw an error when a nonexistent partition is accessed in strict mode
[ https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13229976#comment-13229976 ] Phabricator commented on HIVE-2870: --- lucian has commented on the revision HIVE-2870 [jira] Throw an error when a nonexistent partition is accessed in strict mode. ...is the clarification that this is a strict mode restriction automatically included in the error message? No, but neither is it if for other strict-only errors: hive select * from tmp_table_with_partitions; FAILED: Error in semantic analysis: No partition predicate found for Alias tmp_table_with_partitions Table tmp_table_with_partitions hive select count(*) from tmp_table_with_partitions where ds=asdf; FAILED: Error in semantic analysis: No valid partition left after pruning for Alias tmp_table_with_partitions Table tmp_table_with_partitions I can change it, but I wanted to be consistent with that other one I tested. REVISION DETAIL https://reviews.facebook.net/D2319 Throw an error when a nonexistent partition is accessed in strict mode -- Key: HIVE-2870 URL: https://issues.apache.org/jira/browse/HIVE-2870 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Lucian Adrian Grijincu Priority: Minor Attachments: HIVE-2870.D2319.1.patch Original Estimate: 24h Remaining Estimate: 24h When a table does not exist and someone tries to read from it in a query, Hive throws an error. But if a partition is directly accessed that does not exist, an error is not thrown. This is inconsistent and also leads to a lot of confused users who get no output. This task is to cause Hive to throw an error when the partition pruner for a query eliminates ALL existing partitions for some table when running in strict mode. -- 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-2870) Throw an error when a nonexistent partition is accessed in strict mode
[ https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13229979#comment-13229979 ] Phabricator commented on HIVE-2870: --- lucian has commented on the revision HIVE-2870 [jira] Throw an error when a nonexistent partition is accessed in strict mode. I checked the error message list and I see other errors advertise the nonstrict mode in case the user really wants to run the operation. I'll change the message. REVISION DETAIL https://reviews.facebook.net/D2319 Throw an error when a nonexistent partition is accessed in strict mode -- Key: HIVE-2870 URL: https://issues.apache.org/jira/browse/HIVE-2870 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Lucian Adrian Grijincu Priority: Minor Attachments: HIVE-2870.D2319.1.patch Original Estimate: 24h Remaining Estimate: 24h When a table does not exist and someone tries to read from it in a query, Hive throws an error. But if a partition is directly accessed that does not exist, an error is not thrown. This is inconsistent and also leads to a lot of confused users who get no output. This task is to cause Hive to throw an error when the partition pruner for a query eliminates ALL existing partitions for some table when running in strict mode. -- 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-2778) Fail on table sampling
[
https://issues.apache.org/jira/browse/HIVE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Navis updated HIVE-2778:
Attachment: HIVE-2778.D1593.2.patch
Granted license to ASF.. Couldn't it be automated by phabricator?
Fail on table sampling
---
Key: HIVE-2778
URL: https://issues.apache.org/jira/browse/HIVE-2778
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.9.0
Environment: Reproduced only on hadoop-0.20.2-CDH3u1, work fine on
hadoop-0.20.2
Reporter: Navis
Assignee: Navis
Fix For: 0.9.0
Attachments: HIVE-2778.D1593.1.patch, HIVE-2778.D1593.2.patch,
HIVE-2778.D1593.2.patch
Trying table sampling on any non-empty table throws NPE. This does not occur
by test on mini-MR.
{noformat}
select count(*) from emp tablesample (0.1 percent);
Total MapReduce jobs = 1
Launching Job 1 out of 1
Number of reduce tasks determined at compile time: 1
In order to change the average load for a reducer (in bytes):
set hive.exec.reducers.bytes.per.reducer=number
In order to limit the maximum number of reducers:
set hive.exec.reducers.max=number
In order to set a constant number of reducers:
set mapred.reduce.tasks=number
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.sampleSplits(CombineHiveInputFormat.java:450)
at
org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.getSplits(CombineHiveInputFormat.java:403)
at org.apache.hadoop.mapred.JobClient.writeOldSplits(JobClient.java:971)
at org.apache.hadoop.mapred.JobClient.writeSplits(JobClient.java:963)
at org.apache.hadoop.mapred.JobClient.access$500(JobClient.java:170)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:880)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:833)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
at
org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:833)
at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:807)
at
org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:432)
at
org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:136)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:134)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1332)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1123)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:931)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:255)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:186)
Job Submission failed with exception 'java.lang.NullPointerException(null)'
FAILED: Execution Error, return code 1 from
org.apache.hadoop.hive.ql.exec.MapRedTask
{noformat}
--
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-2748) Upgrade Hbase and ZK dependcies
[ https://issues.apache.org/jira/browse/HIVE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230089#comment-13230089 ] Hudson commented on HIVE-2748: -- Integrated in Hive-trunk-h0.21 #1310 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1310/]) HIVE-2748: Upgrade Hbase and ZK dependcies (enis via hashutosh) (Revision 1300818) Result = SUCCESS hashutosh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1300818 Files : * /hive/trunk/hbase-handler/ivy.xml * /hive/trunk/hbase-handler/src/test/org/apache/hadoop/hive/hbase/HBaseTestSetup.java * /hive/trunk/ivy/ivysettings.xml * /hive/trunk/ivy/libraries.properties * /hive/trunk/shims/ivy.xml * /hive/trunk/shims/src/common-secure/java/org/apache/hadoop/hive/thrift/DelegationTokenStore.java * /hive/trunk/shims/src/common-secure/java/org/apache/hadoop/hive/thrift/MemoryTokenStore.java * /hive/trunk/shims/src/common-secure/java/org/apache/hadoop/hive/thrift/ZooKeeperTokenStore.java * /hive/trunk/shims/src/test/org/apache/hadoop/hive/thrift/TestZooKeeperTokenStore.java Upgrade Hbase and ZK dependcies --- Key: HIVE-2748 URL: https://issues.apache.org/jira/browse/HIVE-2748 Project: Hive Issue Type: Task Affects Versions: 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.9.0 Reporter: Ashutosh Chauhan Assignee: Enis Soztutar Fix For: 0.9.0 Attachments: HIVE-2748.3.patch, HIVE-2748.D1431.1.patch, HIVE-2748.D1431.2.patch, HIVE-2748_v4.patch, HIVE-2748_v5.patch, HIVE-2748_v6.patch, HIVE-2748_v7.patch, HIVE-2748_v8.patch Both softwares have moved forward with significant improvements. Lets bump compile time dependency to keep up -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2871: -- Attachment: HIVE-2871.D2331.1.patch kevinwilfong requested code review of HIVE-2871 [jira] Add a new hook to run at the beginning and end of the Driver.run method. Reviewers: JIRA https://issues.apache.org/jira/browse/HIVE-2871 Added a new hook which runs at the beginning and end of the Driver.run method. It has pre and post execution methods. I do not provide any implementations as part of this diff. Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. TEST PLAN EMPTY REVISION DETAIL https://reviews.facebook.net/D2331 AFFECTED FILES common/src/java/org/apache/hadoop/hive/conf/HiveConf.java ql/src/test/results/clientpositive/hook_order.q.out ql/src/test/org/apache/hadoop/hive/ql/hooks/VerifyHooksRunInOrder.java ql/src/test/queries/clientpositive/hook_order.q ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHook.java ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContextImpl.java ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContext.java ql/src/java/org/apache/hadoop/hive/ql/Driver.java MANAGE HERALD DIFFERENTIAL RULES https://reviews.facebook.net/herald/view/differential/ WHY DID I GET THIS EMAIL? https://reviews.facebook.net/herald/transcript/5163/ Tip: use the X-Herald-Rules header to filter Herald messages in your client. Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-2871: Status: Patch Available (was: Open) Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2870) Throw an error when a nonexistent partition is accessed in strict mode
[ https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230383#comment-13230383 ] Phabricator commented on HIVE-2870: --- akramer has requested changes to the revision HIVE-2870 [jira] Throw an error when a nonexistent partition is accessed in strict mode. I checked the error message list and I see other errors advertise the nonstrict mode in case the user really wants to run the operation. I'll change the message. Thanks. It is always better to do something right than wrong. Consistency only matter when there are multiple right things to do or no right thing to do. REVISION DETAIL https://reviews.facebook.net/D2319 BRANCH HIVE-2870-dev-branch Throw an error when a nonexistent partition is accessed in strict mode -- Key: HIVE-2870 URL: https://issues.apache.org/jira/browse/HIVE-2870 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Lucian Adrian Grijincu Priority: Minor Attachments: HIVE-2870.D2319.1.patch Original Estimate: 24h Remaining Estimate: 24h When a table does not exist and someone tries to read from it in a query, Hive throws an error. But if a partition is directly accessed that does not exist, an error is not thrown. This is inconsistent and also leads to a lot of confused users who get no output. This task is to cause Hive to throw an error when the partition pruner for a query eliminates ALL existing partitions for some table when running in strict mode. -- 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-2872) Store which configs the user has explicitly changed
Store which configs the user has explicitly changed --- Key: HIVE-2872 URL: https://issues.apache.org/jira/browse/HIVE-2872 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong It would be useful to keep track of which config variables the user has explicitly changed from the values which are either default or loaded from hive-site.xml. These include config variables set using the hiveconf argument to the CLI, and via the SET command. This could be used to prevent Hive from changing a config variable which has been explicitly set by the user, and also potentially for logging to help with later debugging of failed queries. -- 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-2873) Qualifying a column name in an ORDER BY clause generates 'Error in semantic analysis'
Qualifying a column name in an ORDER BY clause generates 'Error in semantic analysis' - Key: HIVE-2873 URL: https://issues.apache.org/jira/browse/HIVE-2873 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.7.1 Environment: Linux Kernel-2.6.18-glibc-2.5 x86_64 64bit Reporter: Alex Piyevsky When I run the following SELECT: SELECT T1.f03int, SUM(T1.f05double) FROM b774winx86qa07_tmix91 T1 GROUP BY T1.f03int ORDER BY T1.f03int; It generates : (10) [42000] Query returned non-zero code: 10, cause: FAILED: Error in : semantic analysis: line 1:94 Invalid Table Alias or Column Reference T1 If I remove T1 qualifier from the ORDER BY clause (ORDER BY f03int) data is returned correctly. Please advise, am I using incorrect syntax? What is the proper syntax convetion for using a table qualifier with ORDER BY -- 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-2815) Filter pushdown in hbase for keys stored in binary format
[ https://issues.apache.org/jira/browse/HIVE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230431#comment-13230431 ] Phabricator commented on HIVE-2815: --- cwsteinbach has accepted the revision HIVE-2815 [jira] Filter pushdown in hbase for keys stored in binary format. +1. Will commit if tests pass. REVISION DETAIL https://reviews.facebook.net/D1875 BRANCH svn Filter pushdown in hbase for keys stored in binary format - Key: HIVE-2815 URL: https://issues.apache.org/jira/browse/HIVE-2815 Project: Hive Issue Type: Improvement Components: HBase Handler Affects Versions: 0.6.0, 0.7.0, 0.7.1, 0.8.0, 0.8.1 Reporter: Ashutosh Chauhan Assignee: Ashutosh Chauhan Fix For: 0.9.0 Attachments: HIVE-2815.D1875.1.patch, HIVE-2815.D1875.2.patch This patch enables filter pushdown for keys stored in binary format in hbase -- 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-2856) Fix TestCliDriver escape1.q failure on MR2
[ https://issues.apache.org/jira/browse/HIVE-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-2856: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to trunk. Thanks Zhenxiao! Fix TestCliDriver escape1.q failure on MR2 -- Key: HIVE-2856 URL: https://issues.apache.org/jira/browse/HIVE-2856 Project: Hive Issue Type: Bug Components: Query Processor, Tests Affects Versions: 0.8.0 Reporter: Zhenxiao Luo Assignee: Zhenxiao Luo Fix For: 0.9.0 Attachments: HIVE-2856.1.patch.txt, HIVE-2856.2.patch.txt, escape1.q.out, escape1.q.out, escape2.q.out Additional '^' in escape test: [junit] Begin query: escape1.q [junit] Copying file: file:/home/cloudera/Code/hive/data/files/escapetest.txt [junit] 12/01/23 15:22:15 WARN conf.Configuration: mapred.system.dir is deprecated. Instead, use mapreduce.jobtracker.system.dir [junit] 12/01/23 15:22:15 WARN conf.Configuration: mapred.local.dir is deprecated. Instead, use mapreduce.cluster.local.dir [junit] diff -a -I file: -I pfile: -I hdfs: -I /tmp/ -I invalidscheme: -I lastUpdateTime -I lastAccessTime -I [Oo]wner -I CreateTime -I LastAccessTime -I Location -I LOCATION ' -I transient_lastDdlTime -I last_modified_ -I java.lang.RuntimeException -I at org -I at sun -I at java -I at junit -I Caused by: -I LOCK_QUERYID: -I LOCK_TIME: -I grantTime -I [.][.][.] [0-9]* more -I job_[0-9]*_[0-9]* -I USING 'java -cp /home/cloudera/Code/hive/build/ql/test/logs/clientpositive/escape1.q.out /home/cloudera/Code/hive/ql/src/test/results/clientpositive/escape1.q.out [junit] 893d892 [junit] 1 1 ^ [junit] junit.framework.AssertionFailedError: Client execution results failed with error code = 1 [junit] See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. [junit] at junit.framework.Assert.fail(Assert.java:50) [junit] at org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_escape1(TestCliDriver.java:131) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] at java.lang.reflect.Method.invoke(Method.java:616) [junit] at junit.framework.TestCase.runTest(TestCase.java:168) [junit] at junit.framework.TestCase.runBare(TestCase.java:134) [junit] at junit.framework.TestResult$1.protect(TestResult.java:110) [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [junit] at junit.framework.TestResult.run(TestResult.java:113) [junit] at junit.framework.TestCase.run(TestCase.java:124) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:243) [junit] at junit.framework.TestSuite.run(TestSuite.java:238) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768) [junit] Exception: Client execution results failed with error code = 1 [junit] See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. [junit] See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs.) -- 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-2819) Closed range scans on hbase keys
[ https://issues.apache.org/jira/browse/HIVE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230462#comment-13230462 ] Phabricator commented on HIVE-2819: --- cwsteinbach has accepted the revision HIVE-2819 [jira] Closed range scans on hbase keys. +1. Will commit if tests pass. INLINE COMMENTS hbase-handler/src/java/org/apache/hadoop/hive/hbase/HBaseStorageHandler.java:305 I think this is a little easier to read when rewritten as: if (scSize 1 || 2 scSize) REVISION DETAIL https://reviews.facebook.net/D1923 BRANCH 2818 Closed range scans on hbase keys - Key: HIVE-2819 URL: https://issues.apache.org/jira/browse/HIVE-2819 Project: Hive Issue Type: Improvement Components: HBase Handler Reporter: Ashutosh Chauhan Assignee: Ashutosh Chauhan Attachments: HIVE-2819.D1923.1.patch This patch pushes range scans on keys of closed form into hbase -- 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-2819) Closed range scans on hbase keys
[ https://issues.apache.org/jira/browse/HIVE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-2819: - Component/s: HBase Handler Closed range scans on hbase keys - Key: HIVE-2819 URL: https://issues.apache.org/jira/browse/HIVE-2819 Project: Hive Issue Type: Improvement Components: HBase Handler Reporter: Ashutosh Chauhan Assignee: Ashutosh Chauhan Attachments: HIVE-2819.D1923.1.patch This patch pushes range scans on keys of closed form into hbase -- 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-2819) Closed range scans on hbase keys
[ https://issues.apache.org/jira/browse/HIVE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230466#comment-13230466 ] Phabricator commented on HIVE-2819: --- cwsteinbach has requested changes to the revision HIVE-2819 [jira] Closed range scans on hbase keys. Patch needs to be rebased. REVISION DETAIL https://reviews.facebook.net/D1923 BRANCH 2818 Closed range scans on hbase keys - Key: HIVE-2819 URL: https://issues.apache.org/jira/browse/HIVE-2819 Project: Hive Issue Type: Improvement Components: HBase Handler Reporter: Ashutosh Chauhan Assignee: Ashutosh Chauhan Attachments: HIVE-2819.D1923.1.patch This patch pushes range scans on keys of closed form into hbase -- 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
Hive-0.8.1-SNAPSHOT-h0.21 - Build # 223 - Fixed
Changes for Build #222 Changes for Build #223 All tests passed The Apache Jenkins build system has built Hive-0.8.1-SNAPSHOT-h0.21 (build #223) Status: Fixed Check console output at https://builds.apache.org/job/Hive-0.8.1-SNAPSHOT-h0.21/223/ to view the results.
[jira] [Updated] (HIVE-2809) StorageHandler authorization providers
[ https://issues.apache.org/jira/browse/HIVE-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2809: -- Attachment: HIVE-2809.D1953.5.patch enis updated the revision HIVE-2809 [jira] StorageHandler authorization providers. Reviewers: JIRA Updated the patch for trunk, and fixed a possible NPE in HdfsAP. REVISION DETAIL https://reviews.facebook.net/D1953 AFFECTED FILES contrib/src/java/org/apache/hadoop/hive/contrib/metastore/hooks/TestURLHook.java contrib/src/test/queries/clientnegative/url_hook.q contrib/src/test/results/clientnegative/url_hook.q.out contrib/src/test/results/clientpositive/fileformat_base64.q.out contrib/src/test/results/clientpositive/serde_s3.q.out hbase-handler/src/java/org/apache/hadoop/hive/hbase/HBaseAuthorizationProvider.java hbase-handler/src/java/org/apache/hadoop/hive/hbase/HBaseStorageHandler.java hbase-handler/src/test/results/hbase_binary_storage_queries.q.out hbase-handler/src/test/results/hbase_queries.q.out hbase-handler/src/test/results/hbase_stats.q.out hbase-handler/src/test/results/hbase_stats2.q.out metastore/src/test/org/apache/hadoop/hive/metastore/TestEmbeddedHiveMetaStore.java ql/src/java/org/apache/hadoop/hive/ql/Driver.java ql/src/java/org/apache/hadoop/hive/ql/exec/DDLTask.java ql/src/java/org/apache/hadoop/hive/ql/hooks/Entity.java ql/src/java/org/apache/hadoop/hive/ql/hooks/ReadEntity.java ql/src/java/org/apache/hadoop/hive/ql/hooks/WriteEntity.java ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java ql/src/java/org/apache/hadoop/hive/ql/plan/HiveOperation.java ql/src/java/org/apache/hadoop/hive/ql/security/authorization/DefaultHiveAuthorizationProvider.java ql/src/java/org/apache/hadoop/hive/ql/security/authorization/HdfsAuthorizationProvider.java ql/src/java/org/apache/hadoop/hive/ql/security/authorization/HiveAuthorizationProviderBase.java ql/src/java/org/apache/hadoop/hive/ql/security/authorization/StorageDelegationAuthorizationProvider.java ql/src/test/org/apache/hadoop/hive/ql/security/authorization/AuthTestUtils.java ql/src/test/org/apache/hadoop/hive/ql/security/authorization/TestHdfsAuthorizationProvider.java ql/src/test/queries/clientnegative/authorization_fail_5.q ql/src/test/queries/clientnegative/authorization_part.q ql/src/test/queries/clientpositive/alter_rename_partition_authorization.q ql/src/test/queries/clientpositive/exim_23_import_part_authsuccess.q ql/src/test/results/clientnegative/addpart1.q.out ql/src/test/results/clientnegative/authorization_fail_5.q.out ql/src/test/results/clientnegative/authorization_part.q.out ql/src/test/results/clientnegative/database_drop_not_empty.q.out ql/src/test/results/clientnegative/database_drop_not_empty_restrict.q.out ql/src/test/results/clientnegative/drop_partition_failure.q.out ql/src/test/results/clientnegative/exim_01_nonpart_over_loaded.q.out ql/src/test/results/clientnegative/exim_02_all_part_over_overlap.q.out ql/src/test/results/clientnegative/exim_03_nonpart_noncompat_colschema.q.out ql/src/test/results/clientnegative/exim_04_nonpart_noncompat_colnumber.q.out ql/src/test/results/clientnegative/exim_05_nonpart_noncompat_coltype.q.out ql/src/test/results/clientnegative/exim_06_nonpart_noncompat_storage.q.out ql/src/test/results/clientnegative/exim_07_nonpart_noncompat_ifof.q.out ql/src/test/results/clientnegative/exim_08_nonpart_noncompat_serde.q.out ql/src/test/results/clientnegative/exim_09_nonpart_noncompat_serdeparam.q.out ql/src/test/results/clientnegative/exim_10_nonpart_noncompat_bucketing.q.out ql/src/test/results/clientnegative/exim_11_nonpart_noncompat_sorting.q.out ql/src/test/results/clientnegative/exim_13_nonnative_import.q.out ql/src/test/results/clientnegative/exim_14_nonpart_part.q.out ql/src/test/results/clientnegative/exim_15_part_nonpart.q.out ql/src/test/results/clientnegative/exim_16_part_noncompat_schema.q.out ql/src/test/results/clientnegative/exim_17_part_spec_underspec.q.out ql/src/test/results/clientnegative/exim_18_part_spec_missing.q.out ql/src/test/results/clientnegative/exim_19_external_over_existing.q.out ql/src/test/results/clientnegative/exim_20_managed_location_over_existing.q.out ql/src/test/results/clientnegative/exim_21_part_managed_external.q.out ql/src/test/results/clientnegative/exim_23_import_exist_authfail.q.out ql/src/test/results/clientnegative/exim_24_import_part_authfail.q.out ql/src/test/results/clientnegative/exim_25_import_nonexist_authfail.q.out ql/src/test/results/clientnegative/protectmode_part_no_drop.q.out ql/src/test/results/clientnegative/protectmode_tbl2.q.out ql/src/test/results/clientnegative/protectmode_tbl3.q.out ql/src/test/results/clientnegative/protectmode_tbl4.q.out ql/src/test/results/clientnegative/protectmode_tbl5.q.out
[jira] [Updated] (HIVE-2748) Upgrade Hbase and ZK dependcies
[ https://issues.apache.org/jira/browse/HIVE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated HIVE-2748: - Attachment: HIVE-2748.3-1.patch Version of patch 3 that uses 92.1-SNAPSHOT instead to deal with maven download issues. Upgrade Hbase and ZK dependcies --- Key: HIVE-2748 URL: https://issues.apache.org/jira/browse/HIVE-2748 Project: Hive Issue Type: Task Affects Versions: 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.9.0 Reporter: Ashutosh Chauhan Assignee: Enis Soztutar Fix For: 0.9.0 Attachments: HIVE-2748.3-1.patch, HIVE-2748.3.patch, HIVE-2748.D1431.1.patch, HIVE-2748.D1431.2.patch, HIVE-2748_v4.patch, HIVE-2748_v5.patch, HIVE-2748_v6.patch, HIVE-2748_v7.patch, HIVE-2748_v8.patch Both softwares have moved forward with significant improvements. Lets bump compile time dependency to keep up -- 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-2822) Add JSON output to the hive ddl commands
[
https://issues.apache.org/jira/browse/HIVE-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Gates updated HIVE-2822:
-
Attachment: HIVE-2822.05-branch0-8-1.patch
Version of patch 5 branch 8 that applies after HIVE-2748 patch 3-1.
Add JSON output to the hive ddl commands
Key: HIVE-2822
URL: https://issues.apache.org/jira/browse/HIVE-2822
Project: Hive
Issue Type: Improvement
Reporter: Chris Dean
Attachments: HIVE-2822.03-branch0-8.patch, HIVE-2822.03.patch,
HIVE-2822.03b.patch, HIVE-2822.04-branch-08.patch,
HIVE-2822.05-branch0-8-1.patch, HIVE-2822.05-branch0-8.patch,
HIVE-2822.05.patch, hive-json-01-branch0-8.patch, hive-json-01.patch,
hive-json-02-branch0-8.patch, hive-json-02.patch
The goal is to have an option to produce JSON output of the DDL commands that
is easily machine parseable.
For example, desc my_table currently gives
{noformat}
idbigint
user string
{noformat}
and we want to allow a json output:
{noformat}
{
columns: [
{name: id, type: bigint},
{name: user, type: string}
]
}
{noformat}
--
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-1634) Allow access to Primitive types stored in binary format in HBase
[ https://issues.apache.org/jira/browse/HIVE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Gates updated HIVE-1634: - Attachment: HIVE-1634.branch08.patch Version of the patch that applies to branch 0.8 after applying HIVE-2748 patch 3-1. Allow access to Primitive types stored in binary format in HBase Key: HIVE-1634 URL: https://issues.apache.org/jira/browse/HIVE-1634 Project: Hive Issue Type: Improvement Components: HBase Handler Affects Versions: 0.7.0, 0.8.0, 0.9.0 Reporter: Basab Maulik Assignee: Ashutosh Chauhan Fix For: 0.9.0 Attachments: HIVE-1634.0.patch, HIVE-1634.1.patch, HIVE-1634.D1581.1.patch, HIVE-1634.D1581.2.patch, HIVE-1634.D1581.3.patch, HIVE-1634.branch08.patch, TestHiveHBaseExternalTable.java, hive-1634_3.patch This addresses HIVE-1245 in part, for atomic or primitive types. The serde property hbase.columns.storage.types = -,b,b,b,b,b,b,b,b is a specification of the storage option for the corresponding column in the serde property hbase.columns.mapping. Allowed values are '-' for table default, 's' for standard string storage, and 'b' for binary storage as would be obtained from o.a.h.hbase.utils.Bytes. Map types for HBase column families use a colon separated pair such as 's:b' for the key and value part specifiers respectively. See the test cases and queries for HBase handler for additional examples. There is also a table property hbase.table.default.storage.type = string to specify a table level default storage type. The other valid specification is binary. The table level default is overridden by a column level specification. This control is available for the boolean, tinyint, smallint, int, bigint, float, and double primitive types. The attached patch also relaxes the mapping of map types to HBase column families to allow any primitive type to be the map key. Attached is a program for creating a table and populating it in HBase. The external table in Hive can access the data as shown in the example below. hive create external table TestHiveHBaseExternalTable (key string, c_bool boolean, c_byte tinyint, c_short smallint, c_int int, c_long bigint, c_string string, c_float float, c_double double) stored by 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' with serdeproperties (hbase.columns.mapping = :key,cf:boolean,cf:byte,cf:short,cf:int,cf:long,cf:string,cf:float,cf:double) tblproperties (hbase.table.name = TestHiveHBaseExternalTable); OK Time taken: 0.691 seconds hive select * from TestHiveHBaseExternalTable; OK key-1 NULLNULLNULLNULLNULLTest-String NULLNULL Time taken: 0.346 seconds hive drop table TestHiveHBaseExternalTable; OK Time taken: 0.139 seconds hive create external table TestHiveHBaseExternalTable (key string, c_bool boolean, c_byte tinyint, c_short smallint, c_int int, c_long bigint, c_string string, c_float float, c_double double) stored by 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' with serdeproperties ( hbase.columns.mapping = :key,cf:boolean,cf:byte,cf:short,cf:int,cf:long,cf:string,cf:float,cf:double, hbase.columns.storage.types = -,b,b,b,b,b,b,b,b ) tblproperties ( hbase.table.name = TestHiveHBaseExternalTable, hbase.table.default.storage.type = string); OK Time taken: 0.139 seconds hive select * from TestHiveHBaseExternalTable; OK key-1 true-128-32768 -2147483648 -9223372036854775808 Test-String -2.1793132E-11 2.01345E291 Time taken: 0.151 seconds hive drop table TestHiveHBaseExternalTable; OK Time taken: 0.154 seconds hive create external table TestHiveHBaseExternalTable (key string, c_bool boolean, c_byte tinyint, c_short smallint, c_int int, c_long bigint, c_string string, c_float float, c_double double) stored by 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' with serdeproperties ( hbase.columns.mapping = :key,cf:boolean,cf:byte,cf:short,cf:int,cf:long,cf:string,cf:float,cf:double, hbase.columns.storage.types = -,b,b,b,b,b,-,b,b ) tblproperties (hbase.table.name = TestHiveHBaseExternalTable); OK Time taken: 0.347 seconds hive select * from TestHiveHBaseExternalTable; OK key-1 true-128-32768 -2147483648 -9223372036854775808 Test-String -2.1793132E-11 2.01345E291 Time taken: 0.245 seconds hive -- 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-2870) Throw an error when a nonexistent partition is accessed in strict mode
[ https://issues.apache.org/jira/browse/HIVE-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2870: -- Attachment: HIVE-2870.D2319.2.patch lucian updated the revision HIVE-2870 [jira] Throw an error when a nonexistent partition is accessed in strict mode. Reviewers: JIRA, njain, kevinwilfong, akramer found that the error message was already present REVISION DETAIL https://reviews.facebook.net/D2319 AFFECTED FILES ql/src/java/org/apache/hadoop/hive/ql/optimizer/ppr/PartitionPruner.java Throw an error when a nonexistent partition is accessed in strict mode -- Key: HIVE-2870 URL: https://issues.apache.org/jira/browse/HIVE-2870 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Lucian Adrian Grijincu Priority: Minor Attachments: HIVE-2870.D2319.1.patch, HIVE-2870.D2319.2.patch Original Estimate: 24h Remaining Estimate: 24h When a table does not exist and someone tries to read from it in a query, Hive throws an error. But if a partition is directly accessed that does not exist, an error is not thrown. This is inconsistent and also leads to a lot of confused users who get no output. This task is to cause Hive to throw an error when the partition pruner for a query eliminates ALL existing partitions for some table when running in strict mode. -- 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-2874) Renaming external partition changes location
Renaming external partition changes location Key: HIVE-2874 URL: https://issues.apache.org/jira/browse/HIVE-2874 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Renaming an external partition will change the location of that partition to the default location of a managed partition with the same name. E.g. If ex_table is external and has partition part=1 with location /.../managed_table/part=1 Calling ALTER TABLE ex_table PARTITION (part = '1') RENAME TO PARTITION (part = '2'); Will change the location of the partition to /.../ex_table/part=2 -- 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-2875) Renaming partition changes partition location prefix
Renaming partition changes partition location prefix Key: HIVE-2875 URL: https://issues.apache.org/jira/browse/HIVE-2875 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Renaming a partition changes the location of the partition to the default location of the table, followed by the partition specification. It should just change the partition specification of the path. If the path does not end with the old partition specification, we should probably throw an exception because renaming a partition should not change the path so dramatically, and not changing the path to reflect the new partition name could leave the partition in a very confusing state. -- 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-2872) Store which configs the user has explicitly changed
[ https://issues.apache.org/jira/browse/HIVE-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230645#comment-13230645 ] Phabricator commented on HIVE-2872: --- njain has commented on the revision HIVE-2872 [jira] Store which configs the user has explicitly changed. Talked to Kevin offline - no need to add appliedSystemProperties in conf. Also, can you add a big comment in SessionState explaining overriddenConfigurations REVISION DETAIL https://reviews.facebook.net/D2337 Store which configs the user has explicitly changed --- Key: HIVE-2872 URL: https://issues.apache.org/jira/browse/HIVE-2872 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2872.D2337.1.patch It would be useful to keep track of which config variables the user has explicitly changed from the values which are either default or loaded from hive-site.xml. These include config variables set using the hiveconf argument to the CLI, and via the SET command. This could be used to prevent Hive from changing a config variable which has been explicitly set by the user, and also potentially for logging to help with later debugging of failed queries. -- 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-2872) Store which configs the user has explicitly changed
[ https://issues.apache.org/jira/browse/HIVE-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2872: - Status: Open (was: Patch Available) Store which configs the user has explicitly changed --- Key: HIVE-2872 URL: https://issues.apache.org/jira/browse/HIVE-2872 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2872.D2337.1.patch It would be useful to keep track of which config variables the user has explicitly changed from the values which are either default or loaded from hive-site.xml. These include config variables set using the hiveconf argument to the CLI, and via the SET command. This could be used to prevent Hive from changing a config variable which has been explicitly set by the user, and also potentially for logging to help with later debugging of failed queries. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2871: - Status: Open (was: Patch Available) Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230654#comment-13230654 ] Phabricator commented on HIVE-2871: --- njain has commented on the revision HIVE-2871 [jira] Add a new hook to run at the beginning and end of the Driver.run method. INLINE COMMENTS common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:578 We should explicitly state here that the hooks will be run in order. Also, add a comment in hive-default.xml.default explaining this ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContextImpl.java:25 Ado you want to add the sessionState also ? REVISION DETAIL https://reviews.facebook.net/D2331 Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2872) Store which configs the user has explicitly changed
[ https://issues.apache.org/jira/browse/HIVE-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-2872: Status: Patch Available (was: Open) Store which configs the user has explicitly changed --- Key: HIVE-2872 URL: https://issues.apache.org/jira/browse/HIVE-2872 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2872.D2337.1.patch, HIVE-2872.D2337.2.patch It would be useful to keep track of which config variables the user has explicitly changed from the values which are either default or loaded from hive-site.xml. These include config variables set using the hiveconf argument to the CLI, and via the SET command. This could be used to prevent Hive from changing a config variable which has been explicitly set by the user, and also potentially for logging to help with later debugging of failed queries. -- 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-2872) Store which configs the user has explicitly changed
[ https://issues.apache.org/jira/browse/HIVE-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2872: -- Attachment: HIVE-2872.D2337.2.patch kevinwilfong updated the revision HIVE-2872 [jira] Store which configs the user has explicitly changed. Reviewers: JIRA, njain Removed the mapping from HiveConf, created a new method which constructs the mapping of variables which have been set using System properties, which the SessionState uses instead. Also added the comment as requested. REVISION DETAIL https://reviews.facebook.net/D2337 AFFECTED FILES common/src/java/org/apache/hadoop/hive/conf/HiveConf.java cli/src/java/org/apache/hadoop/hive/cli/CliDriver.java ql/src/test/results/clientpositive/overridden_confs.q.out ql/src/test/org/apache/hadoop/hive/ql/hooks/VerifyOverriddenConfigsHook.java ql/src/test/queries/clientpositive/overridden_confs.q ql/src/java/org/apache/hadoop/hive/ql/session/SessionState.java ql/src/java/org/apache/hadoop/hive/ql/processors/SetProcessor.java Store which configs the user has explicitly changed --- Key: HIVE-2872 URL: https://issues.apache.org/jira/browse/HIVE-2872 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2872.D2337.1.patch, HIVE-2872.D2337.2.patch It would be useful to keep track of which config variables the user has explicitly changed from the values which are either default or loaded from hive-site.xml. These include config variables set using the hiveconf argument to the CLI, and via the SET command. This could be used to prevent Hive from changing a config variable which has been explicitly set by the user, and also potentially for logging to help with later debugging of failed queries. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2871: -- Attachment: HIVE-2871.D2331.2.patch kevinwilfong updated the revision HIVE-2871 [jira] Add a new hook to run at the beginning and end of the Driver.run method. Reviewers: JIRA, njain Expanded comment in HiveConf, and added entry in hive-default.xml.template REVISION DETAIL https://reviews.facebook.net/D2331 AFFECTED FILES conf/hive-default.xml.template common/src/java/org/apache/hadoop/hive/conf/HiveConf.java ql/src/test/results/clientpositive/hook_order.q.out ql/src/test/org/apache/hadoop/hive/ql/hooks/VerifyHooksRunInOrder.java ql/src/test/queries/clientpositive/hook_order.q ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHook.java ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContextImpl.java ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContext.java ql/src/java/org/apache/hadoop/hive/ql/Driver.java Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-2871: Status: Patch Available (was: Open) Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230683#comment-13230683 ] Phabricator commented on HIVE-2871: --- kevinwilfong has commented on the revision HIVE-2871 [jira] Add a new hook to run at the beginning and end of the Driver.run method. INLINE COMMENTS ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContextImpl.java:25 The reason I didn't add it is that in other hook contexts (HookContext and HiveSemanticAnalyzerHookContext) the SessionState is not included. Hooks can get it via SessionState.get() I don't really see the advantage of adding it, but if you feel strongly about this I can. REVISION DETAIL https://reviews.facebook.net/D2331 Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2835) Change default configuration for hive.exec.dynamic.partition
[ https://issues.apache.org/jira/browse/HIVE-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230704#comment-13230704 ] Phabricator commented on HIVE-2835: --- ashutoshc has accepted the revision HIVE-2835 [jira] Change default configuration for hive.exec.dynamic.partition. +1 Will commit if tests pass REVISION DETAIL https://reviews.facebook.net/D2157 BRANCH h-2835 Change default configuration for hive.exec.dynamic.partition Key: HIVE-2835 URL: https://issues.apache.org/jira/browse/HIVE-2835 Project: Hive Issue Type: Improvement Reporter: Owen O'Malley Assignee: Owen O'Malley Attachments: HIVE-2835.D2157.1.patch, HIVE-2835.D2157.2.patch I think we should enable dynamic partitions by default. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230756#comment-13230756 ] Namit Jain commented on HIVE-2871: -- +1 running tests Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230761#comment-13230761 ] Phabricator commented on HIVE-2871: --- njain has accepted the revision HIVE-2871 [jira] Add a new hook to run at the beginning and end of the Driver.run method. REVISION DETAIL https://reviews.facebook.net/D2331 BRANCH svn Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-2871: - Status: Open (was: Patch Available) Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230768#comment-13230768 ] Phabricator commented on HIVE-2871: --- njain has requested changes to the revision HIVE-2871 [jira] Add a new hook to run at the beginning and end of the Driver.run method. INLINE COMMENTS common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:34 Compile is failing, since these imports have been removed REVISION DETAIL https://reviews.facebook.net/D2331 BRANCH svn Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2872) Store which configs the user has explicitly changed
[ https://issues.apache.org/jira/browse/HIVE-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230772#comment-13230772 ] Phabricator commented on HIVE-2872: --- njain has accepted the revision HIVE-2872 [jira] Store which configs the user has explicitly changed. REVISION DETAIL https://reviews.facebook.net/D2337 BRANCH svn Store which configs the user has explicitly changed --- Key: HIVE-2872 URL: https://issues.apache.org/jira/browse/HIVE-2872 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2872.D2337.1.patch, HIVE-2872.D2337.2.patch It would be useful to keep track of which config variables the user has explicitly changed from the values which are either default or loaded from hive-site.xml. These include config variables set using the hiveconf argument to the CLI, and via the SET command. This could be used to prevent Hive from changing a config variable which has been explicitly set by the user, and also potentially for logging to help with later debugging of failed queries. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-2871: Status: Patch Available (was: Open) Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch, HIVE-2871.D2331.3.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2871: -- Attachment: HIVE-2871.D2331.3.patch kevinwilfong updated the revision HIVE-2871 [jira] Add a new hook to run at the beginning and end of the Driver.run method. Reviewers: JIRA, njain So sorry about that, my eclipse tends to remove imports if I haven't setup the build path properly. Ran ant clean package, so it should be good. REVISION DETAIL https://reviews.facebook.net/D2331 AFFECTED FILES conf/hive-default.xml.template common/src/java/org/apache/hadoop/hive/conf/HiveConf.java ql/src/test/results/clientpositive/hook_order.q.out ql/src/test/org/apache/hadoop/hive/ql/hooks/VerifyHooksRunInOrder.java ql/src/test/queries/clientpositive/hook_order.q ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHook.java ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContextImpl.java ql/src/java/org/apache/hadoop/hive/ql/HiveDriverRunHookContext.java ql/src/java/org/apache/hadoop/hive/ql/Driver.java Add a new hook to run at the beginning and end of the Driver.run method --- Key: HIVE-2871 URL: https://issues.apache.org/jira/browse/HIVE-2871 Project: Hive Issue Type: Improvement Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch, HIVE-2871.D2331.3.patch Driver.run is the highest level method which all queries go through, whether they come from Hive Server, the CLI, or any other entry. We also do not have any hooks before the compilation method is called, and having hooks in Driver.run would provide this. Having hooks in Driver.run will allow, for example, being able to overwrite config values used throughout query processing, including compilation, and at the other end, cleaning up any resources/logging any final values just before returning to the user. -- 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-2797) Make the IP address of a Thrift client available to HMSHandler.
[ https://issues.apache.org/jira/browse/HIVE-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230794#comment-13230794 ] Phabricator commented on HIVE-2797: --- ashutoshc has accepted the revision HIVE-2797 [jira] Make the IP address of a Thrift client available to HMSHandler.. Thanks for adding test-case, Kevin. +1 will commit if tests pass. REVISION DETAIL https://reviews.facebook.net/D1701 BRANCH svn Make the IP address of a Thrift client available to HMSHandler. --- Key: HIVE-2797 URL: https://issues.apache.org/jira/browse/HIVE-2797 Project: Hive Issue Type: Improvement Components: Metastore Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2797.D1701.1.patch, HIVE-2797.D1701.2.patch, HIVE-2797.D1701.3.patch, HIVE-2797.D1701.4.patch Currently, in unsecured mode, metastore Thrift calls are, from the HMSHandler's point of view, anonymous. If we expose the IP address of the Thrift client to the HMSHandler from the Processor, this will help to give some context, in particular for audit logging, of where the call is coming from. -- 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-2875) Renaming partition changes partition location prefix
[ https://issues.apache.org/jira/browse/HIVE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-2875: -- Attachment: HIVE-2875.D2349.1.patch kevinwilfong requested code review of HIVE-2875 [jira] Renaming partition changes partition location prefix. Reviewers: JIRA https://issues.apache.org/jira/browse/HIVE-2875 When a partition is renamed, instead of completely reconstructing the path, the partition specification at the end of the path is replaced with the new partition specification. If the old path for the partition did not end with the partition specification (it is some non default location) an error will be thrown, since we don't have a reasonable way to change the partition location. Renaming a partition changes the location of the partition to the default location of the table, followed by the partition specification. It should just change the partition specification of the path. If the path does not end with the old partition specification, we should probably throw an exception because renaming a partition should not change the path so dramatically, and not changing the path to reflect the new partition name could leave the partition in a very confusing state. TEST PLAN EMPTY REVISION DETAIL https://reviews.facebook.net/D2349 AFFECTED FILES metastore/src/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java ql/src/test/results/clientpositive/rename_partition_location.q.out ql/src/test/org/apache/hadoop/hive/ql/hooks/VerifyPartitionIsNotSubdirectoryOfTableHook.java ql/src/test/queries/clientpositive/rename_partition_location.q MANAGE HERALD DIFFERENTIAL RULES https://reviews.facebook.net/herald/view/differential/ WHY DID I GET THIS EMAIL? https://reviews.facebook.net/herald/transcript/5223/ Tip: use the X-Herald-Rules header to filter Herald messages in your client. Renaming partition changes partition location prefix Key: HIVE-2875 URL: https://issues.apache.org/jira/browse/HIVE-2875 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2875.D2349.1.patch Renaming a partition changes the location of the partition to the default location of the table, followed by the partition specification. It should just change the partition specification of the path. If the path does not end with the old partition specification, we should probably throw an exception because renaming a partition should not change the path so dramatically, and not changing the path to reflect the new partition name could leave the partition in a very confusing state. -- 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-2875) Renaming partition changes partition location prefix
[ https://issues.apache.org/jira/browse/HIVE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-2875: Status: Patch Available (was: Open) Renaming partition changes partition location prefix Key: HIVE-2875 URL: https://issues.apache.org/jira/browse/HIVE-2875 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-2875.D2349.1.patch Renaming a partition changes the location of the partition to the default location of the table, followed by the partition specification. It should just change the partition specification of the path. If the path does not end with the old partition specification, we should probably throw an exception because renaming a partition should not change the path so dramatically, and not changing the path to reflect the new partition name could leave the partition in a very confusing state. -- 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] [Resolved] (HIVE-2778) Fail on table sampling
[
https://issues.apache.org/jira/browse/HIVE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Steinbach resolved HIVE-2778.
--
Resolution: Fixed
Hadoop Flags: Reviewed
Committed to trunk. Thanks Navis!
Fail on table sampling
---
Key: HIVE-2778
URL: https://issues.apache.org/jira/browse/HIVE-2778
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.9.0
Environment: Reproduced only on hadoop-0.20.2-CDH3u1, work fine on
hadoop-0.20.2
Reporter: Navis
Assignee: Navis
Fix For: 0.9.0
Attachments: HIVE-2778.D1593.1.patch, HIVE-2778.D1593.2.patch,
HIVE-2778.D1593.2.patch
Trying table sampling on any non-empty table throws NPE. This does not occur
by test on mini-MR.
{noformat}
select count(*) from emp tablesample (0.1 percent);
Total MapReduce jobs = 1
Launching Job 1 out of 1
Number of reduce tasks determined at compile time: 1
In order to change the average load for a reducer (in bytes):
set hive.exec.reducers.bytes.per.reducer=number
In order to limit the maximum number of reducers:
set hive.exec.reducers.max=number
In order to set a constant number of reducers:
set mapred.reduce.tasks=number
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.sampleSplits(CombineHiveInputFormat.java:450)
at
org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.getSplits(CombineHiveInputFormat.java:403)
at org.apache.hadoop.mapred.JobClient.writeOldSplits(JobClient.java:971)
at org.apache.hadoop.mapred.JobClient.writeSplits(JobClient.java:963)
at org.apache.hadoop.mapred.JobClient.access$500(JobClient.java:170)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:880)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:833)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
at
org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:833)
at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:807)
at
org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:432)
at
org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:136)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:134)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1332)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1123)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:931)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:255)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:186)
Job Submission failed with exception 'java.lang.NullPointerException(null)'
FAILED: Execution Error, return code 1 from
org.apache.hadoop.hive.ql.exec.MapRedTask
{noformat}
--
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-2778) Fail on table sampling
[
https://issues.apache.org/jira/browse/HIVE-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230828#comment-13230828
]
Phabricator commented on HIVE-2778:
---
navis has committed the revision HIVE-2778 [jira] Fail on table sampling.
Change committed by cws.
REVISION DETAIL
https://reviews.facebook.net/D1593
COMMIT
https://reviews.facebook.net/rHIVE1301310
Fail on table sampling
---
Key: HIVE-2778
URL: https://issues.apache.org/jira/browse/HIVE-2778
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.9.0
Environment: Reproduced only on hadoop-0.20.2-CDH3u1, work fine on
hadoop-0.20.2
Reporter: Navis
Assignee: Navis
Fix For: 0.9.0
Attachments: HIVE-2778.D1593.1.patch, HIVE-2778.D1593.2.patch,
HIVE-2778.D1593.2.patch
Trying table sampling on any non-empty table throws NPE. This does not occur
by test on mini-MR.
{noformat}
select count(*) from emp tablesample (0.1 percent);
Total MapReduce jobs = 1
Launching Job 1 out of 1
Number of reduce tasks determined at compile time: 1
In order to change the average load for a reducer (in bytes):
set hive.exec.reducers.bytes.per.reducer=number
In order to limit the maximum number of reducers:
set hive.exec.reducers.max=number
In order to set a constant number of reducers:
set mapred.reduce.tasks=number
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.sampleSplits(CombineHiveInputFormat.java:450)
at
org.apache.hadoop.hive.ql.io.CombineHiveInputFormat.getSplits(CombineHiveInputFormat.java:403)
at org.apache.hadoop.mapred.JobClient.writeOldSplits(JobClient.java:971)
at org.apache.hadoop.mapred.JobClient.writeSplits(JobClient.java:963)
at org.apache.hadoop.mapred.JobClient.access$500(JobClient.java:170)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:880)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:833)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
at
org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:833)
at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:807)
at
org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:432)
at
org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:136)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:134)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1332)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1123)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:931)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:255)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:186)
Job Submission failed with exception 'java.lang.NullPointerException(null)'
FAILED: Execution Error, return code 1 from
org.apache.hadoop.hive.ql.exec.MapRedTask
{noformat}
--
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-2815) Filter pushdown in hbase for keys stored in binary format
[ https://issues.apache.org/jira/browse/HIVE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-2815: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed to trunk. Thanks Ashutosh! Filter pushdown in hbase for keys stored in binary format - Key: HIVE-2815 URL: https://issues.apache.org/jira/browse/HIVE-2815 Project: Hive Issue Type: Improvement Components: HBase Handler Affects Versions: 0.6.0, 0.7.0, 0.7.1, 0.8.0, 0.8.1 Reporter: Ashutosh Chauhan Assignee: Ashutosh Chauhan Fix For: 0.9.0 Attachments: HIVE-2815.D1875.1.patch, HIVE-2815.D1875.2.patch This patch enables filter pushdown for keys stored in binary format in hbase -- 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-2815) Filter pushdown in hbase for keys stored in binary format
[ https://issues.apache.org/jira/browse/HIVE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230846#comment-13230846 ] Phabricator commented on HIVE-2815: --- ashutoshc has committed the revision HIVE-2815 [jira] Filter pushdown in hbase for keys stored in binary format. Change committed by cws. REVISION DETAIL https://reviews.facebook.net/D1875 COMMIT https://reviews.facebook.net/rHIVE1301315 Filter pushdown in hbase for keys stored in binary format - Key: HIVE-2815 URL: https://issues.apache.org/jira/browse/HIVE-2815 Project: Hive Issue Type: Improvement Components: HBase Handler Affects Versions: 0.6.0, 0.7.0, 0.7.1, 0.8.0, 0.8.1 Reporter: Ashutosh Chauhan Assignee: Ashutosh Chauhan Fix For: 0.9.0 Attachments: HIVE-2815.D1875.1.patch, HIVE-2815.D1875.2.patch This patch enables filter pushdown for keys stored in binary format in hbase -- 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
Hive-trunk-h0.21 - Build # 1312 - Failure
Changes for Build #1312 [cws] HIVE-2856. Fix TestCliDriver escape1.q failure on MR2 (Zhenxiao Luo via cws) 2 tests failed. REGRESSION: org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1 Error Message: Unexpected exception See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. Stack Trace: junit.framework.AssertionFailedError: Unexpected exception See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. at junit.framework.Assert.fail(Assert.java:50) at org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1(TestNegativeCliDriver.java:10340) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906) REGRESSION: org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testNegativeCliDriver_minimr_broken_pipe Error Message: Unexpected exception See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. Stack Trace: junit.framework.AssertionFailedError: Unexpected exception See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. at junit.framework.Assert.fail(Assert.java:50) at org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testNegativeCliDriver_minimr_broken_pipe(TestNegativeMinimrCliDriver.java:117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906) The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1312) Status: Failure Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1312/ to view the results.
[jira] [Commented] (HIVE-2856) Fix TestCliDriver escape1.q failure on MR2
[ https://issues.apache.org/jira/browse/HIVE-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13230856#comment-13230856 ] Hudson commented on HIVE-2856: -- Integrated in Hive-trunk-h0.21 #1312 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1312/]) HIVE-2856. Fix TestCliDriver escape1.q failure on MR2 (Zhenxiao Luo via cws) (Revision 1301162) Result = FAILURE cws : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1301162 Files : * /hive/trunk/common/src/java/org/apache/hadoop/hive/common/FileUtils.java * /hive/trunk/ql/src/test/queries/clientpositive/escape1.q * /hive/trunk/ql/src/test/queries/clientpositive/escape2.q * /hive/trunk/ql/src/test/results/clientpositive/escape1.q.out * /hive/trunk/ql/src/test/results/clientpositive/escape2.q.out Fix TestCliDriver escape1.q failure on MR2 -- Key: HIVE-2856 URL: https://issues.apache.org/jira/browse/HIVE-2856 Project: Hive Issue Type: Bug Components: Query Processor, Tests Affects Versions: 0.8.0 Reporter: Zhenxiao Luo Assignee: Zhenxiao Luo Fix For: 0.9.0 Attachments: HIVE-2856.1.patch.txt, HIVE-2856.2.patch.txt, escape1.q.out, escape1.q.out, escape2.q.out Additional '^' in escape test: [junit] Begin query: escape1.q [junit] Copying file: file:/home/cloudera/Code/hive/data/files/escapetest.txt [junit] 12/01/23 15:22:15 WARN conf.Configuration: mapred.system.dir is deprecated. Instead, use mapreduce.jobtracker.system.dir [junit] 12/01/23 15:22:15 WARN conf.Configuration: mapred.local.dir is deprecated. Instead, use mapreduce.cluster.local.dir [junit] diff -a -I file: -I pfile: -I hdfs: -I /tmp/ -I invalidscheme: -I lastUpdateTime -I lastAccessTime -I [Oo]wner -I CreateTime -I LastAccessTime -I Location -I LOCATION ' -I transient_lastDdlTime -I last_modified_ -I java.lang.RuntimeException -I at org -I at sun -I at java -I at junit -I Caused by: -I LOCK_QUERYID: -I LOCK_TIME: -I grantTime -I [.][.][.] [0-9]* more -I job_[0-9]*_[0-9]* -I USING 'java -cp /home/cloudera/Code/hive/build/ql/test/logs/clientpositive/escape1.q.out /home/cloudera/Code/hive/ql/src/test/results/clientpositive/escape1.q.out [junit] 893d892 [junit] 1 1 ^ [junit] junit.framework.AssertionFailedError: Client execution results failed with error code = 1 [junit] See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. [junit] at junit.framework.Assert.fail(Assert.java:50) [junit] at org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_escape1(TestCliDriver.java:131) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] at java.lang.reflect.Method.invoke(Method.java:616) [junit] at junit.framework.TestCase.runTest(TestCase.java:168) [junit] at junit.framework.TestCase.runBare(TestCase.java:134) [junit] at junit.framework.TestResult$1.protect(TestResult.java:110) [junit] at junit.framework.TestResult.runProtected(TestResult.java:128) [junit] at junit.framework.TestResult.run(TestResult.java:113) [junit] at junit.framework.TestCase.run(TestCase.java:124) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:243) [junit] at junit.framework.TestSuite.run(TestSuite.java:238) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768) [junit] Exception: Client execution results failed with error code = 1 [junit] See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs. [junit] See build/ql/tmp/hive.log, or try ant test ... -Dtest.silent=false to get more logs.) -- 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-2828) make timestamp accessible in the hbase KeyValue
[
https://issues.apache.org/jira/browse/HIVE-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-2828:
--
Attachment: HIVE-2828.D1989.3.patch
navis updated the revision HIVE-2828 [jira] make timestamp accessible in the
hbase KeyValue.
Reviewers: JIRA
1. Rebased on trunk
2. Support string type for timestamp column
REVISION DETAIL
https://reviews.facebook.net/D1989
AFFECTED FILES
hbase-handler/src/java/org/apache/hadoop/hive/hbase/HBaseSerDe.java
hbase-handler/src/java/org/apache/hadoop/hive/hbase/HBaseStorageHandler.java
hbase-handler/src/java/org/apache/hadoop/hive/hbase/HiveHBaseTableInputFormat.java
hbase-handler/src/java/org/apache/hadoop/hive/hbase/LazyHBaseRow.java
hbase-handler/src/test/queries/hbase_timestamp.q
hbase-handler/src/test/results/hbase_timestamp.q.out
make timestamp accessible in the hbase KeyValue
Key: HIVE-2828
URL: https://issues.apache.org/jira/browse/HIVE-2828
Project: Hive
Issue Type: Improvement
Components: HBase Handler
Reporter: Navis
Assignee: Navis
Priority: Trivial
Attachments: HIVE-2828.D1989.1.patch, HIVE-2828.D1989.2.patch,
HIVE-2828.D1989.3.patch
Originated from HIVE-2781 and not accepted, but I think this could be helpful
to someone.
By using special column notation ':timestamp' in HBASE_COLUMNS_MAPPING, user
might access timestamp value in hbase KeyValue.
{code}
CREATE TABLE hbase_table (key int, value string, time timestamp)
STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
WITH SERDEPROPERTIES (hbase.columns.mapping = :key,cf:string,:timestamp)
{code}
--
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
Problem related to Hive using JDBC
Hi,
I am trying to implement a task in Hive like Stored Procedure in SQL.
In SQL, when we write cursor, first we execute select query and then
fetching the records we perform some actions.
Likely I have fired a select query as actions in Hive.
sql=select a,c,b from tbl_name;
res=stmt.executeQuery();--- CONTAINS 30 RECORDS
while(res.next())
{
sql=insert into tabl2. ;
rs1=stmt.executeQuery();
like wise many queries are there.
.
.
.
..
}
As my select query contans 30 records but when I execute it my
while(res.next()) execute only once.
I didn't get any kind of errors/exceptions
But instead of queries I just try to display field to check whether it is
fetching or not
then it is working fine.. (while loop contains only System.out.println
statements)
sql=select * from tbl_name;
res=stmt.executeQuery(sql);
while(res.next())
{
S.O.P.(fields : +res.getString(0));
}
Why it is happening I am not getting. Is anything I am doing wrong?
--
Regards,
Bhavesh Shah
