JIRA_hive-132.2.patch_FAILED_TO_APPLY_PATCH

Summary: This patch from JIRA hive-132.2.patch failed to apply to the apache Hive sources. 3 out of 4 hunks FAILED -- saving rejects to file ql/src/test/results/clientpositive/input3.q.out.rej 1 out of 1 hunk FAILED -- saving rejects to file ql/src/test/results/clientpositive/input2.q.out.rej

[jira] Commented: (HIVE-223) when using map-side aggregates - perform single map-reduce group-by

[ https://issues.apache.org/jira/browse/HIVE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671052#action_12671052 ] Joydeep Sen Sarma commented on HIVE-223: the parameters make a lot of sense. for #1

[jira] Created: (HIVE-277) Files created by redundant tasks that have been killed are taken into consideration

Files created by redundant tasks that have been killed are taken into consideration --- Key: HIVE-277 URL: https://issues.apache.org/jira/browse/HIVE-277 Project: Hadoop

[jira] Created: (HIVE-278) Add HiveHistory to Hive web interface

Add HiveHistory to Hive web interface - Key: HIVE-278 URL: https://issues.apache.org/jira/browse/HIVE-278 Project: Hadoop Hive Issue Type: New Feature Components: Logging, Web UI Affects

RE: *UNIT TEST FAILURE for apache HIVE* Hadoop.Version=0.17.1 based on SVN Rev# 741561.49

Folks.. Any ideas why this is still failing... Ashish -Original Message- From: Murli Varadachari [mailto:mvaradach...@facebook.com] Sent: Friday, February 06, 2009 6:05 AM To: hive-dev@hadoop.apache.org Subject: *UNIT TEST FAILURE for apache HIVE* Hadoop.Version=0.17.1 based on SVN

HiveQL and SQL 2003

Hello, I am curious if certain object and type definition features of SQL 2003 standard can be implemented as part of HiveQL. It makes sense because hadoop database was designed as a non-SQL parallel database where operations are written in Java classes. Syntax and semantics for types and

[jira] Created: (HIVE-279) Implement predicate push down for hive queries

Implement predicate push down for hive queries -- Key: HIVE-279 URL: https://issues.apache.org/jira/browse/HIVE-279 Project: Hadoop Hive Issue Type: New Feature Affects Versions: 0.2.0

[jira] Created: (HIVE-280) reserve keywords such as type, database, view etc for future use

reserve keywords such as type, database, view etc for future use Key: HIVE-280 URL: https://issues.apache.org/jira/browse/HIVE-280 Project: Hadoop Hive Issue Type: Bug

[jira] Created: (HIVE-281) Remove iscompressed parameter in the metastore

Remove iscompressed parameter in the metastore Key: HIVE-281 URL: https://issues.apache.org/jira/browse/HIVE-281 Project: Hadoop Hive Issue Type: Improvement Affects Versions: 0.2.0,

[jira] Commented: (HIVE-281) Remove iscompressed parameter in the metastore

[ https://issues.apache.org/jira/browse/HIVE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671392#action_12671392 ] Prasad Chakka commented on HIVE-281: you mean in the ql.metadata interface or in the