[jira] [Assigned] (HIVE-3099) add findbugs in build.xml
[ https://issues.apache.org/jira/browse/HIVE-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang reassigned HIVE-3099: --- Assignee: ransom.hezhiqiang add findbugs in build.xml - Key: HIVE-3099 URL: https://issues.apache.org/jira/browse/HIVE-3099 Project: Hive Issue Type: Improvement Components: Build Infrastructure Reporter: ransom.hezhiqiang Assignee: ransom.hezhiqiang Attachments: HIVE-3099-1.patch see HIVE-1172 and HIVE-2169 it was used default rules. exclude filter file is in findbugs\findbugs-exclude.xml the result of xml files to html file is not added because no style files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3101) dropTable will all ways excute hook.rollbackDropTable whether drop table success or faild.
[
https://issues.apache.org/jira/browse/HIVE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ransom.hezhiqiang reassigned HIVE-3101:
---
Assignee: ransom.hezhiqiang
dropTable will all ways excute hook.rollbackDropTable whether drop table
success or faild.
--
Key: HIVE-3101
URL: https://issues.apache.org/jira/browse/HIVE-3101
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: ransom.hezhiqiang
Assignee: ransom.hezhiqiang
Attachments: HIVE-3101.1.patch
see the codes:
boolean success = false;
try {
client.drop_table(dbname, name, deleteData);
if (hook != null) {
hook.commitDropTable(tbl, deleteData);
}
} catch (NoSuchObjectException e) {
if (!ignoreUknownTab) {
throw e;
}
} finally {
if (!success (hook != null)) {
hook.rollbackDropTable(tbl);
}
}
success will always false, whether the drop was success or faild.
so it's a bug.
--
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-2969) Log Time To Submit metric with PerfLogger
[ https://issues.apache.org/jira/browse/HIVE-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291626#comment-13291626 ] Hudson commented on HIVE-2969: -- Integrated in Hive-trunk-h0.21 #1474 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1474/]) HIVE-2969. Log Time To Submit metric with PerfLogger. (kevinwilfong reviewed by ashutoshc) (Revision 1347870) Result = FAILURE kevinwilfong : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1347870 Files : * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/Driver.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/log/PerfLogger.java Log Time To Submit metric with PerfLogger - Key: HIVE-2969 URL: https://issues.apache.org/jira/browse/HIVE-2969 Project: Hive Issue Type: Wish Components: Logging Affects Versions: 0.10.0 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Priority: Minor Attachments: HIVE-2969.D2919.1.patch Logging the time from when Driver.run starts to when we begin submitting jobs to map reduce would be helpful in determining how much of the lag in starting a query is due to Hive vs. Hadoop. -- 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 # 1474 - Still Failing
Changes for Build #1469 [ecapriolo] HIVE-2418 Translate/Replace UDF (Mark Grover via egc) Changes for Build #1470 [hashutosh] HIVE-2941: Hive should expand nested structs when setting the table schema from thrift structs (Travis Crawford via Ashutosh Chauhan) Changes for Build #1471 [cws] Oracle Metastore schema script doesn't include DDL for DN internal tables (Carl Steinbach via cws) Changes for Build #1472 Changes for Build #1473 Changes for Build #1474 [kevinwilfong] HIVE-2969. Log Time To Submit metric with PerfLogger. (kevinwilfong reviewed by ashutoshc) 1 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:10635) 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 #1474) Status: Still Failing Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1474/ to view the results.
[jira] [Commented] (HIVE-3099) add findbugs in build.xml
[ https://issues.apache.org/jira/browse/HIVE-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291783#comment-13291783 ] ransom.hezhiqiang commented on HIVE-3099: - please review it . thanks. add findbugs in build.xml - Key: HIVE-3099 URL: https://issues.apache.org/jira/browse/HIVE-3099 Project: Hive Issue Type: Improvement Components: Build Infrastructure Reporter: ransom.hezhiqiang Assignee: ransom.hezhiqiang Attachments: HIVE-3099-1.patch see HIVE-1172 and HIVE-2169 it was used default rules. exclude filter file is in findbugs\findbugs-exclude.xml the result of xml files to html file is not added because no style files. -- 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-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Attachment: HIVE-2933-trunk.1.patch.txt HIVE-2933-branch-0.9-1.patch.txt HIVE-2933-branch-0.8.1-3.patch.txt after my test. hive 0.9 and 0.10 also have this problems. so I create patchs for them. analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.8.1 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-0.8.1-2.patch, HIVE-2933-branch-0.8.1-3.patch.txt, HIVE-2933-branch-0.9-1.patch.txt, HIVE-2933-trunk.1.patch.txt analyze command throw NPE when table doesn't exists -- 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-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Affects Version/s: 0.10.0 0.9.0 Status: Patch Available (was: In Progress) analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.9.0, 0.8.1, 0.10.0 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-0.8.1-2.patch, HIVE-2933-branch-0.8.1-3.patch.txt, HIVE-2933-branch-0.9-1.patch.txt, HIVE-2933-trunk.1.patch.txt analyze command throw NPE when table doesn't exists -- 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-3101) dropTable will all ways excute hook.rollbackDropTable whether drop table success or faild.
[
https://issues.apache.org/jira/browse/HIVE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291809#comment-13291809
]
Edward Capriolo commented on HIVE-3101:
---
Can we create a unit test around this? Hooks should print during testing and
then we have some coverage here.
dropTable will all ways excute hook.rollbackDropTable whether drop table
success or faild.
--
Key: HIVE-3101
URL: https://issues.apache.org/jira/browse/HIVE-3101
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: ransom.hezhiqiang
Assignee: ransom.hezhiqiang
Attachments: HIVE-3101.1.patch
see the codes:
boolean success = false;
try {
client.drop_table(dbname, name, deleteData);
if (hook != null) {
hook.commitDropTable(tbl, deleteData);
}
} catch (NoSuchObjectException e) {
if (!ignoreUknownTab) {
throw e;
}
} finally {
if (!success (hook != null)) {
hook.rollbackDropTable(tbl);
}
}
success will always false, whether the drop was success or faild.
so it's a bug.
--
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-3101) dropTable will all ways excute hook.rollbackDropTable whether drop table success or faild.
[
https://issues.apache.org/jira/browse/HIVE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291812#comment-13291812
]
ransom.hezhiqiang commented on HIVE-3101:
-
the default hook is HBaseStorageHandler, it will be cover these codes when
create hbase table.
so i think we already have some unit test about hbase table in hive.
it doesn't need to create unit test.
if we need more test case, i will create it.
dropTable will all ways excute hook.rollbackDropTable whether drop table
success or faild.
--
Key: HIVE-3101
URL: https://issues.apache.org/jira/browse/HIVE-3101
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: ransom.hezhiqiang
Assignee: ransom.hezhiqiang
Attachments: HIVE-3101.1.patch
see the codes:
boolean success = false;
try {
client.drop_table(dbname, name, deleteData);
if (hook != null) {
hook.commitDropTable(tbl, deleteData);
}
} catch (NoSuchObjectException e) {
if (!ignoreUknownTab) {
throw e;
}
} finally {
if (!success (hook != null)) {
hook.rollbackDropTable(tbl);
}
}
success will always false, whether the drop was success or faild.
so it's a bug.
--
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-3101) dropTable will all ways excute hook.rollbackDropTable whether drop table success or faild.
[
https://issues.apache.org/jira/browse/HIVE-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291814#comment-13291814
]
Edward Capriolo commented on HIVE-3101:
---
I will review.
dropTable will all ways excute hook.rollbackDropTable whether drop table
success or faild.
--
Key: HIVE-3101
URL: https://issues.apache.org/jira/browse/HIVE-3101
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: ransom.hezhiqiang
Assignee: ransom.hezhiqiang
Attachments: HIVE-3101.1.patch
see the codes:
boolean success = false;
try {
client.drop_table(dbname, name, deleteData);
if (hook != null) {
hook.commitDropTable(tbl, deleteData);
}
} catch (NoSuchObjectException e) {
if (!ignoreUknownTab) {
throw e;
}
} finally {
if (!success (hook != null)) {
hook.rollbackDropTable(tbl);
}
}
success will always false, whether the drop was success or faild.
so it's a bug.
--
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 # 1475 - Still Failing
Changes for Build #1469 [ecapriolo] HIVE-2418 Translate/Replace UDF (Mark Grover via egc) Changes for Build #1470 [hashutosh] HIVE-2941: Hive should expand nested structs when setting the table schema from thrift structs (Travis Crawford via Ashutosh Chauhan) Changes for Build #1471 [cws] Oracle Metastore schema script doesn't include DDL for DN internal tables (Carl Steinbach via cws) Changes for Build #1472 Changes for Build #1473 Changes for Build #1474 [kevinwilfong] HIVE-2969. Log Time To Submit metric with PerfLogger. (kevinwilfong reviewed by ashutoshc) Changes for Build #1475 No tests ran. The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1475) Status: Still Failing Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1475/ to view the results.
Build failed in Jenkins: Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false #42
See https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/42/ -- [...truncated 5616 lines...] [ivy:resolve] [SUCCESSFUL ] net.sf.kosmosfs#kfs;0.3!kfs.jar (996ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/junit/junit/4.5/junit-4.5.jar ... [ivy:resolve] .. (194kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] junit#junit;4.5!junit.jar (1000ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/hsqldb/hsqldb/1.8.0.10/hsqldb-1.8.0.10.jar ... [ivy:resolve] ... (690kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] hsqldb#hsqldb;1.8.0.10!hsqldb.jar (1012ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/oro/oro/2.0.8/oro-2.0.8.jar ... [ivy:resolve] (63kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] oro#oro;2.0.8!oro.jar (1957ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/eclipse/jdt/core/3.1.1/core-3.1.1.jar ... [ivy:resolve] ... (3483kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.eclipse.jdt#core;3.1.1!core.jar (1200ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/ant/ant/1.6.5/ant-1.6.5.jar ... [ivy:resolve] (1009kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] ant#ant;1.6.5!ant.jar (1383ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar ... [ivy:resolve] (59kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] commons-logging#commons-logging;1.1.1!commons-logging.jar (1014ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/apache/ftpserver/ftplet-api/1.0.0/ftplet-api-1.0.0.jar ... [ivy:resolve] .. (22kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.apache.ftpserver#ftplet-api;1.0.0!ftplet-api.jar(bundle) (972ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/apache/mina/mina-core/2.0.0-M5/mina-core-2.0.0-M5.jar ... [ivy:resolve] (622kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.apache.mina#mina-core;2.0.0-M5!mina-core.jar(bundle) (1122ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/apache/ftpserver/ftpserver-core/1.0.0/ftpserver-core-1.0.0.jar ... [ivy:resolve] . (264kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.apache.ftpserver#ftpserver-core;1.0.0!ftpserver-core.jar(bundle) (1687ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/apache/ftpserver/ftpserver-deprecated/1.0.0-M2/ftpserver-deprecated-1.0.0-M2.jar ... [ivy:resolve] ... (31kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.apache.ftpserver#ftpserver-deprecated;1.0.0-M2!ftpserver-deprecated.jar (996ms) [ivy:resolve] downloading http://repo1.maven.org/maven2/org/slf4j/slf4j-api/1.5.2/slf4j-api-1.5.2.jar ... [ivy:resolve] .. (16kB) [ivy:resolve] .. (0kB) [ivy:resolve] [SUCCESSFUL ] org.slf4j#slf4j-api;1.5.2!slf4j-api.jar (1000ms) ivy-retrieve-hadoop-shim: [echo] Project: shims [javac] Compiling 16 source files to https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/42/artifact/hive/build/shims/classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/ws/hive/shims/src/0.20/java/org/apache/hadoop/hive/shims/Hadoop20Shims.java uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [echo] Building shims 0.20S build_shims: [echo] Project: shims [echo] Compiling https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/ws/hive/shims/src/common/java;/home/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/hive/shims/src/common-secure/java;/home/jenkins/jenkins-slave/workspace/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/hive/shims/src/0.20S/java against hadoop 1.0.0 (https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/42/artifact/hive/build/hadoopcore/hadoop-1.0.0) ivy-init-settings: [echo] Project: shims ivy-resolve-hadoop-shim: [echo] Project: shims [ivy:resolve] :: loading settings :: file = https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/ws/hive/ivy/ivysettings.xml [ivy:resolve] downloading http://repo1.maven.org/maven2/org/apache/hadoop/hadoop-core/1.0.0/hadoop-core-1.0.0.jar ... [ivy:resolve]
[jira] [Updated] (HIVE-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Affects Version/s: (was: 0.10.0) analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.8.1, 0.9.0 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-0.8.1-2.patch, HIVE-2933-branch-0.8.1-3.patch.txt, HIVE-2933-branch-0.9-1.patch.txt analyze command throw NPE when table doesn't exists -- 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-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Attachment: (was: HIVE-2933-trunk.1.patch.txt) analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.8.1, 0.9.0 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-0.8.1-2.patch, HIVE-2933-branch-0.8.1-3.patch.txt, HIVE-2933-branch-0.9-1.patch.txt analyze command throw NPE when table doesn't exists -- 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-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Attachment: (was: HIVE-2933-0.8.1-2.patch) analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.8.1, 0.9.0 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-branch-0.9-1.patch.txt analyze command throw NPE when table doesn't exists -- 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-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Status: Open (was: Patch Available) recommit it. analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.9.0, 0.8.1 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-branch-0.9-1.patch.txt, HIVE-2933.0.10-2.patch.txt, HIVE-2933.branch8.1-4.patch.txt analyze command throw NPE when table doesn't exists -- 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-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Affects Version/s: 0.10.0 Status: Patch Available (was: Open) analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.9.0, 0.8.1, 0.10.0 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-branch-0.9-1.patch.txt, HIVE-2933.0.10-2.patch.txt, HIVE-2933.branch8.1-4.patch.txt analyze command throw NPE when table doesn't exists -- 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-2933) analyze command throw NPE when table doesn't exists
[ https://issues.apache.org/jira/browse/HIVE-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ransom.hezhiqiang updated HIVE-2933: Attachment: HIVE-2933.branch8.1-4.patch.txt HIVE-2933.0.10-2.patch.txt add patchs for 0.8.1 and 0.10. all patchs was tested.please review it. analyze command throw NPE when table doesn't exists --- Key: HIVE-2933 URL: https://issues.apache.org/jira/browse/HIVE-2933 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.8.1, 0.9.0 Reporter: alex gemini Assignee: ransom.hezhiqiang Priority: Minor Attachments: HIVE-2933-branch-0.9-1.patch.txt, HIVE-2933.0.10-2.patch.txt, HIVE-2933.branch8.1-4.patch.txt analyze command throw NPE when table doesn't exists -- 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-2646) Hive Ivy dependencies on Hadoop should depend on jars directly, not tarballs
[ https://issues.apache.org/jira/browse/HIVE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291928#comment-13291928 ] Kanna Karanam commented on HIVE-2646: - I downloaded the Hadoop Hive source from apache and made some changes in Hadoop internally. Now I am trying to run hive unit tests against my changes (internal Hadoop). Are there any configuration settings in hive (unit tests) to configure and run against local Hadoop jars. Hive Ivy dependencies on Hadoop should depend on jars directly, not tarballs Key: HIVE-2646 URL: https://issues.apache.org/jira/browse/HIVE-2646 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.8.0 Reporter: Andrew Bayer Assignee: Andrew Bayer Priority: Critical Fix For: 0.10.0, 0.9.1 Attachments: HIVE-2646-fixtests.patch, HIVE-2646-fixtests.txt, HIVE-2646.D2133.1.patch, HIVE-2646.D2133.10.patch, HIVE-2646.D2133.11.patch, HIVE-2646.D2133.12.patch, HIVE-2646.D2133.13.patch, HIVE-2646.D2133.14.patch, HIVE-2646.D2133.15.patch, HIVE-2646.D2133.2.patch, HIVE-2646.D2133.3.patch, HIVE-2646.D2133.4.patch, HIVE-2646.D2133.5.patch, HIVE-2646.D2133.6.patch, HIVE-2646.D2133.7.patch, HIVE-2646.D2133.8.patch, HIVE-2646.D2133.9.patch, HIVE-2646.D2883.1.patch, HIVE-2646.D2883.2.patch, HIVE-2646.D2883.3.patch, HIVE-2646.diff.txt, HIVE-2646_LANG.patch The current Hive Ivy dependency logic for its Hadoop dependencies is problematic - depending on the tarball and extracting the jars from there, rather than depending on the jars directly. It'd be great if this was fixed to actually have the jar dependencies defined directly. -- 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-3105) HIVE-895 introduced build errors in Eclipse
Kevin Wilfong created HIVE-3105: --- Summary: HIVE-895 introduced build errors in Eclipse Key: HIVE-3105 URL: https://issues.apache.org/jira/browse/HIVE-3105 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Priority: Minor HIVE-895 added some more jars to ivy.xml, but did not add them to Eclipse's classpath causing the Eclipse build to fail. -- 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-3105) HIVE-895 introduced build errors in Eclipse
[ https://issues.apache.org/jira/browse/HIVE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3105: Attachment: HIVE-3105.1.patch.txt HIVE-895 introduced build errors in Eclipse --- Key: HIVE-3105 URL: https://issues.apache.org/jira/browse/HIVE-3105 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Priority: Minor Attachments: HIVE-3105.1.patch.txt HIVE-895 added some more jars to ivy.xml, but did not add them to Eclipse's classpath causing the Eclipse build to fail. -- 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-3105) HIVE-895 introduced build errors in Eclipse
[ https://issues.apache.org/jira/browse/HIVE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3105: Status: Patch Available (was: Open) HIVE-895 introduced build errors in Eclipse --- Key: HIVE-3105 URL: https://issues.apache.org/jira/browse/HIVE-3105 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Priority: Minor Attachments: HIVE-3105.1.patch.txt HIVE-895 added some more jars to ivy.xml, but did not add them to Eclipse's classpath causing the Eclipse build to fail. -- 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-3106) Add option to make multi inserts more atomic
Kevin Wilfong created HIVE-3106: --- Summary: Add option to make multi inserts more atomic Key: HIVE-3106 URL: https://issues.apache.org/jira/browse/HIVE-3106 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Kevin Wilfong Assignee: Kevin Wilfong Currently, with multi-insert queries as soon the output of one of the inserts is ready the move task associated with that insert is run, creating the table/partition. However, if concurrency is enabled the lock on this table/partition is not released until the entire query finishes, which can be much later. This causes issues if, for example, a user is waiting for an output of the multi-insert query which is created long before the other outputs, and checking for it's existence using the metastore's Thrift methods (get_table/get_partition). In which case, the user will run their query which uses the output, and it will experience a timeout trying to acquire the lock on the table/partition. If all the move tasks depend on the parent's of all other move tasks, the output creation will be much closer to atomic relieving this problem. -- 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-3013) TestCliDriver cannot be debugged with eclipse since hadoop_home is set wrongly
[ https://issues.apache.org/jira/browse/HIVE-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3013: - Attachment: HIVE-3013.3.patch.txt Attaching an updated version of that patch that allows you to set JVM arguments for Eclipse launch configurations. TestCliDriver cannot be debugged with eclipse since hadoop_home is set wrongly -- Key: HIVE-3013 URL: https://issues.apache.org/jira/browse/HIVE-3013 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.9.0 Reporter: Namit Jain Assignee: Carl Steinbach Attachments: HIVE-3013.2.patch.txt, HIVE-3013.3.patch.txt, hive.3013.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3105) HIVE-895 introduced build errors in Eclipse
[ https://issues.apache.org/jira/browse/HIVE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291974#comment-13291974 ] Carl Steinbach commented on HIVE-3105: -- @Kevin: This is a duplicate of HIVE-3013. Can you please review that patch? Thanks. HIVE-895 introduced build errors in Eclipse --- Key: HIVE-3105 URL: https://issues.apache.org/jira/browse/HIVE-3105 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Priority: Minor Attachments: HIVE-3105.1.patch.txt HIVE-895 added some more jars to ivy.xml, but did not add them to Eclipse's classpath causing the Eclipse build to fail. -- 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-3013) TestCliDriver cannot be debugged with eclipse since hadoop_home is set wrongly
[ https://issues.apache.org/jira/browse/HIVE-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291976#comment-13291976 ] Carl Steinbach commented on HIVE-3013: -- https://reviews.facebook.net/D3555 TestCliDriver cannot be debugged with eclipse since hadoop_home is set wrongly -- Key: HIVE-3013 URL: https://issues.apache.org/jira/browse/HIVE-3013 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.9.0 Reporter: Namit Jain Assignee: Carl Steinbach Attachments: HIVE-3013.2.patch.txt, HIVE-3013.3.patch.txt, hive.3013.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3105) HIVE-895 introduced build errors in Eclipse
[ https://issues.apache.org/jira/browse/HIVE-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3105: - Resolution: Duplicate Status: Resolved (was: Patch Available) HIVE-895 introduced build errors in Eclipse --- Key: HIVE-3105 URL: https://issues.apache.org/jira/browse/HIVE-3105 Project: Hive Issue Type: Bug Reporter: Kevin Wilfong Assignee: Kevin Wilfong Priority: Minor Attachments: HIVE-3105.1.patch.txt HIVE-895 added some more jars to ivy.xml, but did not add them to Eclipse's classpath causing the Eclipse build to fail. -- 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-3076) drop partition does not work for non-partition columns
[ https://issues.apache.org/jira/browse/HIVE-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292012#comment-13292012 ] Francis Liu commented on HIVE-3076: --- Hi can we backport this to 0.9? As this is a major issue affecting both hive and hcatalog. drop partition does not work for non-partition columns -- Key: HIVE-3076 URL: https://issues.apache.org/jira/browse/HIVE-3076 Project: Hive Issue Type: Bug Reporter: Namit Jain Fix For: 0.10.0 There is still a problem in case there is a mixture of string and non-string partition columns. -- 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-3063) drop partition for non-string columns is failing
[ https://issues.apache.org/jira/browse/HIVE-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292013#comment-13292013 ] Francis Liu commented on HIVE-3063: --- Hi can we backport this to 0.9? As this is a major issue affecting both hive and hcatalog. drop partition for non-string columns is failing Key: HIVE-3063 URL: https://issues.apache.org/jira/browse/HIVE-3063 Project: Hive Issue Type: Bug Components: Metastore, Query Processor Reporter: Namit Jain Assignee: Namit Jain Fix For: 0.10.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2694) Add FORMAT UDF
[ https://issues.apache.org/jira/browse/HIVE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-2694: - Status: Open (was: Patch Available) @Zhenxiao: Please see my comments on phabricator. Thanks. Add FORMAT UDF -- Key: HIVE-2694 URL: https://issues.apache.org/jira/browse/HIVE-2694 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Zhenxiao Luo Attachments: HIVE-2694.1.patch.txt, HIVE-2694.2.patch.txt, HIVE-2694.D1149.1.patch, HIVE-2694.D1149.2.patch, HIVE-2694.D1149.3.patch, HIVE-2694.D2673.1.patch, HIVE-2694.D2673.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3106) Add option to make multi inserts more atomic
[ https://issues.apache.org/jira/browse/HIVE-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3106: Attachment: HIVE-3106.1.patch.txt Add option to make multi inserts more atomic Key: HIVE-3106 URL: https://issues.apache.org/jira/browse/HIVE-3106 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3106.1.patch.txt Currently, with multi-insert queries as soon the output of one of the inserts is ready the move task associated with that insert is run, creating the table/partition. However, if concurrency is enabled the lock on this table/partition is not released until the entire query finishes, which can be much later. This causes issues if, for example, a user is waiting for an output of the multi-insert query which is created long before the other outputs, and checking for it's existence using the metastore's Thrift methods (get_table/get_partition). In which case, the user will run their query which uses the output, and it will experience a timeout trying to acquire the lock on the table/partition. If all the move tasks depend on the parent's of all other move tasks, the output creation will be much closer to atomic relieving this problem. -- 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-3106) Add option to make multi inserts more atomic
[ https://issues.apache.org/jira/browse/HIVE-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292048#comment-13292048 ] Kevin Wilfong commented on HIVE-3106: - Submitted a diff here https://reviews.facebook.net/D3561 Add option to make multi inserts more atomic Key: HIVE-3106 URL: https://issues.apache.org/jira/browse/HIVE-3106 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3106.1.patch.txt Currently, with multi-insert queries as soon the output of one of the inserts is ready the move task associated with that insert is run, creating the table/partition. However, if concurrency is enabled the lock on this table/partition is not released until the entire query finishes, which can be much later. This causes issues if, for example, a user is waiting for an output of the multi-insert query which is created long before the other outputs, and checking for it's existence using the metastore's Thrift methods (get_table/get_partition). In which case, the user will run their query which uses the output, and it will experience a timeout trying to acquire the lock on the table/partition. If all the move tasks depend on the parent's of all other move tasks, the output creation will be much closer to atomic relieving this problem. -- 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-3106) Add option to make multi inserts more atomic
[ https://issues.apache.org/jira/browse/HIVE-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3106: Status: Patch Available (was: Open) Add option to make multi inserts more atomic Key: HIVE-3106 URL: https://issues.apache.org/jira/browse/HIVE-3106 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3106.1.patch.txt Currently, with multi-insert queries as soon the output of one of the inserts is ready the move task associated with that insert is run, creating the table/partition. However, if concurrency is enabled the lock on this table/partition is not released until the entire query finishes, which can be much later. This causes issues if, for example, a user is waiting for an output of the multi-insert query which is created long before the other outputs, and checking for it's existence using the metastore's Thrift methods (get_table/get_partition). In which case, the user will run their query which uses the output, and it will experience a timeout trying to acquire the lock on the table/partition. If all the move tasks depend on the parent's of all other move tasks, the output creation will be much closer to atomic relieving this problem. -- 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-2694) Add FORMAT UDF
[ https://issues.apache.org/jira/browse/HIVE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-2694: - Status: Patch Available (was: Open) Add FORMAT UDF -- Key: HIVE-2694 URL: https://issues.apache.org/jira/browse/HIVE-2694 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Zhenxiao Luo Attachments: HIVE-2694.1.patch.txt, HIVE-2694.2.patch.txt, HIVE-2694.D1149.1.patch, HIVE-2694.D1149.2.patch, HIVE-2694.D1149.3.patch, HIVE-2694.D2673.1.patch, HIVE-2694.D2673.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2694) Add FORMAT UDF
[ https://issues.apache.org/jira/browse/HIVE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292067#comment-13292067 ] Carl Steinbach commented on HIVE-2694: -- +1. Will commit if tests pass. Add FORMAT UDF -- Key: HIVE-2694 URL: https://issues.apache.org/jira/browse/HIVE-2694 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Zhenxiao Luo Attachments: HIVE-2694.1.patch.txt, HIVE-2694.2.patch.txt, HIVE-2694.D1149.1.patch, HIVE-2694.D1149.2.patch, HIVE-2694.D1149.3.patch, HIVE-2694.D2673.1.patch, HIVE-2694.D2673.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2694) Add FORMAT UDF
[ https://issues.apache.org/jira/browse/HIVE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292068#comment-13292068 ] Carl Steinbach commented on HIVE-2694: -- Latest review request from Zhenxiao: https://reviews.facebook.net/D2673 Add FORMAT UDF -- Key: HIVE-2694 URL: https://issues.apache.org/jira/browse/HIVE-2694 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Zhenxiao Luo Attachments: HIVE-2694.1.patch.txt, HIVE-2694.2.patch.txt, HIVE-2694.D1149.1.patch, HIVE-2694.D1149.2.patch, HIVE-2694.D1149.3.patch, HIVE-2694.D2673.1.patch, HIVE-2694.D2673.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3013) TestCliDriver cannot be debugged with eclipse since hadoop_home is set incorrectly
[ https://issues.apache.org/jira/browse/HIVE-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3013: - Summary: TestCliDriver cannot be debugged with eclipse since hadoop_home is set incorrectly (was: TestCliDriver cannot be debugged with eclipse since hadoop_home is set wrongly) TestCliDriver cannot be debugged with eclipse since hadoop_home is set incorrectly -- Key: HIVE-3013 URL: https://issues.apache.org/jira/browse/HIVE-3013 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.9.0 Reporter: Namit Jain Assignee: Carl Steinbach Attachments: HIVE-3013.2.patch.txt, HIVE-3013.3.patch.txt, hive.3013.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2693) Add DECIMAL data type
[ https://issues.apache.org/jira/browse/HIVE-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-2693: - Component/s: Types Add DECIMAL data type - Key: HIVE-2693 URL: https://issues.apache.org/jira/browse/HIVE-2693 Project: Hive Issue Type: New Feature Components: Query Processor, Types Reporter: Carl Steinbach Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice template for how to do this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1107) Generic parallel execution framework for Hive (and Pig, and ...)
[ https://issues.apache.org/jira/browse/HIVE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292087#comment-13292087 ] Milind Bhandarkar commented on HIVE-1107: - @jco, @squarecog et al. I have had initial discussions with Keren about this project. I agree that full production-quality unification is a lot of work, and would require super-human effort to get it done in 4 months. So, Keren's internship with Greenplum will focus on producing a prototype. The approach I have proposed to her involves taking an open-source execution engine, which has superset of these operators, which is already proven to work with Hadoop (in fact has Hive implemented on top of it already), and make sure a subset of pig operators are ported to it. Generic parallel execution framework for Hive (and Pig, and ...) Key: HIVE-1107 URL: https://issues.apache.org/jira/browse/HIVE-1107 Project: Hive Issue Type: New Feature Components: Query Processor Reporter: Carl Steinbach Pig and Hive each have their own libraries for handling plan execution. As we prepare to invest more time improving Hive's plan execution mechanism we should also start to consider ways of building a generic plan execution mechanism that is capable of supporting the needs of Hive and Pig, as well as other Hadoop data flow programming environments. -- 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-1107) Generic parallel execution framework for Hive (and Pig, and ...)
[ https://issues.apache.org/jira/browse/HIVE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292089#comment-13292089 ] Carl Steinbach commented on HIVE-1107: -- @Milind: Which open-source execution engine are you using? Generic parallel execution framework for Hive (and Pig, and ...) Key: HIVE-1107 URL: https://issues.apache.org/jira/browse/HIVE-1107 Project: Hive Issue Type: New Feature Components: Query Processor Reporter: Carl Steinbach Pig and Hive each have their own libraries for handling plan execution. As we prepare to invest more time improving Hive's plan execution mechanism we should also start to consider ways of building a generic plan execution mechanism that is capable of supporting the needs of Hive and Pig, as well as other Hadoop data flow programming environments. -- 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-1107) Generic parallel execution framework for Hive (and Pig, and ...)
[ https://issues.apache.org/jira/browse/HIVE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292094#comment-13292094 ] Milind Bhandarkar commented on HIVE-1107: - I have requested Keren to look at Hyracks (http://code.google.com/p/hyracks/) and Asterix. This is built by Mike Carey's research group at UC Irvine, and recently ex-Yahoo! researchers (Marcus Weimer Tyson Condie) produced some interesting results using Hyracks. Please note that this is exploratory work right now, and just a proposed approach. Not a final choice. Generic parallel execution framework for Hive (and Pig, and ...) Key: HIVE-1107 URL: https://issues.apache.org/jira/browse/HIVE-1107 Project: Hive Issue Type: New Feature Components: Query Processor Reporter: Carl Steinbach Pig and Hive each have their own libraries for handling plan execution. As we prepare to invest more time improving Hive's plan execution mechanism we should also start to consider ways of building a generic plan execution mechanism that is capable of supporting the needs of Hive and Pig, as well as other Hadoop data flow programming environments. -- 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-2694) Add FORMAT UDF
[ https://issues.apache.org/jira/browse/HIVE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-2694: --- Attachment: HIVE-2694.3.patch.txt Add FORMAT UDF -- Key: HIVE-2694 URL: https://issues.apache.org/jira/browse/HIVE-2694 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Zhenxiao Luo Attachments: HIVE-2694.1.patch.txt, HIVE-2694.2.patch.txt, HIVE-2694.3.patch.txt, HIVE-2694.D1149.1.patch, HIVE-2694.D1149.2.patch, HIVE-2694.D1149.3.patch, HIVE-2694.D2673.1.patch, HIVE-2694.D2673.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2694) Add FORMAT UDF
[ https://issues.apache.org/jira/browse/HIVE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292106#comment-13292106 ] Zhenxiao Luo commented on HIVE-2694: @Carl: HIVE-2694.3.patch.txt is the updated patch for the current trunk. Add FORMAT UDF -- Key: HIVE-2694 URL: https://issues.apache.org/jira/browse/HIVE-2694 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Zhenxiao Luo Attachments: HIVE-2694.1.patch.txt, HIVE-2694.2.patch.txt, HIVE-2694.3.patch.txt, HIVE-2694.D1149.1.patch, HIVE-2694.D1149.2.patch, HIVE-2694.D1149.3.patch, HIVE-2694.D2673.1.patch, HIVE-2694.D2673.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3013) TestCliDriver cannot be debugged with eclipse since hadoop_home is set incorrectly
[ https://issues.apache.org/jira/browse/HIVE-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292112#comment-13292112 ] Ashutosh Chauhan commented on HIVE-3013: +1 Few comments (posting here, since phabricator has lost ability to post back on jira): * TestCliDriver.launch seems to work now. I didn't run the full suite of 887 tests, but first few (~20) ran without any failures. * TestHBaseCliDriver and TestTruncate doesnt launch correctly. * Others launch successfully, but only few have all tests passing. * HiveCLI.launch launches successfully, but doesnt work because of incorrect config. None of these are related to this jira, so can be handled in follow-ups. Just noting these here for others about what I found out. TestCliDriver cannot be debugged with eclipse since hadoop_home is set incorrectly -- Key: HIVE-3013 URL: https://issues.apache.org/jira/browse/HIVE-3013 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.9.0 Reporter: Namit Jain Assignee: Carl Steinbach Attachments: HIVE-3013.2.patch.txt, HIVE-3013.3.patch.txt, hive.3013.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2691) Specify location of log4j configuration files via configuration properties
[
https://issues.apache.org/jira/browse/HIVE-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-2691:
---
Attachment: HIVE-2691.1.patch.txt
Specify location of log4j configuration files via configuration properties
--
Key: HIVE-2691
URL: https://issues.apache.org/jira/browse/HIVE-2691
Project: Hive
Issue Type: New Feature
Components: Configuration, Logging
Reporter: Carl Steinbach
Assignee: Zhenxiao Luo
Attachments: HIVE-2691.1.patch.txt, HIVE-2691.D1131.1.patch,
HIVE-2691.D1203.1.patch, HIVE-2691.D1203.2.patch, HIVE-2691.D1203.3.patch,
HIVE-2691.D1203.4.patch, HIVE-2691.D1203.5.patch, HIVE-2691.D1203.6.patch,
HIVE-2691.D2667.1.patch, HIVE-2691.D2667.1.patch
Oozie needs to be able to override the default location of the log4j
configuration
files from the Hive command line, e.g:
{noformat}
hive -hiveconf hive.log4j.file=/home/carl/hive-log4j.properties -hiveconf
hive.log4j.exec.file=/home/carl/hive-exec-log4j.properties
{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] [Created] (HIVE-3107) More semantic analysis errors
Richard Ding created HIVE-3107:
--
Summary: More semantic analysis errors
Key: HIVE-3107
URL: https://issues.apache.org/jira/browse/HIVE-3107
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.9.0
Reporter: Richard Ding
This is related to HIVE-1922.
Following queries all fail with various SemanticExceptions:
{code}
explain select t.c from t group by c;
explain select t.c from t group by c sort by t.c;
explain select t.c as c0 from t group by c0;
explain select t.c from t group by t.c sort by t.c;
{code}
It is true that one could always find a version of any of above queries that
works. But one has to try to find out and it doesn't work well with machine
generated SQL 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-3108) SELECT count(DISTINCT col) ... returns 0 if col is a partition column
Dean Wampler created HIVE-3108: -- Summary: SELECT count(DISTINCT col) ... returns 0 if col is a partition column Key: HIVE-3108 URL: https://issues.apache.org/jira/browse/HIVE-3108 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.9.0, 0.8.0 Environment: Mac OSX running Apache distribution of hadoop and hive natively. Reporter: Dean Wampler Suppose stocks is a managed OR external table, partitioned by exchange and symbol. count(DISTINCT x) returns 0 for either exchange, symbol, or both: hive SELECT count(DISTINCT exchange), count(DISTINCT symbol) from stocks; 0 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
