[jira] [Commented] (HIVE-1644) use filter pushdown for automatically accessing indexes
[ https://issues.apache.org/jira/browse/HIVE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027298#comment-13027298 ] John Sichi commented on HIVE-1644: -- Seems to me we should get your patch committed without the automated test case; for now we'll just have to verify index usage by checking the log. And open a followup for dealing with the empty result case. So can you prepare the final patch for me to review and commit? use filter pushdown for automatically accessing indexes --- Key: HIVE-1644 URL: https://issues.apache.org/jira/browse/HIVE-1644 Project: Hive Issue Type: Improvement Components: Indexing Affects Versions: 0.8.0 Reporter: John Sichi Assignee: Russell Melick Attachments: HIVE-1644.1.patch, HIVE-1644.10.patch, HIVE-1644.11.patch, HIVE-1644.12.patch, HIVE-1644.13.patch, HIVE-1644.14.patch, HIVE-1644.15.patch, HIVE-1644.16.patch, HIVE-1644.17.patch, HIVE-1644.18.patch, HIVE-1644.2.patch, HIVE-1644.3.patch, HIVE-1644.4.patch, HIVE-1644.5.patch, HIVE-1644.6.patch, HIVE-1644.7.patch, HIVE-1644.8.patch, HIVE-1644.9.patch, hive.log HIVE-1226 provides utilities for analyzing filters which have been pushed down to a table scan. The next step is to use these for selecting available indexes and generating access plans for those indexes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2070) SHOW GRANT grantTime field should be a human-readable timestamp
[ https://issues.apache.org/jira/browse/HIVE-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027311#comment-13027311 ] He Yongqiang commented on HIVE-2070: Carl? SHOW GRANT grantTime field should be a human-readable timestamp --- Key: HIVE-2070 URL: https://issues.apache.org/jira/browse/HIVE-2070 Project: Hive Issue Type: Improvement Components: Query Processor, Security Reporter: Jonathan Natkins Assignee: Jonathan Natkins Attachments: HIVE-2070.1.patch Unix timestamps are not super useful when trying to interpret metadata hive show grant user foo on table bar; database default table bar principalName foo principalType USER privilege Select grantTime 1300828549 grantor natty -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2137) JDBC driver doesn't encode string properly.
[ https://issues.apache.org/jira/browse/HIVE-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027321#comment-13027321 ] jin adachi commented on HIVE-2137: -- This patch can set character encoding in the connection string. For example, jdbc:hive://10.68.160.236:1/default - jdbc:hive://10.68.160.236:1/default?characterEncoding=UTF-8 If you set characterEncoding, string is decoded by character code which was set. If not set, it's the same as before. JDBC driver doesn't encode string properly. --- Key: HIVE-2137 URL: https://issues.apache.org/jira/browse/HIVE-2137 Project: Hive Issue Type: Bug Components: JDBC Affects Versions: 0.6.0, 0.7.0 Reporter: jin adachi Attachments: HiveConnection.patch, HivePreparedStatement.patch, HiveResultSet.patch, HiveStatement.patch, JdbcSessionState.patch JDBC driver decode string by client encoding. It ignore server encoding. For example, server = Linux (utf-8) client = Windows (shift-jis : it's japanese charset) It makes character corruption in the client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2138) Exception when no splits returned from index
Exception when no splits returned from index
Key: HIVE-2138
URL: https://issues.apache.org/jira/browse/HIVE-2138
Project: Hive
Issue Type: Bug
Components: Indexing
Affects Versions: 0.8.0
Reporter: Russell Melick
Running a query that uses indexing but doesn't return any results give an
exception.
{code} java.lang.IllegalArgumentException: Can not create a Path from an empty
string
at org.apache.hadoop.fs.Path.checkPathArg(Path.java:82)
at org.apache.hadoop.fs.Path.init(Path.java:90)
at org.apache.hadoop.util.StringUtils.stringToPath(StringUtils.java:224)
at
org.apache.hadoop.mapred.FileInputFormat.setInputPaths(FileInputFormat.java:282)
at
org.apache.hadoop.hive.ql.index.HiveIndexedInputFormat.getSplits(HiveIndexedInputFormat.java:123)
{code}
This could potentially be fixed by creating a new empty file to use for the
splits.
Once this is fixed, the index_auto_test_if_used.q can be used.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2138) Exception when no splits returned from index
[
https://issues.apache.org/jira/browse/HIVE-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell Melick updated HIVE-2138:
-
Attachment: index_auto_test_if_used.q
Attached test file (index_auto_test_if_used) that should test whether indexes
are used.
Exception when no splits returned from index
Key: HIVE-2138
URL: https://issues.apache.org/jira/browse/HIVE-2138
Project: Hive
Issue Type: Bug
Components: Indexing
Affects Versions: 0.8.0
Reporter: Russell Melick
Attachments: index_auto_test_if_used.q
Running a query that uses indexing but doesn't return any results give an
exception.
{code} java.lang.IllegalArgumentException: Can not create a Path from an
empty string
at org.apache.hadoop.fs.Path.checkPathArg(Path.java:82)
at org.apache.hadoop.fs.Path.init(Path.java:90)
at org.apache.hadoop.util.StringUtils.stringToPath(StringUtils.java:224)
at
org.apache.hadoop.mapred.FileInputFormat.setInputPaths(FileInputFormat.java:282)
at
org.apache.hadoop.hive.ql.index.HiveIndexedInputFormat.getSplits(HiveIndexedInputFormat.java:123)
{code}
This could potentially be fixed by creating a new empty file to use for the
splits.
Once this is fixed, the index_auto_test_if_used.q can be used.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027424#comment-13027424 ] Ning Zhang commented on HIVE-2086: -- +1 Data loss with external table - Key: HIVE-2086 URL: https://issues.apache.org/jira/browse/HIVE-2086 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.7.0 Environment: Amazon elastics mapreduce cluster Reporter: Q Long Assignee: Jonathan Natkins Attachments: HIVE-2086.1.patch, HIVE-2086.2.patch Data loss when using create external table like statement. 1) Set up an external table S, point to location L. Populate data in S. 2) Create another external table T, using statement like this: create external table T like S location L Make sure table T point to the same location as the original table S. 3) Query table T, see the same set of data in S. 4) drop table T. 5) Query table S will return nothing, and location L is deleted. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
