[jira] [Updated] (HIVE-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification
[ https://issues.apache.org/jira/browse/HIVE-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Bautin updated HIVE-3384: - Attachment: HIVE-3384-2012-12-04.patch Manually generated patch corresponding to https://reviews.facebook.net/D6873?vs=onid=22815whitespace=ignore-all#differential-review-toc addressing the problem with PluginTest running from the pdk module. HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification -- Key: HIVE-3384 URL: https://issues.apache.org/jira/browse/HIVE-3384 Project: Hive Issue Type: Bug Components: JDBC Reporter: Weidong Bian Priority: Minor Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch jdbc module couldn't be compiled with jdk7 as it adds some abstract method in the JDBC specification some error info: error: HiveCallableStatement is not abstract and does not override abstract method TgetObject(String,ClassT) in CallableStatement . . . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification
[
https://issues.apache.org/jira/browse/HIVE-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509587#comment-13509587
]
Mikhail Bautin commented on HIVE-3384:
--
[~ashutoshc]: Thank you for testing the patch. I have addressed your comment
and PluginTest now passes when running from both {{builtin}} and {{pdk}}
modules.
{code:title=build/pdk/test-plugin/build/TEST-org.apache.hive.pdk.PluginTest.txt}
Testsuite: org.apache.hive.pdk.PluginTest
Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 42.592 sec
- Standard Error -
GLOBAL SETUP: Copying file:
file:/wd/hive-trunk/build/pdk/test-plugin/test/onerow.txt
Deleted file:/wd/hive-trunk/build/pdk/test-plugin/build/warehouse/onerow
org.apache.hive.pdktest.Rot13 SETUP: Deleted
file:/wd/hive-trunk/build/pdk/test-plugin/build/warehouse/rot13_data
org.apache.hive.pdktest.Rot13 TEARDOWN:
Hive history file=/tmp/mbautin/hive_job_log_mbautin_201212040011_1557635606.txt
OK
Time taken: 6.16 seconds
GLOBAL TEARDOWN:
Hive history file=/tmp/mbautin/hive_job_log_mbautin_201212040012_1607147323.txt
OK
Time taken: 0.287 seconds
- ---
Testcase: SELECT tp_rot13('Mixed Up!') FROM onerow; took 2.532 sec
Testcase: SELECT tp_rot13(s) FROM rot13_data; took 2.495 sec
{code}
HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC
specification
--
Key: HIVE-3384
URL: https://issues.apache.org/jira/browse/HIVE-3384
Project: Hive
Issue Type: Bug
Components: JDBC
Reporter: Weidong Bian
Priority: Minor
Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch,
D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch,
HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch,
HIVE-3384.patch, HIVE-JDK7-JDBC.patch
jdbc module couldn't be compiled with jdk7 as it adds some abstract method in
the JDBC specification
some error info:
error: HiveCallableStatement is not abstract and does not override abstract
method TgetObject(String,ClassT) in CallableStatement
.
.
.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3750) JDBCStatsPublisher fails when ID length exceeds length of ID column
[ https://issues.apache.org/jira/browse/HIVE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3750: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed. Thanks Kevin JDBCStatsPublisher fails when ID length exceeds length of ID column --- Key: HIVE-3750 URL: https://issues.apache.org/jira/browse/HIVE-3750 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3750.1.patch.txt When the length of the ID field passed to JDBCStatsPublisher exceeds the length of the column in the table (currently 255 characters) stats collection fails. This causes the entire query to fail when hive.stats.reliable is set to true. One way to prevent this would be to calculate a deterministic, very low collision hash of the ID prefix used for aggregation and use that when the length of the ID is too long. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3073) Hive List Bucketing - DML support
[ https://issues.apache.org/jira/browse/HIVE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3073: - Status: Open (was: Patch Available) minor comments Hive List Bucketing - DML support -- Key: HIVE-3073 URL: https://issues.apache.org/jira/browse/HIVE-3073 Project: Hive Issue Type: New Feature Components: SQL Affects Versions: 0.10.0 Reporter: Gang Tim Liu Assignee: Gang Tim Liu Attachments: HIVE-3073.patch.12, HIVE-3073.patch.13, HIVE-3073.patch.15, HIVE-3073.patch.18, HIVE-3073.patch.19, HIVE-3073.patch.21, HIVE-3073.patch.22, HIVE-3073.patch.24 If a hive table column has skewed keys, query performance on non-skewed key is always impacted. Hive List Bucketing feature will address it: https://cwiki.apache.org/Hive/listbucketing.html This jira issue will track DML change for the feature: 1. single skewed column 2. manual load data -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3702) Renaming table changes table location scheme/authority
[ https://issues.apache.org/jira/browse/HIVE-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509652#comment-13509652 ] Namit Jain commented on HIVE-3702: -- +1 Renaming table changes table location scheme/authority -- Key: HIVE-3702 URL: https://issues.apache.org/jira/browse/HIVE-3702 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.9.0 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3702.1.patch.txt, HIVE-3702.2.patch.txt Renaming a table changes the location of the table to the default location of the database, followed by the table name. This means that if the default location of the database uses a different scheme/authority, an exception will get thrown attempting to move the data. Instead, the table's location should be made the default location of the database followed by the table name, but using the original location's scheme and authority. This only applies for managed tables, and there is already a check to ensure the new location doesn't already exist. This is analogous to what was done for partitions in HIVE-2875 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3537) release locks at the end of move tasks
[ https://issues.apache.org/jira/browse/HIVE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3537: - Status: Patch Available (was: Open) comments addressed release locks at the end of move tasks -- Key: HIVE-3537 URL: https://issues.apache.org/jira/browse/HIVE-3537 Project: Hive Issue Type: Bug Components: Locking, Query Processor Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3537.1.patch, hive.3537.2.patch Look at HIVE-3106 for details. In order to make sure that concurrency is not an issue for multi-table inserts, the current option is to introduce a dependency task, which thereby delays the creation of all partitions. It would be desirable to release the locks for the outputs as soon as the move task is completed. That way, for multi-table inserts, the concurrency can be enabled without delaying any table. Currently, the movetask contains a input/output, but they do not seem to be populated correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3702) Renaming table changes table location scheme/authority
[ https://issues.apache.org/jira/browse/HIVE-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3702: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed. Thanks Kevin Renaming table changes table location scheme/authority -- Key: HIVE-3702 URL: https://issues.apache.org/jira/browse/HIVE-3702 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.9.0 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3702.1.patch.txt, HIVE-3702.2.patch.txt Renaming a table changes the location of the table to the default location of the database, followed by the table name. This means that if the default location of the database uses a different scheme/authority, an exception will get thrown attempting to move the data. Instead, the table's location should be made the default location of the database followed by the table name, but using the original location's scheme and authority. This only applies for managed tables, and there is already a check to ensure the new location doesn't already exist. This is analogous to what was done for partitions in HIVE-2875 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3767) BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins also
[ https://issues.apache.org/jira/browse/HIVE-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3767: - Summary: BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins also (was: BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins alsi ) BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins also - Key: HIVE-3767 URL: https://issues.apache.org/jira/browse/HIVE-3767 Project: Hive Issue Type: Bug Reporter: Namit Jain -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3767) BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins alsi
Namit Jain created HIVE-3767: Summary: BucketizedHiveInputFormat should be automatically used with Bucketized Map Joins alsi Key: HIVE-3767 URL: https://issues.apache.org/jira/browse/HIVE-3767 Project: Hive Issue Type: Bug Reporter: Namit Jain -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3768) Document JDBC client configuration for secure clusters
[ https://issues.apache.org/jira/browse/HIVE-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lefty Leverenz reassigned HIVE-3768: Assignee: Lefty Leverenz Document JDBC client configuration for secure clusters -- Key: HIVE-3768 URL: https://issues.apache.org/jira/browse/HIVE-3768 Project: Hive Issue Type: Bug Components: Documentation Affects Versions: 0.9.0 Reporter: Lefty Leverenz Assignee: Lefty Leverenz Fix For: 0.10.0 Document the JDBC client configuration required for starting Hive on a secure cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3768) Document JDBC client configuration for secure clusters
[ https://issues.apache.org/jira/browse/HIVE-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lefty Leverenz updated HIVE-3768: - Attachment: HIVE-3768.1.patch Patch 1 documents the need for hive-site.xml to be in the CLASSPATH of the JDBC client when configuring Hive on a secure cluster. The information is added to the administration doc for setting up JDBC, which was converted from wiki format to xml. The patch adds one doc file and modifies two auxiliary files: * docs/xdocs/admin_manual/hivejdbc.xml is the source doc for Hive JDBC setup. * project.xml adds a menu item for the JDBC setup doc, fixes a misnamed menu item (DDL, not DML), adds a link to the javadocs, and changes the capitalization of a few menu items. * site.vsl removes menu indentation and changes the copyright year to 2012 in HTML footers. Document JDBC client configuration for secure clusters -- Key: HIVE-3768 URL: https://issues.apache.org/jira/browse/HIVE-3768 Project: Hive Issue Type: Bug Components: Documentation Affects Versions: 0.9.0 Reporter: Lefty Leverenz Assignee: Lefty Leverenz Fix For: 0.10.0 Attachments: HIVE-3768.1.patch Document the JDBC client configuration required for starting Hive on a secure cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2439) Upgrade antlr version to 3.4
[ https://issues.apache.org/jira/browse/HIVE-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiruvel Thirumoolan updated HIVE-2439: --- Attachment: HIVE-2439_branch9.patch Work in progress patch for branch9. Inherits from Ashutosh's previous patch. Majority of the test cases that failed previously pass now, though there are still failures. For experimentation I used https://github.com/thiruvel/HiveANTLR34Issue and changed the grammar there and confirmed the same tree is generated with antlr 3.2 and 3.4. Feedback/Comments welcome. Upgrade antlr version to 3.4 Key: HIVE-2439 URL: https://issues.apache.org/jira/browse/HIVE-2439 Project: Hive Issue Type: Improvement Affects Versions: 0.8.0 Reporter: Ashutosh Chauhan Attachments: HIVE-2439_branch9.patch, hive-2439_incomplete.patch Upgrade antlr version to 3.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3400) Add Retries to Hive MetaStore Connections
[ https://issues.apache.org/jira/browse/HIVE-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509955#comment-13509955 ] Ashutosh Chauhan commented on HIVE-3400: Bhushan, Patch wasn't applying cleanly on trunk, so I had to resolve some conflicts. I did that and ran tests and all the test cases passed. Great progress! But, I have few minor comments which I left on phabricator. If you can take care of those and generate a patch against trunk and attach here, I will take care of committing and closing this issue. Add Retries to Hive MetaStore Connections - Key: HIVE-3400 URL: https://issues.apache.org/jira/browse/HIVE-3400 Project: Hive Issue Type: Improvement Components: Metastore Reporter: Bhushan Mandhani Assignee: Bhushan Mandhani Priority: Minor Labels: metastore Attachments: HIVE-3400.1.patch.txt, HIVE-3400.2.patch.txt Currently, when using Thrift to access the MetaStore, if the Thrift host dies, there is no mechanism to reconnect to some other host even if the MetaStore URIs variable in the Conf contains multiple hosts. Hive should retry and reconnect rather than throwing a communication link error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3255) Add DBTokenStore to store Delegation Tokens in DB
[
https://issues.apache.org/jira/browse/HIVE-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-3255:
---
Attachment: hive-3255_4.patch
Patch refreshed for latest trunk. Really appreciate if some committer can take
a look.
Add DBTokenStore to store Delegation Tokens in DB
-
Key: HIVE-3255
URL: https://issues.apache.org/jira/browse/HIVE-3255
Project: Hive
Issue Type: New Feature
Components: Metastore, Security
Affects Versions: 0.9.0
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan
Attachments: hive-3255_2.patch, hive-3255_3.patch, hive-3255_4.patch,
hive-3255.patch
Before HIVE-1696 metastore was completely stateless and all the data is in
backend db. HIVE-1696 added delegation tokens for metastore which metastore
needs to keep in memory. HIVE-2467 added support for storing delegation
tokens in ZooKeeper via an interface {{DelegationTokenStore}}. This jira is
about using DB backend for storing tokens which metastore uses for storing
data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3645) RCFileWriter does not implement the right function to support Federation
[
https://issues.apache.org/jira/browse/HIVE-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510061#comment-13510061
]
Ashutosh Chauhan commented on HIVE-3645:
Committed to 0.9 branch.
RCFileWriter does not implement the right function to support Federation
Key: HIVE-3645
URL: https://issues.apache.org/jira/browse/HIVE-3645
Project: Hive
Issue Type: Bug
Components: Serializers/Deserializers
Affects Versions: 0.9.0, 0.10.0
Environment: Hadoop 0.23.3 federation, Hive 0.9 and Pig 0.10
Reporter: Viraj Bhat
Assignee: Arup Malakar
Fix For: 0.11
Attachments: HIVE_3645_branch_0.patch, HIVE_3645_trunk_0.patch
Create a table using Hive DDL
{code}
CREATE TABLE tmp_hcat_federated_numbers_part_1 (
id int,
intnum int,
floatnum float
)partitioned by (
part1string,
part2string
)
STORED AS rcfile
LOCATION 'viewfs:///database/tmp_hcat_federated_numbers_part_1';
{code}
Populate it using Pig:
{code}
A = load 'default.numbers_pig' using org.apache.hcatalog.pig.HCatLoader();
B = filter A by id = 500;
C = foreach B generate (int)id, (int)intnum, (float)floatnum;
store C into
'default.tmp_hcat_federated_numbers_part_1'
using org.apache.hcatalog.pig.HCatStorer
('part1=pig, part2=hcat_pig_insert',
'id: int,intnum: int,floatnum: float');
{code}
Generates the following error when running on a Federated Cluster:
{quote}
2012-10-29 20:40:25,011 [main] ERROR
org.apache.pig.tools.pigstats.SimplePigStats - ERROR 2997: Unable to recreate
exception from backed error: AttemptID:attempt_1348522594824_0846_m_00_3
Info:Error: org.apache.hadoop.fs.viewfs.NotInMountpointException:
getDefaultReplication on empty path is invalid
at
org.apache.hadoop.fs.viewfs.ViewFileSystem.getDefaultReplication(ViewFileSystem.java:479)
at org.apache.hadoop.hive.ql.io.RCFile$Writer.init(RCFile.java:723)
at org.apache.hadoop.hive.ql.io.RCFile$Writer.init(RCFile.java:705)
at
org.apache.hadoop.hive.ql.io.RCFileOutputFormat.getRecordWriter(RCFileOutputFormat.java:86)
at
org.apache.hcatalog.mapreduce.FileOutputFormatContainer.getRecordWriter(FileOutputFormatContainer.java:100)
at
org.apache.hcatalog.mapreduce.HCatOutputFormat.getRecordWriter(HCatOutputFormat.java:228)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat.getRecordWriter(PigOutputFormat.java:84)
at
org.apache.hadoop.mapred.MapTask$NewDirectOutputCollector.init(MapTask.java:587)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:706)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:332)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:157)
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:1212)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:152)
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3769) Must publish new Hive-0.10 artifacts to apache repository.
Mithun Radhakrishnan created HIVE-3769: -- Summary: Must publish new Hive-0.10 artifacts to apache repository. Key: HIVE-3769 URL: https://issues.apache.org/jira/browse/HIVE-3769 Project: Hive Issue Type: Bug Components: Build Infrastructure, Thrift API Reporter: Mithun Radhakrishnan Fix For: 0.10.0 Hive-0.10 has successfully moved to Thrift-0.9. (HIVE-2715) Could we please also have the Hive-0.10 artifacts published on the Apache Repository? Please note that the currently published artifacts are pretty old. I suspect HIVE-2715 isn't available in the published artifact. https://repository.apache.org/content/groups/snapshots/org/apache/hive/hive-metastore/0.10.0-SNAPSHOT/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3769) Must publish new Hive-0.10 artifacts to apache repository.
[ https://issues.apache.org/jira/browse/HIVE-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mithun Radhakrishnan updated HIVE-3769: --- Affects Version/s: 0.10.0 Must publish new Hive-0.10 artifacts to apache repository. -- Key: HIVE-3769 URL: https://issues.apache.org/jira/browse/HIVE-3769 Project: Hive Issue Type: Bug Components: Build Infrastructure, Thrift API Affects Versions: 0.10.0 Reporter: Mithun Radhakrishnan Fix For: 0.10.0 Hive-0.10 has successfully moved to Thrift-0.9. (HIVE-2715) Could we please also have the Hive-0.10 artifacts published on the Apache Repository? Please note that the currently published artifacts are pretty old. I suspect HIVE-2715 isn't available in the published artifact. https://repository.apache.org/content/groups/snapshots/org/apache/hive/hive-metastore/0.10.0-SNAPSHOT/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3633) sort-merge join does not work with sub-queries
[ https://issues.apache.org/jira/browse/HIVE-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510084#comment-13510084 ] Kevin Wilfong commented on HIVE-3633: - +1 sort-merge join does not work with sub-queries -- Key: HIVE-3633 URL: https://issues.apache.org/jira/browse/HIVE-3633 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3633.1.patch, hive.3633.2.patch, hive.3633.3.patch, hive.3633.4.patch, hive.3633.5.patch, hive.3633.6.patch, hive.3633.7.patch, hive.3633.8.patch Consider the following query: create table smb_bucket_1(key int, value string) CLUSTERED BY (key) SORTED BY (key) INTO 6 BUCKETS STORED AS TEXTFILE; create table smb_bucket_2(key int, value string) CLUSTERED BY (key) SORTED BY (key) INTO 6 BUCKETS STORED AS TEXTFILE; -- load the above tables set hive.optimize.bucketmapjoin = true; set hive.optimize.bucketmapjoin.sortedmerge = true; set hive.input.format = org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat; explain select count(*) from ( select /*+mapjoin(a)*/ a.key as key1, b.key as key2, a.value as value1, b.value as value2 from smb_bucket_1 a join smb_bucket_2 b on a.key = b.key) subq; The above query does not use sort-merge join. This would be very useful as we automatically convert the queries to use sorting and bucketing properties for join. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3770) Test cases's broken in TestParse
Gang Tim Liu created HIVE-3770: -- Summary: Test cases's broken in TestParse Key: HIVE-3770 URL: https://issues.apache.org/jira/browse/HIVE-3770 Project: Hive Issue Type: Bug Components: Testing Infrastructure Reporter: Gang Tim Liu Assignee: Gang Tim Liu 20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750: 20 Test cases = testParse_case_sensitivity sample error ant test -Dtestcase=TestParse -Dqfile=groupby1.q [junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out ../ql/src/test/results/compiler/parse/groupby1.q.out [junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml ../ql/src/test/results/compiler/plan/groupby1.q.xml [junit] 1224,1226d1223 [junit] void property=maxStatsKeyPrefixLength [junit] int200/int [junit] /void -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3770) Test cases's broken in TestParse
[
https://issues.apache.org/jira/browse/HIVE-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gang Tim Liu updated HIVE-3770:
---
Description:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
was:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
sample error
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
Test cases's broken in TestParse
Key: HIVE-3770
URL: https://issues.apache.org/jira/browse/HIVE-3770
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Reporter: Gang Tim Liu
Assignee: Gang Tim Liu
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3770) Test cases's broken in TestParse
[
https://issues.apache.org/jira/browse/HIVE-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gang Tim Liu updated HIVE-3770:
---
Description:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
was:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
Test cases's broken in TestParse
Key: HIVE-3770
URL: https://issues.apache.org/jira/browse/HIVE-3770
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Reporter: Gang Tim Liu
Assignee: Gang Tim Liu
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3770) Test cases's broken in TestParse
[
https://issues.apache.org/jira/browse/HIVE-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gang Tim Liu updated HIVE-3770:
---
Description:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
testParse_input4
testParse_input5
testParse_input6
testParse_input7
testParse_input9
testParse_input_testsequencefile
testParse_join1
testParse_join2
testParse_join3
testParse_sample2
testParse_sample3
testParse_sample4
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
was:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
Test cases's broken in TestParse
Key: HIVE-3770
URL: https://issues.apache.org/jira/browse/HIVE-3770
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Reporter: Gang Tim Liu
Assignee: Gang Tim Liu
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
testParse_input4
testParse_input5
testParse_input6
testParse_input7
testParse_input9
testParse_input_testsequencefile
testParse_join1
testParse_join2
testParse_join3
testParse_sample2
testParse_sample3
testParse_sample4
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3770) Test cases's broken in TestParse
[
https://issues.apache.org/jira/browse/HIVE-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gang Tim Liu updated HIVE-3770:
---
Description:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
testParse_input4
testParse_input5
testParse_input6
testParse_input7
testParse_input9
testParse_input_testsequencefile
testParse_join1
testParse_join2
testParse_join3
testParse_sample2
testParse_sample3
testParse_sample4
testParse_sample5
testParse_sample6
testParse_sample7
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
was:
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
testParse_input4
testParse_input5
testParse_input6
testParse_input7
testParse_input9
testParse_input_testsequencefile
testParse_join1
testParse_join2
testParse_join3
testParse_sample2
testParse_sample3
testParse_sample4
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
Test cases's broken in TestParse
Key: HIVE-3770
URL: https://issues.apache.org/jira/browse/HIVE-3770
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Reporter: Gang Tim Liu
Assignee: Gang Tim Liu
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
testParse_input4
testParse_input5
testParse_input6
testParse_input7
testParse_input9
testParse_input_testsequencefile
testParse_join1
testParse_join2
testParse_join3
testParse_sample2
testParse_sample3
testParse_sample4
testParse_sample5
testParse_sample6
testParse_sample7
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (HIVE-3750) JDBCStatsPublisher fails when ID length exceeds length of ID column
[ https://issues.apache.org/jira/browse/HIVE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan reopened HIVE-3750: This is making quite a few test case in TestParse and elsewhere to fail, because golden files were not updated corresponding to maxStatsKeyPrefixLength config which is now showing up in the outputs. Please run all tests and update golden file (assuming they need to be updated). JDBCStatsPublisher fails when ID length exceeds length of ID column --- Key: HIVE-3750 URL: https://issues.apache.org/jira/browse/HIVE-3750 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3750.1.patch.txt When the length of the ID field passed to JDBCStatsPublisher exceeds the length of the column in the table (currently 255 characters) stats collection fails. This causes the entire query to fail when hive.stats.reliable is set to true. One way to prevent this would be to calculate a deterministic, very low collision hash of the ID prefix used for aggregation and use that when the length of the ID is too long. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3770) Test cases's broken in TestParse
[
https://issues.apache.org/jira/browse/HIVE-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510101#comment-13510101
]
Ashutosh Chauhan commented on HIVE-3770:
I also found this in my test run and commented on HIVE-3750 . I am fine if you
want to close the reopen I did there and want to provide a fix here.
Test cases's broken in TestParse
Key: HIVE-3770
URL: https://issues.apache.org/jira/browse/HIVE-3770
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Reporter: Gang Tim Liu
Assignee: Gang Tim Liu
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
testParse_input4
testParse_input5
testParse_input6
testParse_input7
testParse_input9
testParse_input_testsequencefile
testParse_join1
testParse_join2
testParse_join3
testParse_sample2
testParse_sample3
testParse_sample4
testParse_sample5
testParse_sample6
testParse_sample7
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification
[ https://issues.apache.org/jira/browse/HIVE-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-3384. Resolution: Fixed Fix Version/s: 0.11 Assignee: Mikhail Bautin Committed to trunk. Thanks, Shengsheng, Chris and Mikhail for your persistence on this one! HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification -- Key: HIVE-3384 URL: https://issues.apache.org/jira/browse/HIVE-3384 Project: Hive Issue Type: Bug Components: JDBC Reporter: Weidong Bian Assignee: Mikhail Bautin Priority: Minor Fix For: 0.11 Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch jdbc module couldn't be compiled with jdk7 as it adds some abstract method in the JDBC specification some error info: error: HiveCallableStatement is not abstract and does not override abstract method TgetObject(String,ClassT) in CallableStatement . . . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3766) Enable adding hooks to hive meta store init
[ https://issues.apache.org/jira/browse/HIVE-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3766: Status: Open (was: Patch Available) Comments on Phabricator Enable adding hooks to hive meta store init --- Key: HIVE-3766 URL: https://issues.apache.org/jira/browse/HIVE-3766 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jean Xu Assignee: Jean Xu We will enable hooks to be added to init HMSHandler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3762) Minor fix for 'tableName' in Hive.g
[ https://issues.apache.org/jira/browse/HIVE-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navis updated HIVE-3762: Status: Patch Available (was: Open) Minor fix for 'tableName' in Hive.g --- Key: HIVE-3762 URL: https://issues.apache.org/jira/browse/HIVE-3762 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Navis Assignee: Navis Priority: Trivial Attachments: HIVE-3762.D7143.1.patch Current definition for 'tableName' is (db=Identifier DOT)? tab=Identifier. If user specifies value default. for it, hive parser accepts default as table name and reserves . for next token but it's not valid. Really trivial but it is small needed part for improving query auto-completion (I'm doing it). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3762) Minor fix for 'tableName' in Hive.g
[ https://issues.apache.org/jira/browse/HIVE-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-3762: -- Attachment: HIVE-3762.D7143.1.patch navis requested code review of HIVE-3762 [jira] Minor fix for 'tableName' in Hive.g. Reviewers: JIRA DPAL-1939 Minor fix for tableName in Hive.g Current definition for 'tableName' is (db=Identifier DOT)? tab=Identifier. If user specifies value default. for it, hive parser accepts default as table name and reserves . for next token but it's not valid. Really trivial but it is small needed part for improving query auto-completion (I'm doing it). TEST PLAN EMPTY REVISION DETAIL https://reviews.facebook.net/D7143 AFFECTED FILES ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g ql/src/test/results/clientnegative/invalid_tbl_name.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/16887/ To: JIRA, navis Minor fix for 'tableName' in Hive.g --- Key: HIVE-3762 URL: https://issues.apache.org/jira/browse/HIVE-3762 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Navis Assignee: Navis Priority: Trivial Attachments: HIVE-3762.D7143.1.patch Current definition for 'tableName' is (db=Identifier DOT)? tab=Identifier. If user specifies value default. for it, hive parser accepts default as table name and reserves . for next token but it's not valid. Really trivial but it is small needed part for improving query auto-completion (I'm doing it). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3771) HIVE-3750 broke TestParse
Kevin Wilfong created HIVE-3771: --- Summary: HIVE-3750 broke TestParse Key: HIVE-3771 URL: https://issues.apache.org/jira/browse/HIVE-3771 Project: Hive Issue Type: Bug Components: Testing Infrastructure Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong see title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3648) HiveMetaStoreFsImpl is not compatible with hadoop viewfs
[ https://issues.apache.org/jira/browse/HIVE-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arup Malakar updated HIVE-3648: --- Attachment: HIVE_3648_branch_1.patch Rebased branch patch. HiveMetaStoreFsImpl is not compatible with hadoop viewfs Key: HIVE-3648 URL: https://issues.apache.org/jira/browse/HIVE-3648 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.9.0, 0.10.0 Reporter: Kihwal Lee Assignee: Arup Malakar Fix For: 0.11 Attachments: HIVE_3648_branch_0.patch, HIVE_3648_branch_1.patch, HIVE-3648-trunk-0.patch, HIVE_3648_trunk_1.patch, HIVE-3648-trunk-1.patch HiveMetaStoreFsImpl#deleteDir() method calls Trash#moveToTrash(). This may not work when viewfs is used. It needs to call Trash#moveToAppropriateTrash() instead. Please note that this method is not available in hadoop versions earlier than 0.23. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3645) RCFileWriter does not implement the right function to support Federation
[
https://issues.apache.org/jira/browse/HIVE-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510143#comment-13510143
]
Arup Malakar commented on HIVE-3645:
Thank you Ashutosh.
RCFileWriter does not implement the right function to support Federation
Key: HIVE-3645
URL: https://issues.apache.org/jira/browse/HIVE-3645
Project: Hive
Issue Type: Bug
Components: Serializers/Deserializers
Affects Versions: 0.9.0, 0.10.0
Environment: Hadoop 0.23.3 federation, Hive 0.9 and Pig 0.10
Reporter: Viraj Bhat
Assignee: Arup Malakar
Fix For: 0.11
Attachments: HIVE_3645_branch_0.patch, HIVE_3645_trunk_0.patch
Create a table using Hive DDL
{code}
CREATE TABLE tmp_hcat_federated_numbers_part_1 (
id int,
intnum int,
floatnum float
)partitioned by (
part1string,
part2string
)
STORED AS rcfile
LOCATION 'viewfs:///database/tmp_hcat_federated_numbers_part_1';
{code}
Populate it using Pig:
{code}
A = load 'default.numbers_pig' using org.apache.hcatalog.pig.HCatLoader();
B = filter A by id = 500;
C = foreach B generate (int)id, (int)intnum, (float)floatnum;
store C into
'default.tmp_hcat_federated_numbers_part_1'
using org.apache.hcatalog.pig.HCatStorer
('part1=pig, part2=hcat_pig_insert',
'id: int,intnum: int,floatnum: float');
{code}
Generates the following error when running on a Federated Cluster:
{quote}
2012-10-29 20:40:25,011 [main] ERROR
org.apache.pig.tools.pigstats.SimplePigStats - ERROR 2997: Unable to recreate
exception from backed error: AttemptID:attempt_1348522594824_0846_m_00_3
Info:Error: org.apache.hadoop.fs.viewfs.NotInMountpointException:
getDefaultReplication on empty path is invalid
at
org.apache.hadoop.fs.viewfs.ViewFileSystem.getDefaultReplication(ViewFileSystem.java:479)
at org.apache.hadoop.hive.ql.io.RCFile$Writer.init(RCFile.java:723)
at org.apache.hadoop.hive.ql.io.RCFile$Writer.init(RCFile.java:705)
at
org.apache.hadoop.hive.ql.io.RCFileOutputFormat.getRecordWriter(RCFileOutputFormat.java:86)
at
org.apache.hcatalog.mapreduce.FileOutputFormatContainer.getRecordWriter(FileOutputFormatContainer.java:100)
at
org.apache.hcatalog.mapreduce.HCatOutputFormat.getRecordWriter(HCatOutputFormat.java:228)
at
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigOutputFormat.getRecordWriter(PigOutputFormat.java:84)
at
org.apache.hadoop.mapred.MapTask$NewDirectOutputCollector.init(MapTask.java:587)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:706)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:332)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:157)
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:1212)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:152)
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3771) HIVE-3750 broke TestParse
[ https://issues.apache.org/jira/browse/HIVE-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510144#comment-13510144 ] Kevin Wilfong commented on HIVE-3771: - https://reviews.facebook.net/D7149 HIVE-3750 broke TestParse - Key: HIVE-3771 URL: https://issues.apache.org/jira/browse/HIVE-3771 Project: Hive Issue Type: Bug Components: Testing Infrastructure Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3771.1.patch.txt see title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3771) HIVE-3750 broke TestParse
[ https://issues.apache.org/jira/browse/HIVE-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3771: Status: Patch Available (was: Open) HIVE-3750 broke TestParse - Key: HIVE-3771 URL: https://issues.apache.org/jira/browse/HIVE-3771 Project: Hive Issue Type: Bug Components: Testing Infrastructure Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3771.1.patch.txt see title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3771) HIVE-3750 broke TestParse
[ https://issues.apache.org/jira/browse/HIVE-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wilfong updated HIVE-3771: Attachment: HIVE-3771.1.patch.txt HIVE-3750 broke TestParse - Key: HIVE-3771 URL: https://issues.apache.org/jira/browse/HIVE-3771 Project: Hive Issue Type: Bug Components: Testing Infrastructure Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3771.1.patch.txt see title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3750) JDBCStatsPublisher fails when ID length exceeds length of ID column
[ https://issues.apache.org/jira/browse/HIVE-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510146#comment-13510146 ] Kevin Wilfong commented on HIVE-3750: - Sorry about that. I filed HIVE-3771 to fix it and attached a diff. I only saw failures in TestParse. JDBCStatsPublisher fails when ID length exceeds length of ID column --- Key: HIVE-3750 URL: https://issues.apache.org/jira/browse/HIVE-3750 Project: Hive Issue Type: Bug Components: Statistics Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3750.1.patch.txt When the length of the ID field passed to JDBCStatsPublisher exceeds the length of the column in the table (currently 255 characters) stats collection fails. This causes the entire query to fail when hive.stats.reliable is set to true. One way to prevent this would be to calculate a deterministic, very low collision hash of the ID prefix used for aggregation and use that when the length of the ID is too long. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-3770) Test cases's broken in TestParse
[
https://issues.apache.org/jira/browse/HIVE-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gang Tim Liu resolved HIVE-3770.
Resolution: Duplicate
Test cases's broken in TestParse
Key: HIVE-3770
URL: https://issues.apache.org/jira/browse/HIVE-3770
Project: Hive
Issue Type: Bug
Components: Testing Infrastructure
Reporter: Gang Tim Liu
Assignee: Gang Tim Liu
20 TestParse test cases are broken. It's introduced from D7017 HIVE-3750:
20 Test cases
=
testParse_case_sensitivity
testParse_groupby1
testParse_input1
testParse_input2
testParse_input3
testParse_input4
testParse_input5
testParse_input6
testParse_input7
testParse_input9
testParse_input_testsequencefile
testParse_join1
testParse_join2
testParse_join3
testParse_sample2
testParse_sample3
testParse_sample4
testParse_sample5
testParse_sample6
testParse_sample7
sample error
{quote}
ant test -Dtestcase=TestParse -Dqfile=groupby1.q
[junit] diff -a ../build/ql/test/logs/positive/groupby1.q.out
../ql/src/test/results/compiler/parse/groupby1.q.out
[junit] diff -a -b ../build/ql/test/logs/positive/groupby1.q.xml
../ql/src/test/results/compiler/plan/groupby1.q.xml
[junit] 1224,1226d1223
[junit] void property=maxStatsKeyPrefixLength
[junit] int200/int
[junit] /void
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3766) Enable adding hooks to hive meta store init
[ https://issues.apache.org/jira/browse/HIVE-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean Xu updated HIVE-3766: -- Status: Patch Available (was: Open) https://reviews.facebook.net/D7113 is ready for review Enable adding hooks to hive meta store init --- Key: HIVE-3766 URL: https://issues.apache.org/jira/browse/HIVE-3766 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jean Xu Assignee: Jean Xu We will enable hooks to be added to init HMSHandler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3381) Result of outer join is not valid
[
https://issues.apache.org/jira/browse/HIVE-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Navis updated HIVE-3381:
Status: Patch Available (was: Open)
Result of outer join is not valid
-
Key: HIVE-3381
URL: https://issues.apache.org/jira/browse/HIVE-3381
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.10.0
Reporter: Navis
Assignee: Navis
Priority: Critical
Attachments: HIVE-3381.D5565.3.patch, HIVE-3381.D5565.4.patch
Outer joins, especially full outer joins or outer join with filter on 'ON
clause' is not showing proper results. For example, query in test join_1to1.q
{code}
SELECT * FROM join_1to1_1 a full outer join join_1to1_2 b on a.key1 = b.key1
and a.value = 66 and b.value = 66 ORDER BY a.key1 ASC, a.key2 ASC, a.value
ASC, b.key1 ASC, b.key2 ASC, b.value ASC;
{code}
results
{code}
NULL NULLNULLNULLNULL66
NULL NULLNULLNULL10050 66
NULL NULLNULL10 10010 66
NULL NULLNULL30 10030 88
NULL NULLNULL35 10035 88
NULL NULLNULL40 10040 88
NULL NULLNULL40 10040 88
NULL NULLNULL50 10050 88
NULL NULLNULL50 10050 88
NULL NULLNULL50 10050 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULL66 NULLNULLNULL
NULL 10050 66 NULLNULLNULL
5 10005 66 5 10005 66
1510015 66 NULLNULLNULL
2010020 66 20 10020 66
2510025 88 NULLNULLNULL
3010030 66 NULLNULLNULL
3510035 88 NULLNULLNULL
4010040 66 NULLNULLNULL
4010040 66 40 10040 66
4010040 88 NULLNULLNULL
4010040 88 NULLNULLNULL
5010050 66 NULLNULLNULL
5010050 66 50 10050 66
5010050 66 50 10050 66
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
6010040 66 60 10040 66
6010040 66 60 10040 66
6010040 66 60 10040 66
6010040 66 60 10040 66
7010040 66 NULLNULLNULL
7010040 66 NULLNULLNULL
7010040 66 NULLNULLNULL
7010040 66 NULLNULLNULL
8010040 88 NULLNULLNULL
8010040 88 NULLNULLNULL
8010040 88 NULLNULLNULL
8010040 88 NULLNULLNULL
{code}
but it seemed not right. This should be
{code}
NULL NULLNULLNULLNULL66
NULL NULLNULLNULL10050 66
NULL NULLNULL10 10010 66
NULL NULLNULL25 10025 66
NULL NULLNULL30 10030 88
NULL NULLNULL35 10035 88
NULL NULLNULL40 10040 88
NULL NULLNULL50 10050 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULLNULL80 10040 66
NULL NULLNULL80 10040 66
NULL NULL66 NULLNULLNULL
NULL 10050 66 NULLNULLNULL
5 10005 66 5 10005 66
1510015 66 NULLNULLNULL
2010020 66 20 10020 66
2510025 88 NULLNULLNULL
3010030 66 NULLNULLNULL
3510035 88 NULLNULLNULL
4010040 66 40 10040 66
4010040 88 NULLNULLNULL
5010050 66 50 10050 66
5010050 66 50 10050 66
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
6010040 66 60 10040 66
6010040 66 60 10040 66
6010040 66 60 10040 66
6010040 66 60 10040 66
7010040 66 NULLNULLNULL
7010040 66 NULLNULLNULL
8010040 88 NULLNULLNULL
8010040 88 NULLNULLNULL
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3381) Result of outer join is not valid
[
https://issues.apache.org/jira/browse/HIVE-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-3381:
--
Attachment: HIVE-3381.D5565.4.patch
navis updated the revision HIVE-3381 [jira] Result of outer join is not valid.
Reviewers: JIRA
1. Simplified code a little
2. Added comments including example
3. Rebased on trunk passed all tests
REVISION DETAIL
https://reviews.facebook.net/D5565
AFFECTED FILES
ql/src/java/org/apache/hadoop/hive/ql/exec/CommonJoinOperator.java
ql/src/java/org/apache/hadoop/hive/ql/exec/HashTableSinkOperator.java
ql/src/java/org/apache/hadoop/hive/ql/exec/JoinOperator.java
ql/src/java/org/apache/hadoop/hive/ql/exec/JoinUtil.java
ql/src/java/org/apache/hadoop/hive/ql/exec/MapJoinOperator.java
ql/src/java/org/apache/hadoop/hive/ql/exec/SMBMapJoinOperator.java
ql/src/java/org/apache/hadoop/hive/ql/exec/persistence/MapJoinObjectValue.java
ql/src/test/results/clientpositive/auto_join21.q.out
ql/src/test/results/clientpositive/auto_join29.q.out
ql/src/test/results/clientpositive/auto_join7.q.out
ql/src/test/results/clientpositive/auto_join_filters.q.out
ql/src/test/results/clientpositive/join21.q.out
ql/src/test/results/clientpositive/join7.q.out
ql/src/test/results/clientpositive/join_1to1.q.out
ql/src/test/results/clientpositive/join_filters.q.out
ql/src/test/results/clientpositive/join_filters_overlap.q.out
To: JIRA, navis
Cc: njain
Result of outer join is not valid
-
Key: HIVE-3381
URL: https://issues.apache.org/jira/browse/HIVE-3381
Project: Hive
Issue Type: Bug
Components: Query Processor
Affects Versions: 0.10.0
Reporter: Navis
Assignee: Navis
Priority: Critical
Attachments: HIVE-3381.D5565.3.patch, HIVE-3381.D5565.4.patch
Outer joins, especially full outer joins or outer join with filter on 'ON
clause' is not showing proper results. For example, query in test join_1to1.q
{code}
SELECT * FROM join_1to1_1 a full outer join join_1to1_2 b on a.key1 = b.key1
and a.value = 66 and b.value = 66 ORDER BY a.key1 ASC, a.key2 ASC, a.value
ASC, b.key1 ASC, b.key2 ASC, b.value ASC;
{code}
results
{code}
NULL NULLNULLNULLNULL66
NULL NULLNULLNULL10050 66
NULL NULLNULL10 10010 66
NULL NULLNULL30 10030 88
NULL NULLNULL35 10035 88
NULL NULLNULL40 10040 88
NULL NULLNULL40 10040 88
NULL NULLNULL50 10050 88
NULL NULLNULL50 10050 88
NULL NULLNULL50 10050 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULL66 NULLNULLNULL
NULL 10050 66 NULLNULLNULL
5 10005 66 5 10005 66
1510015 66 NULLNULLNULL
2010020 66 20 10020 66
2510025 88 NULLNULLNULL
3010030 66 NULLNULLNULL
3510035 88 NULLNULLNULL
4010040 66 NULLNULLNULL
4010040 66 40 10040 66
4010040 88 NULLNULLNULL
4010040 88 NULLNULLNULL
5010050 66 NULLNULLNULL
5010050 66 50 10050 66
5010050 66 50 10050 66
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
5010050 88 NULLNULLNULL
6010040 66 60 10040 66
6010040 66 60 10040 66
6010040 66 60 10040 66
6010040 66 60 10040 66
7010040 66 NULLNULLNULL
7010040 66 NULLNULLNULL
7010040 66 NULLNULLNULL
7010040 66 NULLNULLNULL
8010040 88 NULLNULLNULL
8010040 88 NULLNULLNULL
8010040 88 NULLNULLNULL
8010040 88 NULLNULLNULL
{code}
but it seemed not right. This should be
{code}
NULL NULLNULLNULLNULL66
NULL NULLNULLNULL10050 66
NULL NULLNULL10 10010 66
NULL NULLNULL25 10025 66
NULL NULLNULL30 10030 88
NULL NULLNULL35 10035 88
NULL NULLNULL40 10040 88
NULL NULLNULL50 10050 88
NULL NULLNULL70 10040 88
NULL NULLNULL70 10040 88
NULL NULLNULL80 10040 66
NULL NULLNULL80 10040 66
NULL NULL66 NULLNULLNULL
[jira] [Updated] (HIVE-3589) describe/show partition/show tblproperties command should accept database name
[ https://issues.apache.org/jira/browse/HIVE-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navis updated HIVE-3589: Status: Patch Available (was: Open) describe/show partition/show tblproperties command should accept database name -- Key: HIVE-3589 URL: https://issues.apache.org/jira/browse/HIVE-3589 Project: Hive Issue Type: Bug Components: Metastore, Query Processor Affects Versions: 0.8.1 Reporter: Sujesh Chirackkal Assignee: Navis Priority: Minor Attachments: HIVE-3589.D6075.1.patch, HIVE-3589.D6075.2.patch describe command not giving the details when called as describe dbname.tablename. Throwing the error Table dbname not found. Ex: hive -e describe masterdb.table1 will throw error Table masterdb not found -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3464) Merging join tree may reorder joins which could be invalid
[ https://issues.apache.org/jira/browse/HIVE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-3464: -- Attachment: HIVE-3464.D5409.2.patch navis updated the revision HIVE-3464 [jira] Merging join tree may reorder joins which could be invalid. Reviewers: JIRA Rebase on trunk REVISION DETAIL https://reviews.facebook.net/D5409 AFFECTED FILES ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java ql/src/test/queries/clientpositive/mergejoins_mixed.q ql/src/test/results/clientpositive/mergejoins_mixed.q.out To: JIRA, navis Merging join tree may reorder joins which could be invalid -- Key: HIVE-3464 URL: https://issues.apache.org/jira/browse/HIVE-3464 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Attachments: HIVE-3464.D5409.2.patch Currently, hive merges join tree from right to left regardless of join types, which may introduce join reordering. For example, select * from a join a b on a.key=b.key join a c on b.key=c.key join a d on a.key=d.key; Hive tries to merge join tree in a-d=b-d, a-d=a-b, b-c=a-b order and a-d=a-b and b-c=a-b will be merged. Final join tree is a-(bdc). With this, ab-d join will be executed prior to ab-c. But if join type of -c and -d is different, this is not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3648) HiveMetaStoreFsImpl is not compatible with hadoop viewfs
[ https://issues.apache.org/jira/browse/HIVE-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510214#comment-13510214 ] Ashutosh Chauhan commented on HIVE-3648: Committed to 0.9 branch. HiveMetaStoreFsImpl is not compatible with hadoop viewfs Key: HIVE-3648 URL: https://issues.apache.org/jira/browse/HIVE-3648 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.9.0, 0.10.0 Reporter: Kihwal Lee Assignee: Arup Malakar Fix For: 0.11 Attachments: HIVE_3648_branch_0.patch, HIVE_3648_branch_1.patch, HIVE-3648-trunk-0.patch, HIVE_3648_trunk_1.patch, HIVE-3648-trunk-1.patch HiveMetaStoreFsImpl#deleteDir() method calls Trash#moveToTrash(). This may not work when viewfs is used. It needs to call Trash#moveToAppropriateTrash() instead. Please note that this method is not available in hadoop versions earlier than 0.23. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (HIVE-3073) Hive List Bucketing - DML support
[ https://issues.apache.org/jira/browse/HIVE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-3073 started by Gang Tim Liu. Hive List Bucketing - DML support -- Key: HIVE-3073 URL: https://issues.apache.org/jira/browse/HIVE-3073 Project: Hive Issue Type: New Feature Components: SQL Affects Versions: 0.10.0 Reporter: Gang Tim Liu Assignee: Gang Tim Liu Attachments: HIVE-3073.patch.12, HIVE-3073.patch.13, HIVE-3073.patch.15, HIVE-3073.patch.18, HIVE-3073.patch.19, HIVE-3073.patch.21, HIVE-3073.patch.22, HIVE-3073.patch.24, HIVE-3073.patch.26 If a hive table column has skewed keys, query performance on non-skewed key is always impacted. Hive List Bucketing feature will address it: https://cwiki.apache.org/Hive/listbucketing.html This jira issue will track DML change for the feature: 1. single skewed column 2. manual load data -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3073) Hive List Bucketing - DML support
[ https://issues.apache.org/jira/browse/HIVE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gang Tim Liu updated HIVE-3073: --- Attachment: HIVE-3073.patch.26 Hive List Bucketing - DML support -- Key: HIVE-3073 URL: https://issues.apache.org/jira/browse/HIVE-3073 Project: Hive Issue Type: New Feature Components: SQL Affects Versions: 0.10.0 Reporter: Gang Tim Liu Assignee: Gang Tim Liu Attachments: HIVE-3073.patch.12, HIVE-3073.patch.13, HIVE-3073.patch.15, HIVE-3073.patch.18, HIVE-3073.patch.19, HIVE-3073.patch.21, HIVE-3073.patch.22, HIVE-3073.patch.24, HIVE-3073.patch.26 If a hive table column has skewed keys, query performance on non-skewed key is always impacted. Hive List Bucketing feature will address it: https://cwiki.apache.org/Hive/listbucketing.html This jira issue will track DML change for the feature: 1. single skewed column 2. manual load data -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3073) Hive List Bucketing - DML support
[ https://issues.apache.org/jira/browse/HIVE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gang Tim Liu updated HIVE-3073: --- Status: Patch Available (was: In Progress) patch is available on both phabricator and attachment. Hive List Bucketing - DML support -- Key: HIVE-3073 URL: https://issues.apache.org/jira/browse/HIVE-3073 Project: Hive Issue Type: New Feature Components: SQL Affects Versions: 0.10.0 Reporter: Gang Tim Liu Assignee: Gang Tim Liu Attachments: HIVE-3073.patch.12, HIVE-3073.patch.13, HIVE-3073.patch.15, HIVE-3073.patch.18, HIVE-3073.patch.19, HIVE-3073.patch.21, HIVE-3073.patch.22, HIVE-3073.patch.24, HIVE-3073.patch.26 If a hive table column has skewed keys, query performance on non-skewed key is always impacted. Hive List Bucketing feature will address it: https://cwiki.apache.org/Hive/listbucketing.html This jira issue will track DML change for the feature: 1. single skewed column 2. manual load data -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3745) Hive does improper = based string comparisons for strings with trailing whitespaces
[
https://issues.apache.org/jira/browse/HIVE-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510258#comment-13510258
]
Harsh J commented on HIVE-3745:
---
My colleague, [~esteban], pointed out that the SQL92 standard
(http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt, 8.2 comparison
predicate) qualifies this thought and that Hive does have a bug.
Hive does improper = based string comparisons for strings with trailing
whitespaces
-
Key: HIVE-3745
URL: https://issues.apache.org/jira/browse/HIVE-3745
Project: Hive
Issue Type: Bug
Components: SQL
Affects Versions: 0.9.0
Reporter: Harsh J
Compared to other systems such as DB2, MySQL, etc., which disregard trailing
whitespaces in a string used when comparing two strings with the {{=}}
relational operator, Hive does not do this.
For example, note the following line from the MySQL manual:
http://dev.mysql.com/doc/refman/5.1/en/char.html
{quote}
All MySQL collations are of type PADSPACE. This means that all CHAR and
VARCHAR values in MySQL are compared without regard to any trailing spaces.
{quote}
Hive still is whitespace sensitive and regards trailing spaces of a string as
worthy elements when comparing. Ideally {{LIKE}} should consider this
strongly, but {{=}} should not.
Is there a specific reason behind this difference of implementation in Hive's
SQL?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3384) HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification
[ https://issues.apache.org/jira/browse/HIVE-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Bautin updated HIVE-3384: - Attachment: HIVE-3384-branch-0.9.patch Attaching a version of the patch for the 0.9 branch. [~ashutoshc]: Thank you for taking care of this JIRA. Could you please commit this one to the 0.9 branch as well? HIVE JDBC module won't compile under JDK1.7 as new methods added in JDBC specification -- Key: HIVE-3384 URL: https://issues.apache.org/jira/browse/HIVE-3384 Project: Hive Issue Type: Bug Components: JDBC Reporter: Weidong Bian Assignee: Mikhail Bautin Priority: Minor Fix For: 0.11 Attachments: D6873-0.9.1.patch, D6873.1.patch, D6873.2.patch, D6873.3.patch, D6873.4.patch, D6873.5.patch, D6873.6.patch, D6873.7.patch, HIVE-3384-2012-12-02.patch, HIVE-3384-2012-12-04.patch, HIVE-3384.2.patch, HIVE-3384-branch-0.9.patch, HIVE-3384.patch, HIVE-JDK7-JDBC.patch jdbc module couldn't be compiled with jdk7 as it adds some abstract method in the JDBC specification some error info: error: HiveCallableStatement is not abstract and does not override abstract method TgetObject(String,ClassT) in CallableStatement . . . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3401) Diversify grammar for split sampling
[ https://issues.apache.org/jira/browse/HIVE-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navis updated HIVE-3401: Status: Patch Available (was: Open) Running test Diversify grammar for split sampling Key: HIVE-3401 URL: https://issues.apache.org/jira/browse/HIVE-3401 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Navis Assignee: Navis Priority: Trivial Attachments: HIVE-3401.D4821.2.patch Current split sampling only supports grammar like TABLESAMPLE(n PERCENT). But some users wants to specify just the size of input. It can be easily calculated with a few commands but it seemed good to support more grammars something like TABLESAMPLE(500M). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3464) Merging join tree may reorder joins which could be invalid
[ https://issues.apache.org/jira/browse/HIVE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navis updated HIVE-3464: Status: Patch Available (was: Open) Running test Merging join tree may reorder joins which could be invalid -- Key: HIVE-3464 URL: https://issues.apache.org/jira/browse/HIVE-3464 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.10.0 Reporter: Navis Assignee: Navis Attachments: HIVE-3464.D5409.2.patch Currently, hive merges join tree from right to left regardless of join types, which may introduce join reordering. For example, select * from a join a b on a.key=b.key join a c on b.key=c.key join a d on a.key=d.key; Hive tries to merge join tree in a-d=b-d, a-d=a-b, b-c=a-b order and a-d=a-b and b-c=a-b will be merged. Final join tree is a-(bdc). With this, ab-d join will be executed prior to ab-c. But if join type of -c and -d is different, this is not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3401) Diversify grammar for split sampling
[ https://issues.apache.org/jira/browse/HIVE-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-3401: -- Attachment: HIVE-3401.D4821.2.patch navis updated the revision HIVE-3401 [jira] Diversify grammar for split sampling. Reviewers: JIRA Support row num per split REVISION DETAIL https://reviews.facebook.net/D4821 AFFECTED FILES ql/src/java/org/apache/hadoop/hive/ql/exec/ExplainTask.java ql/src/java/org/apache/hadoop/hive/ql/exec/FetchOperator.java ql/src/java/org/apache/hadoop/hive/ql/exec/MapRedTask.java ql/src/java/org/apache/hadoop/hive/ql/exec/TableScanOperator.java ql/src/java/org/apache/hadoop/hive/ql/io/CombineHiveInputFormat.java ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g ql/src/java/org/apache/hadoop/hive/ql/parse/ParseDriver.java ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java ql/src/java/org/apache/hadoop/hive/ql/parse/SplitSample.java ql/src/java/org/apache/hadoop/hive/ql/plan/MapredWork.java ql/src/java/org/apache/hadoop/hive/ql/plan/TableScanDesc.java ql/src/test/queries/clientpositive/split_sample.q ql/src/test/results/clientpositive/split_sample.q.out To: JIRA, navis Diversify grammar for split sampling Key: HIVE-3401 URL: https://issues.apache.org/jira/browse/HIVE-3401 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Navis Assignee: Navis Priority: Trivial Attachments: HIVE-3401.D4821.2.patch Current split sampling only supports grammar like TABLESAMPLE(n PERCENT). But some users wants to specify just the size of input. It can be easily calculated with a few commands but it seemed good to support more grammars something like TABLESAMPLE(500M). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3771) HIVE-3750 broke TestParse
[ https://issues.apache.org/jira/browse/HIVE-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510320#comment-13510320 ] Namit Jain commented on HIVE-3771: -- +1 HIVE-3750 broke TestParse - Key: HIVE-3771 URL: https://issues.apache.org/jira/browse/HIVE-3771 Project: Hive Issue Type: Bug Components: Testing Infrastructure Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3771.1.patch.txt see title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2723) should throw Ambiguous column reference key Exception in particular join condition
[ https://issues.apache.org/jira/browse/HIVE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navis updated HIVE-2723: Affects Version/s: (was: 0.9.0) Status: Patch Available (was: Open) should throw Ambiguous column reference key Exception in particular join condition -- Key: HIVE-2723 URL: https://issues.apache.org/jira/browse/HIVE-2723 Project: Hive Issue Type: Bug Components: Query Processor Environment: Linux zongren-VirtualBox 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:34:47 UTC 2011 i686 i686 i386 GNU/Linux java version 1.6.0_25 hadoop-0.20.2-cdh3u0 hive-0.7.0-cdh3u0 Reporter: caofangkun Assignee: Navis Priority: Minor Labels: exception-handling, query, queryparser Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2723.D1275.1.patch, ASF.LICENSE.NOT.GRANTED--HIVE-2723.D1275.2.patch, HIVE-2723.D1275.3.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3765) Bucket map join optimization not applied to left semi join
[ https://issues.apache.org/jira/browse/HIVE-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-3765: Assignee: Gang Tim Liu Bucket map join optimization not applied to left semi join -- Key: HIVE-3765 URL: https://issues.apache.org/jira/browse/HIVE-3765 Project: Hive Issue Type: Bug Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Gang Tim Liu When all the hints and settings are present to use the bucket map join optimization, it will not get applied if the join is a left semi join. It works for left outer joins, so it seems it should work for left semi joins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3745) Hive does improper = based string comparisons for strings with trailing whitespaces
[
https://issues.apache.org/jira/browse/HIVE-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Namit Jain reassigned HIVE-3745:
Assignee: Gang Tim Liu
Hive does improper = based string comparisons for strings with trailing
whitespaces
-
Key: HIVE-3745
URL: https://issues.apache.org/jira/browse/HIVE-3745
Project: Hive
Issue Type: Bug
Components: SQL
Affects Versions: 0.9.0
Reporter: Harsh J
Assignee: Gang Tim Liu
Compared to other systems such as DB2, MySQL, etc., which disregard trailing
whitespaces in a string used when comparing two strings with the {{=}}
relational operator, Hive does not do this.
For example, note the following line from the MySQL manual:
http://dev.mysql.com/doc/refman/5.1/en/char.html
{quote}
All MySQL collations are of type PADSPACE. This means that all CHAR and
VARCHAR values in MySQL are compared without regard to any trailing spaces.
{quote}
Hive still is whitespace sensitive and regards trailing spaces of a string as
worthy elements when comparing. Ideally {{LIKE}} should consider this
strongly, but {{=}} should not.
Is there a specific reason behind this difference of implementation in Hive's
SQL?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3728) make optimizing multi-group by configurable
[ https://issues.apache.org/jira/browse/HIVE-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-3728: Assignee: Namit Jain make optimizing multi-group by configurable --- Key: HIVE-3728 URL: https://issues.apache.org/jira/browse/HIVE-3728 Project: Hive Issue Type: Bug Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain This was done as part of https://issues.apache.org/jira/browse/HIVE-609. This should be configurable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3710) HiveConf.ConfVars.HIVE_STATS_COLLECT_RAWDATASIZE should not be checked in FileSinkOperator
[ https://issues.apache.org/jira/browse/HIVE-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-3710: Assignee: Gang Tim Liu HiveConf.ConfVars.HIVE_STATS_COLLECT_RAWDATASIZE should not be checked in FileSinkOperator -- Key: HIVE-3710 URL: https://issues.apache.org/jira/browse/HIVE-3710 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Namit Jain Assignee: Gang Tim Liu It should be part of the plan instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3506) CombineHiveInputFormat doesn't support sub-directory in input path
[
https://issues.apache.org/jira/browse/HIVE-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Namit Jain reassigned HIVE-3506:
Assignee: Gang Tim Liu
CombineHiveInputFormat doesn't support sub-directory in input path
--
Key: HIVE-3506
URL: https://issues.apache.org/jira/browse/HIVE-3506
Project: Hive
Issue Type: Bug
Components: Query Processor
Reporter: Gang Tim Liu
Assignee: Gang Tim Liu
If hive.input.format is org.apache.hadoop.hive.ql.io.CombineHiveInputFormat,
the following test will fail with java.io.FileNotFoundException: ... (No such
file or directory)
– INCLUDE_HADOOP_MAJOR_VERSIONS(0.23)
CREATE TABLE fact_daily(x int) PARTITIONED BY (ds STRING);
CREATE TABLE fact_tz(x int) PARTITIONED BY (ds STRING, hr STRING)
LOCATION 'pfile:${system:test.tmp.dir}/fact_tz';
INSERT OVERWRITE TABLE fact_tz PARTITION (ds='1', hr='1')
SELECT key+11 FROM src WHERE key=484;
ALTER TABLE fact_daily SET TBLPROPERTIES('EXTERNAL'='TRUE');
ALTER TABLE fact_daily ADD PARTITION (ds='1')
LOCATION 'pfile:${system:test.tmp.dir}/fact_tz/ds=1';
set mapred.input.dir.recursive=true;
SELECT * FROM fact_daily WHERE ds='1';
SELECT count(1) FROM fact_daily WHERE ds='1';
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3348) semi-colon in comments in .q file does not work
[ https://issues.apache.org/jira/browse/HIVE-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-3348: Assignee: Namit Jain semi-colon in comments in .q file does not work --- Key: HIVE-3348 URL: https://issues.apache.org/jira/browse/HIVE-3348 Project: Hive Issue Type: Bug Components: Testing Infrastructure Reporter: Namit Jain Assignee: Namit Jain -- comment ; -- comment select count(1) from src; The above test file fails -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3316) The order of the joined tables should be based on the sizes of the tables/partitions being joined
[ https://issues.apache.org/jira/browse/HIVE-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-3316: Assignee: Namit Jain The order of the joined tables should be based on the sizes of the tables/partitions being joined - Key: HIVE-3316 URL: https://issues.apache.org/jira/browse/HIVE-3316 Project: Hive Issue Type: New Feature Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Currently, the join order is based on the order in which the user specified the tables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3328) add thrift APIs to create/drop views
[ https://issues.apache.org/jira/browse/HIVE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-3328: Assignee: Namit Jain add thrift APIs to create/drop views Key: HIVE-3328 URL: https://issues.apache.org/jira/browse/HIVE-3328 Project: Hive Issue Type: New Feature Components: Metastore, Views Reporter: Namit Jain Assignee: Namit Jain -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3772) Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin)
Mikhail Bautin created HIVE-3772: Summary: Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin) Key: HIVE-3772 URL: https://issues.apache.org/jira/browse/HIVE-3772 Project: Hive Issue Type: Bug Reporter: Mikhail Bautin Creating a JIRA for [~rxin]'s patch needed by the Shark project. https://github.com/amplab/hive/commit/17e1c3dd2f6d8eca767115dc46d5a880aed8c765 writeVLong should not use a static field due to concurrency concerns. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-2641) SkewJoin should report progress while writing skew keys to HDFS
[ https://issues.apache.org/jira/browse/HIVE-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-2641: Assignee: Namit Jain SkewJoin should report progress while writing skew keys to HDFS --- Key: HIVE-2641 URL: https://issues.apache.org/jira/browse/HIVE-2641 Project: Hive Issue Type: Improvement Reporter: Namit Jain Assignee: Namit Jain RowContainer.copyToDFSDirectory is used to write the skew keys to HDFS. But this can take a long time, and while it is happening, the MR framework does not see progress from the reducer. The code should do the copy in smaller unit and report progress to the MR framework -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3772) Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin)
[ https://issues.apache.org/jira/browse/HIVE-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510333#comment-13510333 ] Reynold Xin commented on HIVE-3772: --- Thanks for submitting this, Mikhail. Note that this was introduced in 0.9. In 0.7, this was not a problem ... Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin) - Key: HIVE-3772 URL: https://issues.apache.org/jira/browse/HIVE-3772 Project: Hive Issue Type: Bug Reporter: Mikhail Bautin Creating a JIRA for [~rxin]'s patch needed by the Shark project. https://github.com/amplab/hive/commit/17e1c3dd2f6d8eca767115dc46d5a880aed8c765 writeVLong should not use a static field due to concurrency concerns. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3771) HIVE-3750 broke TestParse
[ https://issues.apache.org/jira/browse/HIVE-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3771: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Committed. Thanks Kevin HIVE-3750 broke TestParse - Key: HIVE-3771 URL: https://issues.apache.org/jira/browse/HIVE-3771 Project: Hive Issue Type: Bug Components: Testing Infrastructure Affects Versions: 0.11 Reporter: Kevin Wilfong Assignee: Kevin Wilfong Attachments: HIVE-3771.1.patch.txt see title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3772) Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin)
[ https://issues.apache.org/jira/browse/HIVE-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-3772: -- Attachment: D7155.1.patch mbautin requested code review of [jira] [HIVE-3772] Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin). Reviewers: ashutoshc, njain, raghotham, JIRA Reynold Xin's patch needed by the Shark project. https://github.com/amplab/hive/commit/17e1c3dd2f6d8eca767115dc46d5a880aed8c765 (writeVLong should not use a static field due to concurrency concerns.) TEST PLAN Unit tests REVISION DETAIL https://reviews.facebook.net/D7155 AFFECTED FILES serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryUtils.java MANAGE HERALD DIFFERENTIAL RULES https://reviews.facebook.net/herald/view/differential/ WHY DID I GET THIS EMAIL? https://reviews.facebook.net/herald/transcript/16935/ To: ashutoshc, njain, raghotham, JIRA, mbautin Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin) - Key: HIVE-3772 URL: https://issues.apache.org/jira/browse/HIVE-3772 Project: Hive Issue Type: Bug Reporter: Mikhail Bautin Attachments: D7155.1.patch Creating a JIRA for [~rxin]'s patch needed by the Shark project. https://github.com/amplab/hive/commit/17e1c3dd2f6d8eca767115dc46d5a880aed8c765 writeVLong should not use a static field due to concurrency concerns. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3772) Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin)
[ https://issues.apache.org/jira/browse/HIVE-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Bautin updated HIVE-3772: - Attachment: HIVE-3772-2012-12-04.patch Attaching trunk patch. Fix a concurrency bug in LazyBinaryUtils due to a static field (patch by Reynold Xin) - Key: HIVE-3772 URL: https://issues.apache.org/jira/browse/HIVE-3772 Project: Hive Issue Type: Bug Reporter: Mikhail Bautin Attachments: D7155.1.patch, HIVE-3772-2012-12-04.patch Creating a JIRA for [~rxin]'s patch needed by the Shark project. https://github.com/amplab/hive/commit/17e1c3dd2f6d8eca767115dc46d5a880aed8c765 writeVLong should not use a static field due to concurrency concerns. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
