Build failed in Jenkins: Hive-trunk-h0.21 #809

[Apache Jenkins Server]

See 

Changes:

[nzhang] HIVE-2257. Enable TestHadoop20SAuthBridge (Carl Steinbach via Ning 
Zhang)

--
[...truncated 32837 lines...]
No ivy:settings found for the default reference 'ivy.instance'.  A default 
instance will be used
no settings file found, using default...
:: loading settings :: url = 
jar:file:/home/hudson/.ant/lib/ivy-2.0.0-rc2.jar!/org/apache/ivy/core/settings/ivysettings.xml

ivy-init-dirs:

ivy-download:
  [get] Getting: 
http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.1.0/ivy-2.1.0.jar
  [get] To: 

  [get] Not modified - so not downloaded

ivy-probe-antlib:

ivy-init-antlib:

ivy-init:

check-ivy:

create-dirs:

compile-ant-tasks:

create-dirs:

init:

compile:
 [echo] Compiling: anttasks
[javac] 
:40: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds

deploy-ant-tasks:

create-dirs:

init:

compile:
 [echo] Compiling: anttasks
[javac] 
:40: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds

jar:

init:

install-hadoopcore:

install-hadoopcore-default:

ivy-init-dirs:

ivy-download:
  [get] Getting: 
http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.1.0/ivy-2.1.0.jar
  [get] To: 

  [get] Not modified - so not downloaded

ivy-probe-antlib:

ivy-init-antlib:

ivy-init:

ivy-retrieve-hadoop-source:
:: loading settings :: file = 

[ivy:retrieve] :: resolving dependencies :: 
org.apache.hive#hive-hwi;0.8.0-SNAPSHOT
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  found hadoop#core;0.20.1 in hadoop-source
[ivy:retrieve] :: resolution report :: resolve 661ms :: artifacts dl 0ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  default |   1   |   0   |   0   |   0   ||   1   |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.hive#hive-hwi
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  0 artifacts copied, 1 already retrieved (0kB/1ms)

install-hadoopcore-internal:

setup:

war:

compile:
 [echo] Compiling: hwi
[javac] 
:71: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds

jar:
 [echo] Jar: hwi

make-pom:
 [echo]  Writing POM to 

No ivy:settings found for the default reference 'ivy.instance'.  A default 
instance will be used
no settings file found, using default...
:: loading settings :: url = 
jar:file:/home/hudson/.ant/lib/ivy-2.0.0-rc2.jar!/org/apache/ivy/core/settings/ivysettings.xml

ivy-init-dirs:

ivy-download:
  [get] Getting: 
http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.1.0/ivy-2.1.0.jar
  [get] To: 

  [get] Not modified - so not downloaded

ivy-probe-antlib:

ivy-init-antlib:

ivy-init:

check-ivy:

create-dirs:

compile-ant-tasks:

create-dirs:

init:

compile:
 [echo] Compiling: anttasks
[javac] 
:40: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds

deploy-ant-tasks:

create-dirs:

init:

compile:
 [echo] Compiling: anttasks
[javac] 
:40: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds

jar:

init:

setup:

compile:
 [echo] Compiling: hbase-handler
[javac] 
:299: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
 [copy] Warning: 

 does not exist.

jar:
 [echo] Jar: hbase-handler

make-pom:
 [echo]  Writing POM to 

No ivy:setting

[jira] [Commented] (HIVE-2257) Enable TestHadoop20SAuthBridge

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060306#comment-13060306
 ] 

Hudson commented on HIVE-2257:
--

Integrated in Hive-trunk-h0.21 #809 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/809/])
HIVE-2257. Enable TestHadoop20SAuthBridge (Carl Steinbach via Ning Zhang)

nzhang : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1143233
Files : 
* /hive/trunk/build.xml


> Enable TestHadoop20SAuthBridge
> --
>
> Key: HIVE-2257
> URL: https://issues.apache.org/jira/browse/HIVE-2257
> Project: Hive
>  Issue Type: Bug
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Fix For: 0.8.0
>
> Attachments: HIVE-2257-test-shims.1.patch.txt
>
>
> Looks like this test was accidentally disabled in HIVE-818.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2128) Automatic Indexing with multiple tables

[Syed S. Albiz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Syed S. Albiz updated HIVE-2128:


Attachment: HIVE-2128.2.patch

Hmm, you're right, we would need multiple blockfilter files in that case. I'm 
not sure if that is possible though in the framework we have, given that we 
choose one single index query to generate each time at each stage. In the case 
where we have multiple indexes involved at each stage, the index handler is 
responsible for combining index inputs into a single output file. For example, 
I have attached a case that seems like it might cause problems (both src and 
srcpart have indexes built and filters applied), however since the index 
queries are generated separately for separate table scans it seems like there 
is no collision between blockfilter files. Does this address the issue? It 
seems like there might still be a possibility of collision between table and 
blockfilter file, so I wonder if you had a different case in mind?

> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
>Assignee: Syed S. Albiz
> Attachments: HIVE-2128.1.patch, HIVE-2128.1.patch, HIVE-2128.2.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2171) Allow custom serdes to set field comments

[Jakob Homan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Homan updated HIVE-2171:
--

Status: Patch Available  (was: Open)

> Allow custom serdes to set field comments
> -
>
> Key: HIVE-2171
> URL: https://issues.apache.org/jira/browse/HIVE-2171
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Jakob Homan
>Assignee: Jakob Homan
> Attachments: HIVE-2171.patch
>
>
> Currently, while serde implementations can set a field's name, they can't set 
> its comment.  These are set in the metastore utils to {{(from 
> deserializer)}}.  For those serdes that can provide meaningful comments for a 
> field, they should be propagated to the table description.  These 
> serde-provided comments could be prepended to "(from deserializer)" if others 
> feel that's a meaningful distinction.  This change involves updating 
> {{StructField}} to support a (possibly null) comment field and then 
> propagating this change out to the myriad places {{StructField}} is thrown 
> around.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2260) ExecDriver::addInputPaths should pass the table properties to the record writer

[jirapos...@reviews.apache.org (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060222#comment-13060222
 ] 

jirapos...@reviews.apache.org commented on HIVE-2260:
-


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1014/
---

Review request for hive.


Summary
---

Currently when ExecDriver encounters a non-existent partition, it creates an 
empty file so that the query will be valid (and return 0 results). However, 
when it does this and calls getHiveRecordWriter(), it creates a new instance of 
Properties, rather than providing the Properties associated with the table.

This causes RecordWriters that pull information from the table through the 
Properties to fail (such as Haivvreo). The RecordWriter should be provided the 
table's Properties, as it is in all other cases where it's called.


This addresses bug HIVE-2260.
https://issues.apache.org/jira/browse/HIVE-2260


Diffs
-

  ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 4fba845 

Diff: https://reviews.apache.org/r/1014/diff


Testing
---


Thanks,

Jakob



> ExecDriver::addInputPaths should pass the table properties to the record 
> writer
> ---
>
> Key: HIVE-2260
> URL: https://issues.apache.org/jira/browse/HIVE-2260
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Jakob Homan
>Assignee: Jakob Homan
> Attachments: HIVE-2260.patch
>
>
> Currently when ExecDriver encounters a non-existent partition, it creates an 
> empty file so that the query will be valid (and return 0 results).  However, 
> when it does this and calls {{getHiveRecordWriter()}}, it creates a new 
> instance of Properties, rather than providing the Properties associated with 
> the table.
> This causes RecordWriters that pull information from the table through the 
> Properties to fail (such as [Haivvreo|http://bit.ly/iwEQzJ]).  The 
> RecordWriter should be provided the table's Properties, as it is in all other 
> cases where it's called.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Review Request: ExecDriver::addInputPaths should pass the table properties to the record writer

[Jakob Homan]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1014/
---

Review request for hive.


Summary
---

Currently when ExecDriver encounters a non-existent partition, it creates an 
empty file so that the query will be valid (and return 0 results). However, 
when it does this and calls getHiveRecordWriter(), it creates a new instance of 
Properties, rather than providing the Properties associated with the table.

This causes RecordWriters that pull information from the table through the 
Properties to fail (such as Haivvreo). The RecordWriter should be provided the 
table's Properties, as it is in all other cases where it's called.


This addresses bug HIVE-2260.
https://issues.apache.org/jira/browse/HIVE-2260


Diffs
-

  ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 4fba845 

Diff: https://reviews.apache.org/r/1014/diff


Testing
---


Thanks,

Jakob

[jira] [Commented] (HIVE-2171) Allow custom serdes to set field comments

[Jakob Homan (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060219#comment-13060219
 ] 

Jakob Homan commented on HIVE-2171:
---

bq. hive already stores each column's comment in StorageDescriptor. Can we get 
the comments from there instead of putting it to StructField?
Hive stores column information for native serdes (see 
[SerDeUtils.java:99|https://github.com/apache/hive/blob/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java#L1889]).
  For non-native serdes, it queries the serde's object inspector, which is what 
this patch is dealing with.


> Allow custom serdes to set field comments
> -
>
> Key: HIVE-2171
> URL: https://issues.apache.org/jira/browse/HIVE-2171
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Jakob Homan
>Assignee: Jakob Homan
> Attachments: HIVE-2171.patch
>
>
> Currently, while serde implementations can set a field's name, they can't set 
> its comment.  These are set in the metastore utils to {{(from 
> deserializer)}}.  For those serdes that can provide meaningful comments for a 
> field, they should be propagated to the table description.  These 
> serde-provided comments could be prepended to "(from deserializer)" if others 
> feel that's a meaningful distinction.  This change involves updating 
> {{StructField}} to support a (possibly null) comment field and then 
> propagating this change out to the myriad places {{StructField}} is thrown 
> around.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2128) Automatic Indexing with multiple tables

[John Sichi (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060217#comment-13060217
 ] 

John Sichi commented on HIVE-2128:
--

I don't think this approach works...what if both tables in the query have an 
applicable filter?

In that case, don't we need a separate blockfilter file per table alias?


> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
>Assignee: Syed S. Albiz
> Attachments: HIVE-2128.1.patch, HIVE-2128.1.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2257) Enable TestHadoop20SAuthBridge

[Ning Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ning Zhang updated HIVE-2257:
-

   Resolution: Fixed
Fix Version/s: 0.8.0
 Hadoop Flags: [Reviewed]
   Status: Resolved  (was: Patch Available)

Committed. Thanks Carl!

> Enable TestHadoop20SAuthBridge
> --
>
> Key: HIVE-2257
> URL: https://issues.apache.org/jira/browse/HIVE-2257
> Project: Hive
>  Issue Type: Bug
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Fix For: 0.8.0
>
> Attachments: HIVE-2257-test-shims.1.patch.txt
>
>
> Looks like this test was accidentally disabled in HIVE-818.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2128) Automatic Indexing with multiple tables

[Syed S. Albiz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Syed S. Albiz updated HIVE-2128:


Attachment: HIVE-2128.1.patch

updated to include testcase

> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
>Assignee: Syed S. Albiz
> Attachments: HIVE-2128.1.patch, HIVE-2128.1.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2128) Automatic Indexing with multiple tables

[jirapos...@reviews.apache.org (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060207#comment-13060207
 ] 

jirapos...@reviews.apache.org commented on HIVE-2128:
-


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1010/
---

(Updated 2011-07-06 00:03:20.513755)


Review request for hive and John Sichi.


Changes
---

updated patch to include testcase


Summary
---

Grab the indexed tables during optimized query generation, grab the associated 
path URIs, and keep those around in the Configuration object. When the job is 
passed to ExecDriver, this data is extracted and used in HiveIndexedInputFormat 
to decide whether to use the index file or delegate to the parent 
(HiveInputFormat) class. Not sure if this is robust. 


This addresses bug HIVE-2128.
https://issues.apache.org/jira/browse/HIVE-2128


Diffs (updated)
-

  ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 090ecfc 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexQueryContext.java 
617723e 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexedInputFormat.java 
f1ee95d 
  ql/src/java/org/apache/hadoop/hive/ql/index/bitmap/BitmapIndexHandler.java 
61bbbf5 
  ql/src/java/org/apache/hadoop/hive/ql/index/compact/CompactIndexHandler.java 
7c91946 
  
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java
 dbc489f 
  ql/src/java/org/apache/hadoop/hive/ql/plan/MapredWork.java a03a9a6 
  ql/src/test/queries/clientpositive/index_auto_mult_tables.q PRE-CREATION 
  ql/src/test/results/clientpositive/index_auto_mult_tables.q.out PRE-CREATION 

Diff: https://reviews.apache.org/r/1010/diff


Testing
---

added new testcase index_auto_mult_tables.q


Thanks,

Syed



> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
>Assignee: Syed S. Albiz
> Attachments: HIVE-2128.1.patch, HIVE-2128.1.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Review Request: HIVE-2128: Automatic Indexing with multiple tables

[Syed Albiz]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1010/
---

(Updated 2011-07-06 00:03:20.513755)


Review request for hive and John Sichi.


Changes
---

updated patch to include testcase


Summary
---

Grab the indexed tables during optimized query generation, grab the associated 
path URIs, and keep those around in the Configuration object. When the job is 
passed to ExecDriver, this data is extracted and used in HiveIndexedInputFormat 
to decide whether to use the index file or delegate to the parent 
(HiveInputFormat) class. Not sure if this is robust. 


This addresses bug HIVE-2128.
https://issues.apache.org/jira/browse/HIVE-2128


Diffs (updated)
-

  ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 090ecfc 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexQueryContext.java 
617723e 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexedInputFormat.java 
f1ee95d 
  ql/src/java/org/apache/hadoop/hive/ql/index/bitmap/BitmapIndexHandler.java 
61bbbf5 
  ql/src/java/org/apache/hadoop/hive/ql/index/compact/CompactIndexHandler.java 
7c91946 
  
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java
 dbc489f 
  ql/src/java/org/apache/hadoop/hive/ql/plan/MapredWork.java a03a9a6 
  ql/src/test/queries/clientpositive/index_auto_mult_tables.q PRE-CREATION 
  ql/src/test/results/clientpositive/index_auto_mult_tables.q.out PRE-CREATION 

Diff: https://reviews.apache.org/r/1010/diff


Testing
---

added new testcase index_auto_mult_tables.q


Thanks,

Syed

[jira] [Commented] (HIVE-2128) Automatic Indexing with multiple tables

[John Sichi (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060199#comment-13060199
 ] 

John Sichi commented on HIVE-2128:
--

I don't see the new testcase in either the patch or the reviewboard entry?


> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
>Assignee: Syed S. Albiz
> Attachments: HIVE-2128.1.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2260) ExecDriver::addInputPaths should pass the table properties to the record writer

[Jakob Homan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Homan updated HIVE-2260:
--

Attachment: HIVE-2260.patch

Patch takes the Properties from the table/partition and passes it to the 
RecordWriter.  This fixes the issue Haivvreo runs into.  

The patch doesn't include a unit test, since this is pretty far into the guts 
of ExecDriver.  I'd be happy to write one up and introduce Mockito, which I 
think is the only reasonable way of getting to this code path, if others think 
it's worthwhile.

> ExecDriver::addInputPaths should pass the table properties to the record 
> writer
> ---
>
> Key: HIVE-2260
> URL: https://issues.apache.org/jira/browse/HIVE-2260
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Jakob Homan
>Assignee: Jakob Homan
> Attachments: HIVE-2260.patch
>
>
> Currently when ExecDriver encounters a non-existent partition, it creates an 
> empty file so that the query will be valid (and return 0 results).  However, 
> when it does this and calls {{getHiveRecordWriter()}}, it creates a new 
> instance of Properties, rather than providing the Properties associated with 
> the table.
> This causes RecordWriters that pull information from the table through the 
> Properties to fail (such as [Haivvreo|http://bit.ly/iwEQzJ]).  The 
> RecordWriter should be provided the table's Properties, as it is in all other 
> cases where it's called.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2260) ExecDriver::addInputPaths should pass the table properties to the record writer

[Jakob Homan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Homan updated HIVE-2260:
--

Status: Patch Available  (was: Open)

> ExecDriver::addInputPaths should pass the table properties to the record 
> writer
> ---
>
> Key: HIVE-2260
> URL: https://issues.apache.org/jira/browse/HIVE-2260
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Jakob Homan
>Assignee: Jakob Homan
> Attachments: HIVE-2260.patch
>
>
> Currently when ExecDriver encounters a non-existent partition, it creates an 
> empty file so that the query will be valid (and return 0 results).  However, 
> when it does this and calls {{getHiveRecordWriter()}}, it creates a new 
> instance of Properties, rather than providing the Properties associated with 
> the table.
> This causes RecordWriters that pull information from the table through the 
> Properties to fail (such as [Haivvreo|http://bit.ly/iwEQzJ]).  The 
> RecordWriter should be provided the table's Properties, as it is in all other 
> cases where it's called.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2252) Display a sample of partitions created when Fatal Error occurred due to too many partitioned created

[jirapos...@reviews.apache.org (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060140#comment-13060140
 ] 

jirapos...@reviews.apache.org commented on HIVE-2252:
-


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1013/
---

Review request for hive.


Summary
---

In dynamic partition inserts, if a mapper created too many partitions, a fatal 
error is raised and the job got killed. Sometimes the error is caused by data 
error and it will be helpful for users to debug if we display a sample of 
dynamic partitions generated.


This addresses bug HIVE-2252.
https://issues.apache.org/jira/browse/HIVE-2252


Diffs
-

  trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/FileSinkOperator.java 
1141747 

Diff: https://reviews.apache.org/r/1013/diff


Testing
---

passed all unit tests. 


Thanks,

Ning



> Display a sample of partitions created when Fatal Error occurred due to too 
> many partitioned created
> 
>
> Key: HIVE-2252
> URL: https://issues.apache.org/jira/browse/HIVE-2252
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ning Zhang
>Assignee: Ning Zhang
> Attachments: HIVE-2252.patch
>
>
> In dynamic partition inserts, if a mapper created too many partitions, a 
> fatal error is raised and the job got killed. Sometimes the error is caused 
> by data error and it will be helpful for users to debug if we display a 
> sample of dynamic partitions generated. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Review Request: HIVE-2252. Display a sample of partitions created when Fatal Error occurred due to too many partitioned created

[Ning Zhang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1013/
---

Review request for hive.


Summary
---

In dynamic partition inserts, if a mapper created too many partitions, a fatal 
error is raised and the job got killed. Sometimes the error is caused by data 
error and it will be helpful for users to debug if we display a sample of 
dynamic partitions generated.


This addresses bug HIVE-2252.
https://issues.apache.org/jira/browse/HIVE-2252


Diffs
-

  trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/FileSinkOperator.java 
1141747 

Diff: https://reviews.apache.org/r/1013/diff


Testing
---

passed all unit tests. 


Thanks,

Ning

[jira] [Updated] (HIVE-2252) Display a sample of partitions created when Fatal Error occurred due to too many partitioned created

[Ning Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ning Zhang updated HIVE-2252:
-

Attachment: HIVE-2252.patch

> Display a sample of partitions created when Fatal Error occurred due to too 
> many partitioned created
> 
>
> Key: HIVE-2252
> URL: https://issues.apache.org/jira/browse/HIVE-2252
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ning Zhang
>Assignee: Ning Zhang
> Attachments: HIVE-2252.patch
>
>
> In dynamic partition inserts, if a mapper created too many partitions, a 
> fatal error is raised and the job got killed. Sometimes the error is caused 
> by data error and it will be helpful for users to debug if we display a 
> sample of dynamic partitions generated. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HIVE-2163) SquirrelSQL 3.2.1 doesn't work with Hive 0.7.0

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach resolved HIVE-2163.
--

   Resolution: Duplicate
Fix Version/s: 0.7.1

Verified that this was fixed in HIVE-2054.

> SquirrelSQL 3.2.1 doesn't work with Hive 0.7.0
> --
>
> Key: HIVE-2163
> URL: https://issues.apache.org/jira/browse/HIVE-2163
> Project: Hive
>  Issue Type: Bug
>  Components: JDBC
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Fix For: 0.7.1
>
>
> I tried using SquirrelSQL 3.2.1 with Hive 0.7.0 following the directions 
> located here: http://wiki.apache.org/hadoop/Hive/HiveJDBCInterface
> I registered the Hive JDBC driver with SquirrelSQL, and then get the 
> following exception when I try to connect to the Hive Server process:
> {noformat}
> java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException: 
> java.lang.RuntimeException: java.io.IOException: failure to login 
> at 
> org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:226) 
> at org.apache.hadoop.hive.jdbc.HiveConnection.(HiveConnection.java:72) 
> at org.apache.hadoop.hive.jdbc.HiveDriver.connect(HiveDriver.java:110) 
> at 
> net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133)
>  
> at 
> net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.execute(OpenConnectionCommand.java:97)
>  
> at 
> net.sourceforge.squirrel_sql.client.mainframe.action.ConnectToAliasCommand$SheetHandler.run(ConnectToAliasCommand.java:281)
> at 
> net.sourceforge.squirrel_sql.client.mainframe.action.ConnectToAliasCommand$SheetHandler.performOK(ConnectToAliasCommand.java:238)
> at 
> net.sourceforge.squirrel_sql.client.gui.db.ConnectionInternalFrame.connect(ConnectionInternalFrame.java:311)
>  
> at 
> net.sourceforge.squirrel_sql.client.gui.db.ConnectionInternalFrame.access$300(ConnectionInternalFrame.java:56)
>  
> at 
> net.sourceforge.squirrel_sql.client.gui.db.ConnectionInternalFrame$MyOkClosePanelListener.okPressed(ConnectionInternalFrame.java:461)
> at 
> net.sourceforge.squirrel_sql.client.gui.OkClosePanel.fireButtonPressed(OkClosePanel.java:148)
>  
> at 
> net.sourceforge.squirrel_sql.client.gui.OkClosePanel.access$100(OkClosePanel.java:33)
>  
> at 
> net.sourceforge.squirrel_sql.client.gui.OkClosePanel$1.actionPerformed(OkClosePanel.java:174)
>  
> at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2028) 
> at 
> javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2351) 
> at 
> javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
>  
> at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242) 
> at 
> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
>  
> at java.awt.Component.processMouseEvent(Component.java:6374) 
> at javax.swing.JComponent.processMouseEvent(JComponent.java:3267) 
> at java.awt.Component.processEvent(Component.java:6139) 
> at java.awt.Container.processEvent(Container.java:2085) 
> at java.awt.Component.dispatchEventImpl(Component.java:4736) 
> at java.awt.Container.dispatchEventImpl(Container.java:2143) 
> at java.awt.Component.dispatchEvent(Component.java:4566) 
> at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4621) 
> at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4282) 
> at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4212) 
> at java.awt.Container.dispatchEventImpl(Container.java:2129) 
> at java.awt.Window.dispatchEventImpl(Window.java:2478) 
> at java.awt.Component.dispatchEvent(Component.java:4566) 
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:680) 
> at java.awt.EventQueue.access$000(EventQueue.java:86) 
> at java.awt.EventQueue$1.run(EventQueue.java:639) 
> at java.awt.EventQueue$1.run(EventQueue.java:637) 
> at java.security.AccessController.doPrivileged(Native Method) 
> at 
> java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
>  
> at 
> java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
>  
> at java.awt.EventQueue$2.run(EventQueue.java:653) 
> at java.awt.EventQueue$2.run(EventQueue.java:651) 
> at java.security.AccessController.doPrivileged(Native Method) 
> at 
> java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
>  
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:650) 
> at net.sourceforge.squirrel_sql.client.Main$1.dispatchEvent(Main.java:93) 
> at 
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
>  
> at 
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
>  
> at 
> java.awt.Ev

[jira] [Updated] (HIVE-2258) Honor -S flag during hadoop rmr command

[Vaibhav Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Aggarwal updated HIVE-2258:
---

Status: Patch Available  (was: Open)

> Honor -S flag during hadoop rmr command
> ---
>
> Key: HIVE-2258
> URL: https://issues.apache.org/jira/browse/HIVE-2258
> Project: Hive
>  Issue Type: Bug
>Reporter: Vaibhav Aggarwal
>Assignee: Vaibhav Aggarwal
> Attachments: HIVE-2258.patch
>
>
> Currently even if -S flag is specified, the output of hadoop -rmr command is 
> printed to the screen.
> The reason is that the command writes output to screen instead of log file.
> I have fixed the problem by temporarily redirecting the output for that 
> command.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2259) Skip comments in hive script

[Vaibhav Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Aggarwal updated HIVE-2259:
---

Status: Patch Available  (was: Open)

> Skip comments in hive script
> 
>
> Key: HIVE-2259
> URL: https://issues.apache.org/jira/browse/HIVE-2259
> Project: Hive
>  Issue Type: Bug
>Reporter: Vaibhav Aggarwal
>Assignee: Vaibhav Aggarwal
> Attachments: HIVE-2259.patch
>
>
> If you specify something like:
> -- This is a comment
> add jar jar_path;
> select * from my_table;
> This fails.
> I have created a fix to skip the commented lines.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2259) Skip comments in hive script

[Vaibhav Aggarwal (JIRA)]

Skip comments in hive script


 Key: HIVE-2259
 URL: https://issues.apache.org/jira/browse/HIVE-2259
 Project: Hive
  Issue Type: Bug
Reporter: Vaibhav Aggarwal
Assignee: Vaibhav Aggarwal
 Attachments: HIVE-2259.patch

If you specify something like:

-- This is a comment
add jar jar_path;
select * from my_table;

This fails.

I have created a fix to skip the commented lines.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2259) Skip comments in hive script

[Vaibhav Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Aggarwal updated HIVE-2259:
---

Attachment: HIVE-2259.patch

> Skip comments in hive script
> 
>
> Key: HIVE-2259
> URL: https://issues.apache.org/jira/browse/HIVE-2259
> Project: Hive
>  Issue Type: Bug
>Reporter: Vaibhav Aggarwal
>Assignee: Vaibhav Aggarwal
> Attachments: HIVE-2259.patch
>
>
> If you specify something like:
> -- This is a comment
> add jar jar_path;
> select * from my_table;
> This fails.
> I have created a fix to skip the commented lines.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2256) Better error message in CLI on invalid column name

[Sohan Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sohan Jain updated HIVE-2256:
-

Attachment: HIVE-2256.2.patch

-Updated the outputs for unit tests.
-Fixed the error message to include the line number and position in the query 
of the invalid column.

> Better error message in CLI on invalid column name
> --
>
> Key: HIVE-2256
> URL: https://issues.apache.org/jira/browse/HIVE-2256
> Project: Hive
>  Issue Type: Improvement
>  Components: CLI, Query Processor
>Reporter: Sohan Jain
>Assignee: Sohan Jain
> Attachments: HIVE-2256.1.patch, HIVE-2256.2.patch
>
>
> In the CLI, if a user inputs an incorrect column name, we currently just 
> print the bad column name in the query.  Typically, the user needs to 
> "describe" the table to figure out the correct column.
> This patch prints out a list of valid column and partition names in the table 
> when a user inputs an incorrect column name.
> e.g., 
> {{Error in semantic analysis: Invalid table alias or column reference 
> 'col_does_not_exist' (possible column names are: col1, col2)}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2258) Honor -S flag during hadoop rmr command

[Vaibhav Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Aggarwal updated HIVE-2258:
---

Attachment: HIVE-2258.patch

> Honor -S flag during hadoop rmr command
> ---
>
> Key: HIVE-2258
> URL: https://issues.apache.org/jira/browse/HIVE-2258
> Project: Hive
>  Issue Type: Bug
>Reporter: Vaibhav Aggarwal
>Assignee: Vaibhav Aggarwal
> Attachments: HIVE-2258.patch
>
>
> Currently even if -S flag is specified, the output of hadoop -rmr command is 
> printed to the screen.
> The reason is that the command writes output to screen instead of log file.
> I have fixed the problem by temporarily redirecting the output for that 
> command.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2239) Up the commons-codec version from 1.3 to 1.4

[John Sichi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Sichi updated HIVE-2239:
-

Status: Patch Available  (was: Open)

> Up the commons-codec version from 1.3 to 1.4
> 
>
> Key: HIVE-2239
> URL: https://issues.apache.org/jira/browse/HIVE-2239
> Project: Hive
>  Issue Type: Task
>  Components: Build Infrastructure, Contrib
>Affects Versions: 0.7.0, 0.6.0, 0.8.0
>Reporter: Ashutosh Chauhan
>Assignee: Ashutosh Chauhan
> Attachments: HIVE-2239.2.patch, hive-2239.patch
>
>
> Hadoop upgraded from 1.3 to 1.4. Since, hive is launched from hadoop scripts, 
> it gets 1.4 from there and then it includes 1.3 itself. Having two different 
> versions of same jar causes unwanted grief.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2258) Honor -S flag during hadoop rmr command

[Vaibhav Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Aggarwal updated HIVE-2258:
---

Description: 
Currently even if -S flag is specified, the output of hadoop -rmr command is 
printed to the screen.
The reason is that the command writes output to screen instead of log file.

I have fixed the problem by temporarily redirecting the output for that command.
Summary: Honor -S flag during hadoop rmr command  (was: Honor -S silent 
floag during hadoop rmr command)

> Honor -S flag during hadoop rmr command
> ---
>
> Key: HIVE-2258
> URL: https://issues.apache.org/jira/browse/HIVE-2258
> Project: Hive
>  Issue Type: Bug
>Reporter: Vaibhav Aggarwal
>Assignee: Vaibhav Aggarwal
>
> Currently even if -S flag is specified, the output of hadoop -rmr command is 
> printed to the screen.
> The reason is that the command writes output to screen instead of log file.
> I have fixed the problem by temporarily redirecting the output for that 
> command.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2239) Up the commons-codec version from 1.3 to 1.4

[John Sichi (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060131#comment-13060131
 ] 

John Sichi commented on HIVE-2239:
--

OK, will commit when tests pass.

> Up the commons-codec version from 1.3 to 1.4
> 
>
> Key: HIVE-2239
> URL: https://issues.apache.org/jira/browse/HIVE-2239
> Project: Hive
>  Issue Type: Task
>  Components: Build Infrastructure, Contrib
>Affects Versions: 0.6.0, 0.7.0, 0.8.0
>Reporter: Ashutosh Chauhan
>Assignee: Ashutosh Chauhan
> Attachments: HIVE-2239.2.patch, hive-2239.patch
>
>
> Hadoop upgraded from 1.3 to 1.4. Since, hive is launched from hadoop scripts, 
> it gets 1.4 from there and then it includes 1.3 itself. Having two different 
> versions of same jar causes unwanted grief.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2258) Honor -S silent floag during hadoop rmr command

[Vaibhav Aggarwal (JIRA)]

Honor -S silent floag during hadoop rmr command
---

 Key: HIVE-2258
 URL: https://issues.apache.org/jira/browse/HIVE-2258
 Project: Hive
  Issue Type: Bug
Reporter: Vaibhav Aggarwal
Assignee: Vaibhav Aggarwal




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HIVE-2255) uncomment test-shims in build.xml

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach resolved HIVE-2255.
--

Resolution: Duplicate

Duplicate of HIVE-2257 (whoops)

> uncomment test-shims in build.xml
> -
>
> Key: HIVE-2255
> URL: https://issues.apache.org/jira/browse/HIVE-2255
> Project: Hive
>  Issue Type: Bug
>Reporter: John Sichi
>Assignee: Ning Zhang
>
> I saw this code in build.xml:
> {noformat}
>   
>   
> {noformat}
> I used svn blame to trace it back to HIVE-818.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2239) Up the commons-codec version from 1.3 to 1.4

[Ashutosh Chauhan (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060126#comment-13060126
 ] 

Ashutosh Chauhan commented on HIVE-2239:


Yup, your approach is cleaner then mine. 
+1

> Up the commons-codec version from 1.3 to 1.4
> 
>
> Key: HIVE-2239
> URL: https://issues.apache.org/jira/browse/HIVE-2239
> Project: Hive
>  Issue Type: Task
>  Components: Build Infrastructure, Contrib
>Affects Versions: 0.6.0, 0.7.0, 0.8.0
>Reporter: Ashutosh Chauhan
>Assignee: Ashutosh Chauhan
> Attachments: HIVE-2239.2.patch, hive-2239.patch
>
>
> Hadoop upgraded from 1.3 to 1.4. Since, hive is launched from hadoop scripts, 
> it gets 1.4 from there and then it includes 1.3 itself. Having two different 
> versions of same jar causes unwanted grief.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2257) Enable TestHadoop20SAuthBridge

[Ning Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060128#comment-13060128
 ] 

Ning Zhang commented on HIVE-2257:
--

oops, my fault. I remembered there was some issues in that test, but forgot to 
change it back. 

+1 on this. 

> Enable TestHadoop20SAuthBridge
> --
>
> Key: HIVE-2257
> URL: https://issues.apache.org/jira/browse/HIVE-2257
> Project: Hive
>  Issue Type: Bug
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2257-test-shims.1.patch.txt
>
>
> Looks like this test was accidentally disabled in HIVE-818.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2257) Enable TestHadoop20SAuthBridge

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach updated HIVE-2257:
-

Attachment: HIVE-2257-test-shims.1.patch.txt

> Enable TestHadoop20SAuthBridge
> --
>
> Key: HIVE-2257
> URL: https://issues.apache.org/jira/browse/HIVE-2257
> Project: Hive
>  Issue Type: Bug
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2257-test-shims.1.patch.txt
>
>
> Looks like this test was accidentally disabled in HIVE-818.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2257) Enable TestHadoop20SAuthBridge

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach updated HIVE-2257:
-

Status: Patch Available  (was: Open)

TestHadoop20SAuthBridge passes with this patch in place. Currently running full 
regressions tests.

> Enable TestHadoop20SAuthBridge
> --
>
> Key: HIVE-2257
> URL: https://issues.apache.org/jira/browse/HIVE-2257
> Project: Hive
>  Issue Type: Bug
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2257-test-shims.1.patch.txt
>
>
> Looks like this test was accidentally disabled in HIVE-818.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2257) Enable TestHadoop20SAuthBridge

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach updated HIVE-2257:
-

Description: Looks like this test was accidentally disabled in HIVE-818.
   Assignee: Carl Steinbach
Summary: Enable TestHadoop20SAuthBridge  (was: Enable TestHadoopT)

> Enable TestHadoop20SAuthBridge
> --
>
> Key: HIVE-2257
> URL: https://issues.apache.org/jira/browse/HIVE-2257
> Project: Hive
>  Issue Type: Bug
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
>
> Looks like this test was accidentally disabled in HIVE-818.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2257) Enable TestHadoopT

[Carl Steinbach (JIRA)]

Enable TestHadoopT
--

 Key: HIVE-2257
 URL: https://issues.apache.org/jira/browse/HIVE-2257
 Project: Hive
  Issue Type: Bug
Reporter: Carl Steinbach




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2245) Make CombineHiveInputFormat the default hive.input.format

[Ning Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060115#comment-13060115
 ] 

Ning Zhang commented on HIVE-2245:
--

Interesting. I'm trying index_bitmap.q on my dev box and it worked. I used to 
run all unit tests on the test machine I used and everything was fine then. I 
guess there's something wrong with that box recently. I'll run the whole test 
on my dev box then. 

> Make CombineHiveInputFormat the default hive.input.format
> -
>
> Key: HIVE-2245
> URL: https://issues.apache.org/jira/browse/HIVE-2245
> Project: Hive
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2245.1.patch.txt
>
>
> We should use CombineHiveInputFormat as the default Hive input format.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to normal : Hive-trunk-h0.21 #808

[Apache Jenkins Server]

See 

[jira] [Commented] (HIVE-1587) Files on /tmp/hive-{username}/hive_{some timestamp}/ which are leftovers from old jobs which never are never removed

[Alex Rovner (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060097#comment-13060097
 ] 

Alex Rovner commented on HIVE-1587:
---

Any progress on this issue? I have this issue as well and it's causing quite a 
bit of space waist on our cluster.

> Files on /tmp/hive-{username}/hive_{some timestamp}/ which are leftovers from 
> old jobs which never are never removed
> 
>
> Key: HIVE-1587
> URL: https://issues.apache.org/jira/browse/HIVE-1587
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Affects Versions: 0.7.0
>Reporter: Bennie Schut
>
> I seem to have a lot of files on /tmp/hive-{username}/hive_{some timestamp}/ 
> which are leftovers from old jobs which never are never removed.
> These jobs ran without any problems.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HIVE-2128) Automatic Indexing with multiple tables

[Syed S. Albiz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Syed S. Albiz reassigned HIVE-2128:
---

Assignee: Syed S. Albiz

> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
>Assignee: Syed S. Albiz
> Attachments: HIVE-2128.1.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HIVE-2256) Better error message in CLI on invalid column name

[Sohan Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sohan Jain reassigned HIVE-2256:


Assignee: Sohan Jain

> Better error message in CLI on invalid column name
> --
>
> Key: HIVE-2256
> URL: https://issues.apache.org/jira/browse/HIVE-2256
> Project: Hive
>  Issue Type: Improvement
>  Components: CLI, Query Processor
>Reporter: Sohan Jain
>Assignee: Sohan Jain
> Attachments: HIVE-2256.1.patch
>
>
> In the CLI, if a user inputs an incorrect column name, we currently just 
> print the bad column name in the query.  Typically, the user needs to 
> "describe" the table to figure out the correct column.
> This patch prints out a list of valid column and partition names in the table 
> when a user inputs an incorrect column name.
> e.g., 
> {{Error in semantic analysis: Invalid table alias or column reference 
> 'col_does_not_exist' (possible column names are: col1, col2)}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2256) Better error message in CLI on invalid column name

[Sohan Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sohan Jain updated HIVE-2256:
-

Attachment: HIVE-2256.1.patch

The patch will probably need to edit test cases as well to account for the new 
error messages.

> Better error message in CLI on invalid column name
> --
>
> Key: HIVE-2256
> URL: https://issues.apache.org/jira/browse/HIVE-2256
> Project: Hive
>  Issue Type: Improvement
>  Components: CLI, Query Processor
>Reporter: Sohan Jain
> Attachments: HIVE-2256.1.patch
>
>
> In the CLI, if a user inputs an incorrect column name, we currently just 
> print the bad column name in the query.  Typically, the user needs to 
> "describe" the table to figure out the correct column.
> This patch prints out a list of valid column and partition names in the table 
> when a user inputs an incorrect column name.
> e.g., 
> {{Error in semantic analysis: Invalid table alias or column reference 
> 'col_does_not_exist' (possible column names are: col1, col2)}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2256) Better error message in CLI on invalid column name

[Sohan Jain (JIRA)]

Better error message in CLI on invalid column name
--

 Key: HIVE-2256
 URL: https://issues.apache.org/jira/browse/HIVE-2256
 Project: Hive
  Issue Type: Improvement
  Components: CLI, Query Processor
Reporter: Sohan Jain


In the CLI, if a user inputs an incorrect column name, we currently just print 
the bad column name in the query.  Typically, the user needs to "describe" the 
table to figure out the correct column.

This patch prints out a list of valid column and partition names in the table 
when a user inputs an incorrect column name.

e.g., 
{{Error in semantic analysis: Invalid table alias or column reference 
'col_does_not_exist' (possible column names are: col1, col2)}}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2128) Automatic Indexing with multiple tables

[jirapos...@reviews.apache.org (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060075#comment-13060075
 ] 

jirapos...@reviews.apache.org commented on HIVE-2128:
-


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1010/
---

Review request for hive and John Sichi.


Summary
---

Grab the indexed tables during optimized query generation, grab the associated 
path URIs, and keep those around in the Configuration object. When the job is 
passed to ExecDriver, this data is extracted and used in HiveIndexedInputFormat 
to decide whether to use the index file or delegate to the parent 
(HiveInputFormat) class. Not sure if this is robust. 


This addresses bug HIVE-2128.
https://issues.apache.org/jira/browse/HIVE-2128


Diffs
-

  ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 090ecfc 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexQueryContext.java 
617723e 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexedInputFormat.java 
f1ee95d 
  ql/src/java/org/apache/hadoop/hive/ql/index/bitmap/BitmapIndexHandler.java 
61bbbf5 
  ql/src/java/org/apache/hadoop/hive/ql/index/compact/CompactIndexHandler.java 
7c91946 
  
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java
 dbc489f 
  ql/src/java/org/apache/hadoop/hive/ql/plan/MapredWork.java a03a9a6 

Diff: https://reviews.apache.org/r/1010/diff


Testing
---

added new testcase index_auto_mult_tables.q


Thanks,

Syed



> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
> Attachments: HIVE-2128.1.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Review Request: HIVE-2128: Automatic Indexing with multiple tables

[Syed Albiz]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1010/
---

Review request for hive and John Sichi.


Summary
---

Grab the indexed tables during optimized query generation, grab the associated 
path URIs, and keep those around in the Configuration object. When the job is 
passed to ExecDriver, this data is extracted and used in HiveIndexedInputFormat 
to decide whether to use the index file or delegate to the parent 
(HiveInputFormat) class. Not sure if this is robust. 


This addresses bug HIVE-2128.
https://issues.apache.org/jira/browse/HIVE-2128


Diffs
-

  ql/src/java/org/apache/hadoop/hive/ql/exec/ExecDriver.java 090ecfc 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexQueryContext.java 
617723e 
  ql/src/java/org/apache/hadoop/hive/ql/index/HiveIndexedInputFormat.java 
f1ee95d 
  ql/src/java/org/apache/hadoop/hive/ql/index/bitmap/BitmapIndexHandler.java 
61bbbf5 
  ql/src/java/org/apache/hadoop/hive/ql/index/compact/CompactIndexHandler.java 
7c91946 
  
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java
 dbc489f 
  ql/src/java/org/apache/hadoop/hive/ql/plan/MapredWork.java a03a9a6 

Diff: https://reviews.apache.org/r/1010/diff


Testing
---

added new testcase index_auto_mult_tables.q


Thanks,

Syed

[jira] [Commented] (HIVE-2245) Make CombineHiveInputFormat the default hive.input.format

[John Sichi (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060070#comment-13060070
 ] 

John Sichi commented on HIVE-2245:
--

Ning, in case you are hitting the problem Paul was tracking down with ls, can 
you run his test script on your dev box to test it?  My dev box was affected, 
so I found another one which worked.


> Make CombineHiveInputFormat the default hive.input.format
> -
>
> Key: HIVE-2245
> URL: https://issues.apache.org/jira/browse/HIVE-2245
> Project: Hive
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2245.1.patch.txt
>
>
> We should use CombineHiveInputFormat as the default Hive input format.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HIVE-2196) Ensure HiveConf includes all properties defined in hive-default.xml

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach reassigned HIVE-2196:


Assignee: Chinna Rao Lalam  (was: Carl Steinbach)

> Ensure HiveConf includes all properties defined in hive-default.xml
> ---
>
> Key: HIVE-2196
> URL: https://issues.apache.org/jira/browse/HIVE-2196
> Project: Hive
>  Issue Type: Bug
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Chinna Rao Lalam
> Attachments: HIVE-2196.patch
>
>
> There are a bunch of properties that are defined in hive-default.xml but not 
> in HiveConf.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2128) Automatic Indexing with multiple tables

[Syed S. Albiz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Syed S. Albiz updated HIVE-2128:


Attachment: HIVE-2128.1.patch

> Automatic Indexing with multiple tables
> ---
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
>  Issue Type: Improvement
>  Components: Indexing
>Affects Versions: 0.8.0
>Reporter: Russell Melick
> Attachments: HIVE-2128.1.patch
>
>
> Make automatic indexing work with jobs which access multiple tables.  We'll 
> probably need to modify the way that the index input format works in order to 
> associate index formats/files with specific tables.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HIVE-2005) Implement BETWEEN operator

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach reassigned HIVE-2005:


Assignee: Carl Steinbach

> Implement BETWEEN operator
> --
>
> Key: HIVE-2005
> URL: https://issues.apache.org/jira/browse/HIVE-2005
> Project: Hive
>  Issue Type: New Feature
>  Components: Query Processor
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
>
> Reference: 
> http://dev.mysql.com/doc/refman/5.0/en/comparison-operators.html#operator_between

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2245) Make CombineHiveInputFormat the default hive.input.format

[Carl Steinbach (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Steinbach updated HIVE-2245:
-

Status: Patch Available  (was: Open)

@Ning: I re-ran the TestCliDriver index* tests and they all pass. Can you 
please try running these tests again on your side? Thanks.

> Make CombineHiveInputFormat the default hive.input.format
> -
>
> Key: HIVE-2245
> URL: https://issues.apache.org/jira/browse/HIVE-2245
> Project: Hive
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2245.1.patch.txt
>
>
> We should use CombineHiveInputFormat as the default Hive input format.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2239) Up the commons-codec version from 1.3 to 1.4

[John Sichi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Sichi updated HIVE-2239:
-

Attachment: HIVE-2239.2.patch

I was thinking we could just use the one from Hadoop directly (instead of 
fetching another copy from ivy), as in the attached HIVE-2239.2.patch.  I 
verified build as well as TestContribCliDriver with qfile=fileformat_base64.q.


> Up the commons-codec version from 1.3 to 1.4
> 
>
> Key: HIVE-2239
> URL: https://issues.apache.org/jira/browse/HIVE-2239
> Project: Hive
>  Issue Type: Task
>  Components: Build Infrastructure, Contrib
>Affects Versions: 0.6.0, 0.7.0, 0.8.0
>Reporter: Ashutosh Chauhan
>Assignee: Ashutosh Chauhan
> Attachments: HIVE-2239.2.patch, hive-2239.patch
>
>
> Hadoop upgraded from 1.3 to 1.4. Since, hive is launched from hadoop scripts, 
> it gets 1.4 from there and then it includes 1.3 itself. Having two different 
> versions of same jar causes unwanted grief.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (HIVE-2195) Hive queries hangs with first stage job created with zero mappers and 1 reducer,

[Vaibhav Aggarwal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Aggarwal reassigned HIVE-2195:
--

Assignee: Vaibhav Aggarwal

> Hive queries hangs with first stage job created with zero mappers and 1 
> reducer,  
> --
>
> Key: HIVE-2195
> URL: https://issues.apache.org/jira/browse/HIVE-2195
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: vitthal (Suhas) Gogate
>Assignee: Vaibhav Aggarwal
>
> This happens when query aggregate data w/ predicate selecting bunch of 
> non-existing data partitions. 
> e,g, Table XXX has five columns,  A (int), B (int), C(string), date (int) and 
> hour (int), where date/hour are the partition columns, 
> select cast((100*date+hour) as BIGINT) as datehour, sum(A) as sumA,
> sum(B) as sumB from XXX where date>=20110925 and C='test' group by date, hour 
> order by datehour  
> In the above query, make a note that selected date partition range does not 
> exists in hive table i.e. no date partitions for date>=20110925
> The above query hangs with the first map reduce job it creates, with zero 
> mappers and 1 reducer.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (HIVE-2255) uncomment test-shims in build.xml

[John Sichi (JIRA)]

uncomment test-shims in build.xml
-

 Key: HIVE-2255
 URL: https://issues.apache.org/jira/browse/HIVE-2255
 Project: Hive
  Issue Type: Bug
Reporter: John Sichi
Assignee: Ning Zhang


I saw this code in build.xml:

{noformat}
  
  
{noformat}

I used svn blame to trace it back to HIVE-818.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2253) Merge failing of join tree in exceptional case

[John Sichi (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060030#comment-13060030
 ] 

John Sichi commented on HIVE-2253:
--

We'll need a small unit test with EXPLAIN for this case.


> Merge failing of join tree in exceptional case
> --
>
> Key: HIVE-2253
> URL: https://issues.apache.org/jira/browse/HIVE-2253
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Affects Versions: 0.7.0
> Environment: hadoop 0.20.2, hive 0.7.0
>Reporter: Navis
>Priority: Minor
> Attachments: HIVE-2253.patch
>
>
> In some very exceptional cases, SemanticAnayzer fails to merge join tree. 
> Example is below.
> create table a (val1 int, val2 int)
> create table b (val1 int, val2 int)
> create table c (val1 int, val2 int)
> create table d (val1 int, val2 int)
> create table e (val1 int, val2 int)
> 1. all same(single) join key --> one MR, good
> select * from a join b on a.val1=b.val1 join c on a.val1=c.val1 join d on 
> a.val1=d.val1 join e on a.val1=e.val1
> 2. two join keys --> expected to have two MR, but resulted to three MR
> select * from a join b on a.val1=b.val1 join c on a.val1=c.val1 join d on 
> a.val1=d.val1 join e on a.val2=e.val2
> 3. by changing the join order, we could attain two MR as first-expectation.
> select * from a join e on a.val2=e.val2 join c on a.val1=c.val1 join d on 
> a.val1=d.val1 join b on a.val1=b.val1

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2245) Make CombineHiveInputFormat the default hive.input.format

[Ning Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ning Zhang updated HIVE-2245:
-

Status: Open  (was: Patch Available)

> Make CombineHiveInputFormat the default hive.input.format
> -
>
> Key: HIVE-2245
> URL: https://issues.apache.org/jira/browse/HIVE-2245
> Project: Hive
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2245.1.patch.txt
>
>
> We should use CombineHiveInputFormat as the default Hive input format.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (HIVE-2245) Make CombineHiveInputFormat the default hive.input.format

[Ning Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/HIVE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060005#comment-13060005
 ] 

Ning Zhang commented on HIVE-2245:
--

Carl, there are 11 failed tests in TestCliDriver, e.g., index_bitmap.q and many 
index_*.q. Can you take a look?

> Make CombineHiveInputFormat the default hive.input.format
> -
>
> Key: HIVE-2245
> URL: https://issues.apache.org/jira/browse/HIVE-2245
> Project: Hive
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2245.1.patch.txt
>
>
> We should use CombineHiveInputFormat as the default Hive input format.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2196) Ensure HiveConf includes all properties defined in hive-default.xml

[Chinna Rao Lalam (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chinna Rao Lalam updated HIVE-2196:
---

Status: Patch Available  (was: Open)

> Ensure HiveConf includes all properties defined in hive-default.xml
> ---
>
> Key: HIVE-2196
> URL: https://issues.apache.org/jira/browse/HIVE-2196
> Project: Hive
>  Issue Type: Bug
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2196.patch
>
>
> There are a bunch of properties that are defined in hive-default.xml but not 
> in HiveConf.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (HIVE-2196) Ensure HiveConf includes all properties defined in hive-default.xml

[Chinna Rao Lalam (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chinna Rao Lalam updated HIVE-2196:
---

Attachment: HIVE-2196.patch

> Ensure HiveConf includes all properties defined in hive-default.xml
> ---
>
> Key: HIVE-2196
> URL: https://issues.apache.org/jira/browse/HIVE-2196
> Project: Hive
>  Issue Type: Bug
>  Components: Configuration
>Reporter: Carl Steinbach
>Assignee: Carl Steinbach
> Attachments: HIVE-2196.patch
>
>
> There are a bunch of properties that are defined in hive-default.xml but not 
> in HiveConf.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira