[jira] [Commented] (HIVE-2902) undefined property exists in eclipse-templates/.classpath
[
https://issues.apache.org/jira/browse/HIVE-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254537#comment-13254537
]
tamtam180 commented on HIVE-2902:
-
hbase-*-tests.jar is need.
HBaseTestSetup.java depends on org.apache.hadoop.hbase.MiniHBaseCluster only
include hbase-*-tests.jar.
undefined property exists in eclipse-templates/.classpath
-
Key: HIVE-2902
URL: https://issues.apache.org/jira/browse/HIVE-2902
Project: Hive
Issue Type: Bug
Components: Build Infrastructure
Reporter: tamtam180
Priority: Minor
@hbase-test.version@ was removed from ivy/libraries.properties in HIVE-2748,
but the property still exists in eclipse-templates/.classpath.
{code}
classpathentry kind=lib path=build/ivy/lib/default/hbase-0.92.0.jar/
classpathentry kind=lib
path=build/ivy/lib/default/hbase-@hbase-test.vers...@-tests.jar/
{code}
It should be changed to @hbase.version@
--
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-2667) org.apache.hadoop.hive.ql.exec.MapRedTask error message needs to be more specific
[ https://issues.apache.org/jira/browse/HIVE-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254546#comment-13254546 ] nago n commented on HIVE-2667: -- @Kathleen - i have raised the same issue with new ticket HIVE-2951. Please respond to that. org.apache.hadoop.hive.ql.exec.MapRedTask error message needs to be more specific - Key: HIVE-2667 URL: https://issues.apache.org/jira/browse/HIVE-2667 Project: Hive Issue Type: Improvement Affects Versions: 0.8.0 Reporter: Kathleen Ting Got opaque error message FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask which tedious trial and error deduced to be an MR misconfiguration on io.sort.mb, namely the map buffer size was too small for the allocated child heap size. Would be helpful if the error message was more specific. -- 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-2540) LATERAL VIEW with EXPLODE produces ConcurrentModificationException
[
https://issues.apache.org/jira/browse/HIVE-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-2540:
--
Attachment: HIVE-2540.D2805.1.patch
navis requested code review of HIVE-2540 [jira] LATERAL VIEW with EXPLODE
produces ConcurrentModificationException.
Reviewers: JIRA
DPAL-1095 LATERAL VIEW with EXPLODE produces ConcurrentModificationException
The following produces ConcurrentModificationException on the for loop inside
EXPLODE:
create table foo as select array(1, 2) a from src limit 1;
select a, x.b from foo lateral view explode(a) x as b;
TEST PLAN
EMPTY
REVISION DETAIL
https://reviews.facebook.net/D2805
AFFECTED FILES
hbase-handler/src/java/org/apache/hadoop/hive/hbase/LazyHBaseCellMap.java
ql/src/test/queries/clientpositive/udf_explode.q
ql/src/test/queries/clientpositive/udtf_explode.q
ql/src/test/results/clientpositive/udf_explode.q.out
ql/src/test/results/clientpositive/udtf_explode.q.out
serde/src/java/org/apache/hadoop/hive/serde2/lazy/LazyArray.java
serde/src/java/org/apache/hadoop/hive/serde2/lazy/LazyMap.java
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/6393/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
LATERAL VIEW with EXPLODE produces ConcurrentModificationException
--
Key: HIVE-2540
URL: https://issues.apache.org/jira/browse/HIVE-2540
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.7.1
Reporter: David Phillips
Attachments: HIVE-2540.D2805.1.patch
The following produces {{ConcurrentModificationException}} on the {{for}}
loop inside EXPLODE:
{code}
create table foo as select array(1, 2) a from src limit 1;
select a, x.b from foo lateral view explode(a) x as b;
{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
[jira] [Created] (HIVE-2953) ReflectionStructObjectInspector support for getters and setters
ReflectionStructObjectInspector support for getters and setters --- Key: HIVE-2953 URL: https://issues.apache.org/jira/browse/HIVE-2953 Project: Hive Issue Type: Wish Affects Versions: 0.8.1 Reporter: Jaka Jancar It would be great if ReflectionStructObjectInspector could also support using getters, not just fields. Additionally, it would be also nice to be able to limit it to only use public fields/getters. -- 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: 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.8.1 Reporter: alex gemini Priority: Minor Attachments: HIVE-2933-0.8.1-1.patch, HIVE-2933-0.8.1-2.patch 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-0.8.1-2.patch test added. 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 Priority: Minor Attachments: HIVE-2933-0.8.1-1.patch, HIVE-2933-0.8.1-2.patch 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-2902) undefined property exists in eclipse-templates/.classpath
[
https://issues.apache.org/jira/browse/HIVE-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tamtam180 updated HIVE-2902:
Attachment: HIVE-2902.1.patch.txt
modified as follows
- changed to @hbase.version@ from @hbase-test.version@ in
eclipse-templates/.classpath
undefined property exists in eclipse-templates/.classpath
-
Key: HIVE-2902
URL: https://issues.apache.org/jira/browse/HIVE-2902
Project: Hive
Issue Type: Bug
Components: Build Infrastructure
Reporter: tamtam180
Priority: Minor
Attachments: HIVE-2902.1.patch.txt
@hbase-test.version@ was removed from ivy/libraries.properties in HIVE-2748,
but the property still exists in eclipse-templates/.classpath.
{code}
classpathentry kind=lib path=build/ivy/lib/default/hbase-0.92.0.jar/
classpathentry kind=lib
path=build/ivy/lib/default/hbase-@hbase-test.vers...@-tests.jar/
{code}
It should be changed to @hbase.version@
--
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-2954) The statement fails when a column part of an ORDER BY is not specified in the SELECT.
The statement fails when a column part of an ORDER BY is not specified in the SELECT. - Key: HIVE-2954 URL: https://issues.apache.org/jira/browse/HIVE-2954 Project: Hive Issue Type: Improvement Components: SQL Affects Versions: 0.8.1 Reporter: Mauro Cazzari Given the following table: CREATE TABLE `DBCSTB32` (`aaa` DOUBLE,`bbb` STRING,`ccc` STRING,`ddd` DOUBLE) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\001' STORED AS TEXTFILE; The following statement fails: select TXT_1`aaa`, TXT_1.`bbb` from `DBCSTB32` TXT_1 order by TXT_1.`bbb` asc, TXT_1.`aaa` asc, TXT_1.`ccc` asc ERROR: java.sql.SQLException: Query returned non-zero code: 10, cause: FAILED: Error in semantic analysis: Line 1:104 Invalid column reference '`ccc`' Adding `ccc` to the selected list of columns fixes the 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-2667) org.apache.hadoop.hive.ql.exec.MapRedTask error message needs to be more specific
[ https://issues.apache.org/jira/browse/HIVE-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254832#comment-13254832 ] Kathleen Ting commented on HIVE-2667: - @nago - as mentioned, emailing u...@hive.apache.org is the correct forum for user questions. org.apache.hadoop.hive.ql.exec.MapRedTask error message needs to be more specific - Key: HIVE-2667 URL: https://issues.apache.org/jira/browse/HIVE-2667 Project: Hive Issue Type: Improvement Affects Versions: 0.8.0 Reporter: Kathleen Ting Got opaque error message FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask which tedious trial and error deduced to be an MR misconfiguration on io.sort.mb, namely the map buffer size was too small for the allocated child heap size. Would be helpful if the error message was more specific. -- 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
Re: [VOTE] Apache Hive 0.9.0 Release Candidate 0
-1 * RELEASE_NOTES.txt needs to be updated. * The Postgres metastore upgrade scripts should be excluded from the tarball since they are not current. There is already a build property that handles this (include.postgres), which should default to false. * HIVE-2795 added a python metastore upgrade script located in scripts/metastore/upgrade. This script is not mentioned in any of the README.txt files, and it's also not clear which version of Python is required to run it. Furthermore, the docs in the python script are not very clear, probably won't work with Derby, and reference a dependency in trunk/build/dist/lib/py which is not present in the tarball. * The lib/ directory contains some new JARs which are not covered in the LICENSE file (it's also possible that these are not really required), as well as a couple cases of multiple versions of the same JAR. Here are the ones that jump out at me, though there are probably some I missed: ** JavaEWAH-0.3.2 ** antlr-2.7.7 and antlr-3.0.1? ** commons-codec-1.3 and commons-codec-1.4? ** commons-logging-1.0.4 and commons-logging-1.1.1? ** hamcrest-core-1.1 ** hsqldb-1.8.0.10 ** kfs-0.3 ** oro-2.0.8 (This uses v1.1 of the ASF license) Thanks. Carl On Fri, Apr 13, 2012 at 3:28 PM, Ashutosh Chauhan hashut...@apache.orgwrote: Couple more points: Maven artifacts are available at https://repository.apache.org/content/repositories/orgapachehive-043/ for folks to try out. Vote runs for 3 business days so will expire on Wednesday, 4/18. Thanks, Ashutosh On Fri, Apr 13, 2012 at 11:50, Ashutosh Chauhan hashut...@apache.org wrote: Hey all, Apache Hive 0.9.0-rc0 is out and available at http://people.apache.org/~hashutosh/hive-0.9.0-rc0/ Release notes are available at: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310843version=12317742 Please give it a try, let us know. Hive PMC members: Please test and vote. Thanks, Ashutosh
[jira] [Updated] (HIVE-2918) Hive Dynamic Partition Insert - move task not considering 'hive.exec.max.dynamic.partitions' from CLI
[ https://issues.apache.org/jira/browse/HIVE-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-2918: Status: Open (was: Patch Available) Hive Dynamic Partition Insert - move task not considering 'hive.exec.max.dynamic.partitions' from CLI - Key: HIVE-2918 URL: https://issues.apache.org/jira/browse/HIVE-2918 Project: Hive Issue Type: Bug Affects Versions: 0.8.1, 0.8.0, 0.7.1 Environment: Cent OS 64 bit Reporter: Bejoy KS Assignee: Carl Steinbach Attachments: HIVE-2918.D2703.1.patch Dynamic Partition insert showing an error with the number of partitions created even after the default value of 'hive.exec.max.dynamic.partitions' is bumped high to 2000. Error Message: Failed with exception Number of dynamic partitions created is 1413, which is more than 1000. To solve this try to set hive.exec.max.dynamic.partitions to at least 1413. These are the following properties set on hive CLI hive set hive.exec.dynamic.partition=true; hive set hive.exec.dynamic.partition.mode=nonstrict; hive set hive.exec.max.dynamic.partitions=2000; hive set hive.exec.max.dynamic.partitions.pernode=2000; This is the query with console error log hive INSERT OVERWRITE TABLE partn_dyn Partition (pobox) SELECT country,state,pobox FROM non_partn_dyn; Total MapReduce jobs = 2 Launching Job 1 out of 2 Number of reduce tasks is set to 0 since there's no reduce operator Starting Job = job_201204021529_0002, Tracking URL = http://0.0.0.0:50030/jobdetails.jsp?jobid=job_201204021529_0002 Kill Command = /usr/lib/hadoop/bin/hadoop job -Dmapred.job.tracker=0.0.0.0:8021 -kill job_201204021529_0002 2012-04-02 16:05:28,619 Stage-1 map = 0%, reduce = 0% 2012-04-02 16:05:39,701 Stage-1 map = 100%, reduce = 0% 2012-04-02 16:05:50,800 Stage-1 map = 100%, reduce = 100% Ended Job = job_201204021529_0002 Ended Job = 248865587, job is filtered out (removed at runtime). Moving data to: hdfs://0.0.0.0/tmp/hive-cloudera/hive_2012-04-02_16-05-24_919_5976014408587784412/-ext-1 Loading data to table default.partn_dyn partition (pobox=null) Failed with exception Number of dynamic partitions created is 1413, which is more than 1000. To solve this try to set hive.exec.max.dynamic.partitions to at least 1413. FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.MoveTask I checked the job.xml of the first map only job, there the value hive.exec.max.dynamic.partitions=2000 is reflected but the move task is taking the default value from hive-site.xml . If I change the value in hive-site.xml then the job completes successfully. Bottom line,the property 'hive.exec.max.dynamic.partitions'set on CLI is not being considered by move task -- 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-2883) Metastore client doesnt close connection properly
[
https://issues.apache.org/jira/browse/HIVE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254899#comment-13254899
]
Mithun Radhakrishnan commented on HIVE-2883:
+1
Good fix, this. Takes care of HCATALOG-236 as well.
Metastore client doesnt close connection properly
-
Key: HIVE-2883
URL: https://issues.apache.org/jira/browse/HIVE-2883
Project: Hive
Issue Type: Bug
Components: Metastore
Affects Versions: 0.9.0
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan
Fix For: 0.9.0
Attachments: HIVE-2883.D2613.1.patch
While closing connection, it always fail with following trace. Seemingly, it
doesnt have any harmful effects.
{code}
12/03/20 10:55:02 ERROR hive.metastore: Unable to shutdown local metastore
client
org.apache.thrift.transport.TTransportException: Cannot write to null
outputStream
at
org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport.java:142)
at
org.apache.thrift.protocol.TBinaryProtocol.writeI32(TBinaryProtocol.java:163)
at
org.apache.thrift.protocol.TBinaryProtocol.writeMessageBegin(TBinaryProtocol.java:91)
at org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:62)
at
com.facebook.fb303.FacebookService$Client.send_shutdown(FacebookService.java:421)
at
com.facebook.fb303.FacebookService$Client.shutdown(FacebookService.java:415)
at
org.apache.hadoop.hive.metastore.HiveMetaStoreClient.close(HiveMetaStoreClient.java:310)
{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
[jira] [Commented] (HIVE-2006) Make the HiveServer/Client socket timeout configurable
[
https://issues.apache.org/jira/browse/HIVE-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13254936#comment-13254936
]
Aniket Mokashi commented on HIVE-2006:
--
For hive client, we have
METASTORE_CLIENT_SOCKET_TIMEOUT=hive.metastore.client.socket.timeout.
Do you want to configure read and write timeouts on the server side?
{code}
hive.server.read.socket.timeout=1000
hive.server.write.socket.timeout=1000
{code}
Make the HiveServer/Client socket timeout configurable
--
Key: HIVE-2006
URL: https://issues.apache.org/jira/browse/HIVE-2006
Project: Hive
Issue Type: Improvement
Components: Clients, Server Infrastructure
Reporter: Carl Steinbach
We should add configuration properties that make it possible to control the
thrift socket timeout for HiveServer and HiveClient, e.g.
{code}
hive.server.thrift.socket.timeout=1000
hive.client.thrift.socket.timeout=1000
{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
[jira] [Resolved] (HIVE-2951) Hive map-join throws error !!
[ https://issues.apache.org/jira/browse/HIVE-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach resolved HIVE-2951. -- Resolution: Invalid Questions like this should be directed to the user mailing list (u...@hive.apache.org). Hive map-join throws error !! - Key: HIVE-2951 URL: https://issues.apache.org/jira/browse/HIVE-2951 Project: Hive Issue Type: Bug Affects Versions: 0.7.0 Reporter: nago n I get this below message. What does this mean ? What is really leading for this issue ? what should i do to resolve this ? i use joins in the query as if ( A left outer join B left outer join C lefit out join D ) . whereas A is the Big table. FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.MapredLocalTask ATTEMPT: Execute BackupTask: org.apache.hadoop.hive.ql.exec.MapRedTask I set manual properties : set hive.mapjoin.localtask.max.memory.usage = 0.9; set hive.auto.convert.join = true; set hive.smalltable.filesize = 3000; the default configuration is : -- mapred.child.java.opts :-Xmx2400m -XX:+UseConcMarkSweepGC -XX: +UseParNewGC -XX:+CMSParallelRemarkEnabled -X:-UseAdaptiveSizePolicy - XX:+DisableExplicitGC -- 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 # 1377 - Fixed
Changes for Build #1374 Changes for Build #1375 Changes for Build #1376 Changes for Build #1377 All tests passed The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1377) Status: Fixed Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1377/ to view the results.
[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=13255173#comment-13255173 ] Phabricator commented on HIVE-2646: --- cwsteinbach has commented on the revision HIVE-2646 [jira] Hive Ivy dependencies on Hadoop should depend on jars directly, not tarballs. alter_table_wrong_regex and create_table_wrong_regex both belong in contrib/src/test/queries/clientnegative/. It was a mistake in the first place for them to get committed to the ql directory since nothing else in Hive is supposed to have a dependency on contrib (which is pretty much the whole point of contrib). The same thing goes for udfnull.q. The point of this test (which you would never be able to tell by looking at it since the original author failed to include any documentation) is that query execution will fail (despite query compilation succeeding) if the query references a UDF which is on the local classpath but not on the cluster classpath, which usually happens when the user forgets to include an 'ADD JAR ...' statement. In order to get this test to pass we need to ensure that hive-contrib*.jar is not on bin/hadoop's classpath. REVISION DETAIL https://reviews.facebook.net/D2133 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.9.0 Attachments: 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.diff.txt 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] [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=13255175#comment-13255175
]
Phabricator commented on HIVE-2646:
---
cwsteinbach has commented on the revision HIVE-2646 [jira] Hive Ivy
dependencies on Hadoop should depend on jars directly, not tarballs.
INLINE COMMENTS
build-common.xml:367 Indentation.
build-common.xml:379 ${testcp} is not defined.
build-common.xml:385 $HIVE_HADOOP_TEST_CLASSPATH is supposed to be the
classpath that bin/hadoop would construct for itself without any outside input,
e.g. hadoop-* JAR files and any dependencies. It should not include any Hive
JARs or dependencies.
testutils/hadoop:53 If $HADOOP_CLASSPATH is defined, we should tack it onto
the end of the CLASSPATH at this point.
REVISION DETAIL
https://reviews.facebook.net/D2133
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.9.0
Attachments: 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.diff.txt
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] [Resolved] (HIVE-2077) Allow HBaseStorageHandler to work with hbase 0.90.1
[ https://issues.apache.org/jira/browse/HIVE-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach resolved HIVE-2077. -- Resolution: Duplicate Allow HBaseStorageHandler to work with hbase 0.90.1 --- Key: HIVE-2077 URL: https://issues.apache.org/jira/browse/HIVE-2077 Project: Hive Issue Type: Improvement Components: HBase Handler Affects Versions: 0.7.0 Reporter: Ted Yu Currently HBase handler works with hbase 0.89 We should make it work with 0.90.1 and utilize new features of 0.90.1 -- 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-896) Add LEAD/LAG/FIRST/LAST analytical windowing functions to Hive.
[ https://issues.apache.org/jira/browse/HIVE-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255251#comment-13255251 ] Harish Butani commented on HIVE-896: Hi, Yes, I have been developing SQL Windowing on top of Hive(https://github.com/hbutani/SQLWindowing/wiki). Users can intersperse Hive Queries with Windowing Clauses and Table functions. Users can use this from a CLI (hive --service windowingCLI) or via a Query API. The hope is to provide Users: - Windowing Clauses and Table functions as a simple extension to HQL - overtime to fold the implementation into the Hive code base with hopefully minimal impact to the User experience. Here are some thoughts on how to fold this functionality into Hive: https://github.com/hbutani/SQLWindowing/wiki/MoveToHive Any thoughts/comments/suggestions greatly welcomed. regards, Harish Butani. Add LEAD/LAG/FIRST/LAST analytical windowing functions to Hive. --- Key: HIVE-896 URL: https://issues.apache.org/jira/browse/HIVE-896 Project: Hive Issue Type: New Feature Components: OLAP, UDF Reporter: Amr Awadallah Priority: Minor Windowing functions are very useful for click stream processing and similar time-series/sliding-window analytics. More details at: http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10736/analysis.htm#i1006709 http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10736/analysis.htm#i1007059 http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10736/analysis.htm#i1007032 -- amr -- 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-2955) Queries consists of metadata-only-query returns always empty value
Queries consists of metadata-only-query returns always empty value
--
Key: HIVE-2955
URL: https://issues.apache.org/jira/browse/HIVE-2955
Project: Hive
Issue Type: Bug
Reporter: Navis
Assignee: Navis
Priority: Minor
For partitioned table, simple query on partition column returns always null or
empty value, for example,
{code}
create table emppart(empno int, ename string) partitioned by (deptno int);
.. load partitions..
select distinct deptno from emppart; // empty
select min(deptno), max(deptno) from emppart; // NULL and NULL
{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
[jira] [Updated] (HIVE-2955) Queries consists of metadata-only-query returns always empty value
[
https://issues.apache.org/jira/browse/HIVE-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-2955:
--
Attachment: HIVE-2955.D2817.1.patch
navis requested code review of HIVE-2955 [jira] Queries consists of
metadata-only-query returns always empty value.
Reviewers: JIRA
DPAL-1108 Queries consists of metadata-only-query returns always empty value
For partitioned table, simple query on partition column returns always null
or empty value, for example,
create table emppart(empno int, ename string) partitioned by (deptno int);
.. load partitions..
select distinct deptno from emppart; // empty
select min(deptno), max(deptno) from emppart; // NULL and NULL
TEST PLAN
EMPTY
REVISION DETAIL
https://reviews.facebook.net/D2817
AFFECTED FILES
ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/MetadataOnlyOptimizer.java
ql/src/test/queries/clientpositive/metadataonly1.q
ql/src/test/results/clientpositive/metadataonly1.q.out
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/6411/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
Queries consists of metadata-only-query returns always empty value
--
Key: HIVE-2955
URL: https://issues.apache.org/jira/browse/HIVE-2955
Project: Hive
Issue Type: Bug
Reporter: Navis
Assignee: Navis
Priority: Minor
Attachments: HIVE-2955.D2817.1.patch
For partitioned table, simple query on partition column returns always null
or empty value, for example,
{code}
create table emppart(empno int, ename string) partitioned by (deptno int);
.. load partitions..
select distinct deptno from emppart; // empty
select min(deptno), max(deptno) from emppart; // NULL and NULL
{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
