[jira] [Created] (HIVE-3439) PARTITIONED BY clause in CREATE TABLE is order-dependent
Jonathan Natkins created HIVE-3439: -- Summary: PARTITIONED BY clause in CREATE TABLE is order-dependent Key: HIVE-3439 URL: https://issues.apache.org/jira/browse/HIVE-3439 Project: Hive Issue Type: Bug Reporter: Jonathan Natkins hive create external table foo (a int) location '/user/natty/foo' partitioned by (b int); FAILED: Parse Error: line 1:61 mismatched input 'partitioned' expecting EOF near ''/user/natty/foo'' hive create external table foo (a int) partitioned by (b int) location '/user/natty/foo'; OK Time taken: 0.051 seconds -- 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-3392) Hive unnecessarily validates table SerDes when dropping a table
Jonathan Natkins created HIVE-3392: -- Summary: Hive unnecessarily validates table SerDes when dropping a table Key: HIVE-3392 URL: https://issues.apache.org/jira/browse/HIVE-3392 Project: Hive Issue Type: Bug Reporter: Jonathan Natkins natty@hadoop1:~$ hive hive add jar /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar; Added /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar to class path Added resource: /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar hive create table test (a int) row format serde 'hive.serde.JSONSerDe'; OK Time taken: 2.399 seconds natty@hadoop1:~$ hive hive drop table test; FAILED: Hive Internal Error: java.lang.RuntimeException(MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe com.cloudera.hive.serde.JSONSerDe does not exist)) java.lang.RuntimeException: MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe com.cloudera.hive.serde.JSONSerDe does not exist) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializerFromMetaStore(Table.java:262) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializer(Table.java:253) at org.apache.hadoop.hive.ql.metadata.Table.getCols(Table.java:490) at org.apache.hadoop.hive.ql.metadata.Table.checkValidity(Table.java:162) at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:943) at org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeDropTable(DDLSemanticAnalyzer.java:700) at org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeInternal(DDLSemanticAnalyzer.java:210) at org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:243) at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:430) at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:337) at org.apache.hadoop.hive.ql.Driver.run(Driver.java:889) at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:255) at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212) at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403) at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671) at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.util.RunJar.main(RunJar.java:208) Caused by: MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe com.cloudera.hive.serde.JSONSerDe does not exist) at org.apache.hadoop.hive.metastore.MetaStoreUtils.getDeserializer(MetaStoreUtils.java:211) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializerFromMetaStore(Table.java:260) ... 20 more hive add jar /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar; Added /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar to class path Added resource: /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar hive drop table test; OK Time taken: 0.658 seconds hive -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3392) Hive unnecessarily validates table SerDes when dropping a table
[ https://issues.apache.org/jira/browse/HIVE-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-3392: --- Description: natty@hadoop1:~$ hive hive add jar /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar; Added /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar to class path Added resource: /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar hive create table test (a int) row format serde 'hive.serde.JSONSerDe'; OK Time taken: 2.399 seconds natty@hadoop1:~$ hive hive drop table test; FAILED: Hive Internal Error: java.lang.RuntimeException(MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe hive.serde.JSONSerDe does not exist)) java.lang.RuntimeException: MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe hive.serde.JSONSerDe does not exist) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializerFromMetaStore(Table.java:262) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializer(Table.java:253) at org.apache.hadoop.hive.ql.metadata.Table.getCols(Table.java:490) at org.apache.hadoop.hive.ql.metadata.Table.checkValidity(Table.java:162) at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:943) at org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeDropTable(DDLSemanticAnalyzer.java:700) at org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeInternal(DDLSemanticAnalyzer.java:210) at org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:243) at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:430) at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:337) at org.apache.hadoop.hive.ql.Driver.run(Driver.java:889) at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:255) at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212) at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403) at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671) at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.util.RunJar.main(RunJar.java:208) Caused by: MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe com.cloudera.hive.serde.JSONSerDe does not exist) at org.apache.hadoop.hive.metastore.MetaStoreUtils.getDeserializer(MetaStoreUtils.java:211) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializerFromMetaStore(Table.java:260) ... 20 more hive add jar /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar; Added /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar to class path Added resource: /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar hive drop table test; OK Time taken: 0.658 seconds hive was: natty@hadoop1:~$ hive hive add jar /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar; Added /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar to class path Added resource: /home/natty/source/sample-code/custom-serdes/target/custom-serdes-1.0-SNAPSHOT.jar hive create table test (a int) row format serde 'hive.serde.JSONSerDe'; OK Time taken: 2.399 seconds natty@hadoop1:~$ hive hive drop table test; FAILED: Hive Internal Error: java.lang.RuntimeException(MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe com.cloudera.hive.serde.JSONSerDe does not exist)) java.lang.RuntimeException: MetaException(message:org.apache.hadoop.hive.serde2.SerDeException SerDe com.cloudera.hive.serde.JSONSerDe does not exist) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializerFromMetaStore(Table.java:262) at org.apache.hadoop.hive.ql.metadata.Table.getDeserializer(Table.java:253) at org.apache.hadoop.hive.ql.metadata.Table.getCols(Table.java:490) at org.apache.hadoop.hive.ql.metadata.Table.checkValidity(Table.java:162) at org.apache.hadoop.hive.ql.metadata.Hive.getTable(Hive.java:943) at org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeDropTable(DDLSemanticAnalyzer.java:700) at
[jira] [Updated] (HIVE-3333) Specified SerDe does not get used when executing a query over JSON data
[
https://issues.apache.org/jira/browse/HIVE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Natkins updated HIVE-:
---
Attachment: hive-test-case.tar.gz
Attaching a small test case. The paths in hive.sql will have to be modified
slightly, but should be an easy reproducer.
Specified SerDe does not get used when executing a query over JSON data
---
Key: HIVE-
URL: https://issues.apache.org/jira/browse/HIVE-
Project: Hive
Issue Type: Bug
Components: Serializers/Deserializers
Reporter: Jonathan Natkins
Attachments: hive-test-case.tar.gz
I found a JSON SerDe that I wanted to try out, and I ran into some issues
attempting to use it. The script I was executing looks like this:
ADD JAR /home/natty/hive-test-case/hive-json-serde-0.2.jar;
CREATE TABLE bar (
id INT,
integers ARRAYINT,
datum STRING
) ROW FORMAT SERDE 'org.apache.hadoop.hive.contrib.serde2.JsonSerde';
LOAD DATA LOCAL INPATH '/home/natty/sample_data/json.sample' OVERWRITE INTO
TABLE bar;
SELECT * FROM bar;
The data I loaded in looks like this:
{ id: 1, integers: [ 1, 2, 3 ], datum: hello },
When the SELECT * FROM bar query executes, it returns with a failure:
hive ADD JAR /home/natty/hive-test-case/hive-json-serde-0.2.jar;
Added /home/natty/hive-test-case/hive-json-serde-0.2.jar to class path
Added resource: /home/natty/hive-test-case/hive-json-serde-0.2.jar
hive SELECT * FROM bar;
OK
Failed with exception java.io.IOException:java.lang.ClassCastException:
org.json.JSONArray cannot be cast to [Ljava.lang.Object;
Time taken: 2.335 seconds
Now, this alone doesn't bother me. What bothers me is that, if I look at the
log file, I see the following exception:
2012-08-03 13:12:11,407 ERROR CliDriver (SessionState.java:printError(380)) -
Failed with exception java.io.IOException:java.lang.ClassCastException:
org.json.JSONArray cannot be cast to [Ljava.lang.Object;
java.io.IOException: java.lang.ClassCastException: org.json.JSONArray cannot
be cast to [Ljava.lang.Object;
at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:173)
at org.apache.hadoop.hive.ql.Driver.getResults(Driver.java:1383)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:266)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:208)
Caused by: java.lang.ClassCastException: org.json.JSONArray cannot be cast to
[Ljava.lang.Object;
at
org.apache.hadoop.hive.serde2.objectinspector.StandardListObjectInspector.getList(StandardListObjectInspector.java:98)
at
org.apache.hadoop.hive.serde2.SerDeUtils.buildJSONString(SerDeUtils.java:287)
at
org.apache.hadoop.hive.serde2.SerDeUtils.getJSONString(SerDeUtils.java:213)
at
org.apache.hadoop.hive.serde2.DelimitedJSONSerDe.serializeField(DelimitedJSONSerDe.java:59)
at
org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe.serialize(LazySimpleSerDe.java:365)
at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:163)
... 11 more
Note that this exception indicates that Hive is executing code for the
DelimitedJSONSerDe, rather than the one that I specified (JsonSerde from the
jar file). Seems incorrect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3333) Specified SerDe does not get used when executing a query over JSON data
Jonathan Natkins created HIVE-:
--
Summary: Specified SerDe does not get used when executing a query
over JSON data
Key: HIVE-
URL: https://issues.apache.org/jira/browse/HIVE-
Project: Hive
Issue Type: Bug
Components: Serializers/Deserializers
Reporter: Jonathan Natkins
Attachments: hive-test-case.tar.gz
I found a JSON SerDe that I wanted to try out, and I ran into some issues
attempting to use it. The script I was executing looks like this:
ADD JAR /home/natty/hive-test-case/hive-json-serde-0.2.jar;
CREATE TABLE bar (
id INT,
integers ARRAYINT,
datum STRING
) ROW FORMAT SERDE 'org.apache.hadoop.hive.contrib.serde2.JsonSerde';
LOAD DATA LOCAL INPATH '/home/natty/sample_data/json.sample' OVERWRITE INTO
TABLE bar;
SELECT * FROM bar;
The data I loaded in looks like this:
{ id: 1, integers: [ 1, 2, 3 ], datum: hello },
When the SELECT * FROM bar query executes, it returns with a failure:
hive ADD JAR /home/natty/hive-test-case/hive-json-serde-0.2.jar;
Added /home/natty/hive-test-case/hive-json-serde-0.2.jar to class path
Added resource: /home/natty/hive-test-case/hive-json-serde-0.2.jar
hive SELECT * FROM bar;
OK
Failed with exception java.io.IOException:java.lang.ClassCastException:
org.json.JSONArray cannot be cast to [Ljava.lang.Object;
Time taken: 2.335 seconds
Now, this alone doesn't bother me. What bothers me is that, if I look at the
log file, I see the following exception:
2012-08-03 13:12:11,407 ERROR CliDriver (SessionState.java:printError(380)) -
Failed with exception java.io.IOException:java.lang.ClassCastException:
org.json.JSONArray cannot be cast to [Ljava.lang.Object;
java.io.IOException: java.lang.ClassCastException: org.json.JSONArray cannot be
cast to [Ljava.lang.Object;
at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:173)
at org.apache.hadoop.hive.ql.Driver.getResults(Driver.java:1383)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:266)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:208)
Caused by: java.lang.ClassCastException: org.json.JSONArray cannot be cast to
[Ljava.lang.Object;
at
org.apache.hadoop.hive.serde2.objectinspector.StandardListObjectInspector.getList(StandardListObjectInspector.java:98)
at
org.apache.hadoop.hive.serde2.SerDeUtils.buildJSONString(SerDeUtils.java:287)
at
org.apache.hadoop.hive.serde2.SerDeUtils.getJSONString(SerDeUtils.java:213)
at
org.apache.hadoop.hive.serde2.DelimitedJSONSerDe.serializeField(DelimitedJSONSerDe.java:59)
at
org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe.serialize(LazySimpleSerDe.java:365)
at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:163)
... 11 more
Note that this exception indicates that Hive is executing code for the
DelimitedJSONSerDe, rather than the one that I specified (JsonSerde from the
jar file). Seems incorrect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-3333) Specified SerDe does not get used when executing a query over JSON data
[
https://issues.apache.org/jira/browse/HIVE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Natkins resolved HIVE-.
Resolution: Not A Problem
I think this may have just been pilot error
Specified SerDe does not get used when executing a query over JSON data
---
Key: HIVE-
URL: https://issues.apache.org/jira/browse/HIVE-
Project: Hive
Issue Type: Bug
Components: Serializers/Deserializers
Reporter: Jonathan Natkins
Attachments: hive-test-case.tar.gz
I found a JSON SerDe that I wanted to try out, and I ran into some issues
attempting to use it. The script I was executing looks like this:
ADD JAR /home/natty/hive-test-case/hive-json-serde-0.2.jar;
CREATE TABLE bar (
id INT,
integers ARRAYINT,
datum STRING
) ROW FORMAT SERDE 'org.apache.hadoop.hive.contrib.serde2.JsonSerde';
LOAD DATA LOCAL INPATH '/home/natty/sample_data/json.sample' OVERWRITE INTO
TABLE bar;
SELECT * FROM bar;
The data I loaded in looks like this:
{ id: 1, integers: [ 1, 2, 3 ], datum: hello },
When the SELECT * FROM bar query executes, it returns with a failure:
hive ADD JAR /home/natty/hive-test-case/hive-json-serde-0.2.jar;
Added /home/natty/hive-test-case/hive-json-serde-0.2.jar to class path
Added resource: /home/natty/hive-test-case/hive-json-serde-0.2.jar
hive SELECT * FROM bar;
OK
Failed with exception java.io.IOException:java.lang.ClassCastException:
org.json.JSONArray cannot be cast to [Ljava.lang.Object;
Time taken: 2.335 seconds
Now, this alone doesn't bother me. What bothers me is that, if I look at the
log file, I see the following exception:
2012-08-03 13:12:11,407 ERROR CliDriver (SessionState.java:printError(380)) -
Failed with exception java.io.IOException:java.lang.ClassCastException:
org.json.JSONArray cannot be cast to [Ljava.lang.Object;
java.io.IOException: java.lang.ClassCastException: org.json.JSONArray cannot
be cast to [Ljava.lang.Object;
at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:173)
at org.apache.hadoop.hive.ql.Driver.getResults(Driver.java:1383)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:266)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.util.RunJar.main(RunJar.java:208)
Caused by: java.lang.ClassCastException: org.json.JSONArray cannot be cast to
[Ljava.lang.Object;
at
org.apache.hadoop.hive.serde2.objectinspector.StandardListObjectInspector.getList(StandardListObjectInspector.java:98)
at
org.apache.hadoop.hive.serde2.SerDeUtils.buildJSONString(SerDeUtils.java:287)
at
org.apache.hadoop.hive.serde2.SerDeUtils.getJSONString(SerDeUtils.java:213)
at
org.apache.hadoop.hive.serde2.DelimitedJSONSerDe.serializeField(DelimitedJSONSerDe.java:59)
at
org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe.serialize(LazySimpleSerDe.java:365)
at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:163)
... 11 more
Note that this exception indicates that Hive is executing code for the
DelimitedJSONSerDe, rather than the one that I specified (JsonSerde from the
jar file). Seems incorrect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Attachment: (was: HIVE-2086.3.patch) 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, HIVE-2086.3.patch, create_like.q.out 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
[jira] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Attachment: HIVE-2086.3.patch 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, HIVE-2086.3.patch, create_like.q.out 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
[jira] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Attachment: HIVE-2086.3.patch 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, HIVE-2086.3.patch, create_like.q.out 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
[jira] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Status: Patch Available (was: Open) Just regression tests 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, HIVE-2086.3.patch, create_like.q.out 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
[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=13067522#comment-13067522 ] Jonathan Natkins commented on HIVE-2086: It looks like this was actually just fixed today, as a part of HIVE-1218. However, that fix didn't add any regression tests for this bug, so I'm going to prepare an updated patch once I finish running the test suite. 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, create_like.q.out 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
[jira] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Status: Patch Available (was: Open) 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 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
[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=13025862#comment-13025862 ] Jonathan Natkins commented on HIVE-2086: Sorry about that, I've updated the diffs. This time, there shouldn't be any failures 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 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
[jira] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Attachment: HIVE-2086.2.patch 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
[jira] [Updated] (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:all-tabpanel ] Jonathan Natkins updated HIVE-2070: --- Status: Patch Available (was: Open) https://reviews.apache.org/r/603/ 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] [Updated] (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:all-tabpanel ] Jonathan Natkins updated HIVE-2070: --- Attachment: HIVE-2070.1.patch 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] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Status: Patch Available (was: Open) https://reviews.apache.org/r/604/ 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 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
[jira] [Updated] (HIVE-2086) Data loss with external table
[ https://issues.apache.org/jira/browse/HIVE-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-2086: --- Attachment: HIVE-2086.1.patch 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 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
[jira] Updated: (HIVE-1928) GRANT/REVOKE should handle privileges as tokens, not identifiers
[
https://issues.apache.org/jira/browse/HIVE-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Natkins updated HIVE-1928:
---
Assignee: Jonathan Natkins
Status: Patch Available (was: Open)
GRANT/REVOKE should handle privileges as tokens, not identifiers
Key: HIVE-1928
URL: https://issues.apache.org/jira/browse/HIVE-1928
Project: Hive
Issue Type: Bug
Components: Query Processor, Security
Affects Versions: 0.7.0
Reporter: Carl Steinbach
Assignee: Jonathan Natkins
Priority: Critical
Attachments: HIVE-1928.1.patch
The grammar for the GRANT and REVOKE Privileges statements currently handle
the list of privileges as a list of
identifiers. Since most of the privileges are also keywords in the HQL
grammar this requires users
to individually quote-escape each of the privileges, e.g:
{code}
grant `Create` on table authorization_part to user hive_test_user;
grant `Update` on table authorization_part to user hive_test_user;
grant `Drop` on table authorization_part to user hive_test_user;
grant `select` on table src to user hive_test_user;
{code}
Both MySQL and the SQL standard treat privileges as tokens. Hive should do
the same.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1928) GRANT/REVOKE should handle privileges as tokens, not identifiers
[
https://issues.apache.org/jira/browse/HIVE-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Natkins updated HIVE-1928:
---
Attachment: HIVE-1928.1.patch
https://reviews.apache.org/r/427/
GRANT/REVOKE should handle privileges as tokens, not identifiers
Key: HIVE-1928
URL: https://issues.apache.org/jira/browse/HIVE-1928
Project: Hive
Issue Type: Bug
Components: Query Processor, Security
Affects Versions: 0.7.0
Reporter: Carl Steinbach
Assignee: Jonathan Natkins
Priority: Critical
Attachments: HIVE-1928.1.patch
The grammar for the GRANT and REVOKE Privileges statements currently handle
the list of privileges as a list of
identifiers. Since most of the privileges are also keywords in the HQL
grammar this requires users
to individually quote-escape each of the privileges, e.g:
{code}
grant `Create` on table authorization_part to user hive_test_user;
grant `Update` on table authorization_part to user hive_test_user;
grant `Drop` on table authorization_part to user hive_test_user;
grant `select` on table src to user hive_test_user;
{code}
Both MySQL and the SQL standard treat privileges as tokens. Hive should do
the same.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1211) Tapping logs from child processes
[
https://issues.apache.org/jira/browse/HIVE-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Natkins updated HIVE-1211:
---
Status: Patch Available (was: Open)
Tapping logs from child processes
-
Key: HIVE-1211
URL: https://issues.apache.org/jira/browse/HIVE-1211
Project: Hive
Issue Type: Improvement
Components: Logging
Reporter: bc Wong
Assignee: Carl Steinbach
Attachments: HIVE-1211-2.patch, HIVE-1211.1.patch,
HIVE-1211.3.patch.txt, HIVE-1211.4.patch.txt, HIVE-1211.5.patch.txt,
HIVE-1211.6.patch.txt, HIVE-1211.7.patch.txt, HIVE-1211.8.patch.txt
Stdout/stderr from child processes (e.g. {{MapRedTask}}) are redirected to
the parent's stdout/stderr. There is little one can do to to sort out which
log is from which query.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1971) Verbose/echo mode for the Hive CLI
[ https://issues.apache.org/jira/browse/HIVE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-1971: --- Attachment: HIVE-1971.2.patch.txt Patch updated Verbose/echo mode for the Hive CLI -- Key: HIVE-1971 URL: https://issues.apache.org/jira/browse/HIVE-1971 Project: Hive Issue Type: New Feature Components: CLI Reporter: Jonathan Natkins Assignee: Jonathan Natkins Attachments: HIVE-1971.1.patch.txt, HIVE-1971.2.patch.txt It would be very beneficial to have a mode which allows a user to run a SQL script, and have each command echoed to the console as it's executed. This would be useful in figuring out which SQL statement is causing failures during test runs, especially when running particularly long scripts. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (HIVE-1971) Verbose/echo mode for the Hive CLI
Verbose/echo mode for the Hive CLI -- Key: HIVE-1971 URL: https://issues.apache.org/jira/browse/HIVE-1971 Project: Hive Issue Type: New Feature Components: CLI Reporter: Jonathan Natkins It would be very beneficial to have a mode which allows a user to run a SQL script, and have each command echoed to the console as it's executed. This would be useful in figuring out which SQL statement is causing failures during test runs, especially when running particularly long scripts. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1971) Verbose/echo mode for the Hive CLI
[ https://issues.apache.org/jira/browse/HIVE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-1971: --- Attachment: HIVE-1971.1.patch.txt Verbose/echo mode for the Hive CLI -- Key: HIVE-1971 URL: https://issues.apache.org/jira/browse/HIVE-1971 Project: Hive Issue Type: New Feature Components: CLI Reporter: Jonathan Natkins Assignee: Jonathan Natkins Attachments: HIVE-1971.1.patch.txt It would be very beneficial to have a mode which allows a user to run a SQL script, and have each command echoed to the console as it's executed. This would be useful in figuring out which SQL statement is causing failures during test runs, especially when running particularly long scripts. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1971) Verbose/echo mode for the Hive CLI
[ https://issues.apache.org/jira/browse/HIVE-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-1971: --- Assignee: Jonathan Natkins Status: Patch Available (was: Open) https://reviews.apache.org/r/404/ Verbose/echo mode for the Hive CLI -- Key: HIVE-1971 URL: https://issues.apache.org/jira/browse/HIVE-1971 Project: Hive Issue Type: New Feature Components: CLI Reporter: Jonathan Natkins Assignee: Jonathan Natkins Attachments: HIVE-1971.1.patch.txt It would be very beneficial to have a mode which allows a user to run a SQL script, and have each command echoed to the console as it's executed. This would be useful in figuring out which SQL statement is causing failures during test runs, especially when running particularly long scripts. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1735) Extend Explode UDTF to handle Maps
[ https://issues.apache.org/jira/browse/HIVE-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-1735: --- Status: Patch Available (was: Open) Updated patch available https://reviews.apache.org/r/354 Extend Explode UDTF to handle Maps -- Key: HIVE-1735 URL: https://issues.apache.org/jira/browse/HIVE-1735 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Jonathan Natkins Attachments: HIVE-1735.1.patch The explode() UDTF currently only accepts arrays as input. We should modify it so that it can also handle map inputs, in which case it will output two columns corresponding to the key and value fields. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HIVE-1735) Extend Explode UDTF to handle Maps
[ https://issues.apache.org/jira/browse/HIVE-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-1735: --- Attachment: HIVE-1735.2.patch.txt Extend Explode UDTF to handle Maps -- Key: HIVE-1735 URL: https://issues.apache.org/jira/browse/HIVE-1735 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Jonathan Natkins Attachments: HIVE-1735.1.patch, HIVE-1735.2.patch.txt, HIVE-1735.2.patch.txt The explode() UDTF currently only accepts arrays as input. We should modify it so that it can also handle map inputs, in which case it will output two columns corresponding to the key and value fields. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVE-1636) Implement SHOW TABLES {FROM | IN} db_name
[
https://issues.apache.org/jira/browse/HIVE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986270#action_12986270
]
Jonathan Natkins commented on HIVE-1636:
This new patch addresses the code review comments
Implement SHOW TABLES {FROM | IN} db_name
---
Key: HIVE-1636
URL: https://issues.apache.org/jira/browse/HIVE-1636
Project: Hive
Issue Type: New Feature
Components: Query Processor
Reporter: Carl Steinbach
Assignee: Jonathan Natkins
Attachments: HIVE-1636.1.patch.txt, HIVE-1636.2.patch.txt,
HIVE-1636.3.patch
Make it possible to list the tables in a specific database using the
following syntax borrowed from MySQL:
{noformat}
SHOW TABLES [{FROM|IN} db_name]
{noformat}
See http://dev.mysql.com/doc/refman/5.0/en/show-tables.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1735) Extend Explode UDTF to handle Maps
[ https://issues.apache.org/jira/browse/HIVE-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Natkins updated HIVE-1735: --- Attachment: HIVE-1735.1.patch Extend Explode UDTF to handle Maps -- Key: HIVE-1735 URL: https://issues.apache.org/jira/browse/HIVE-1735 Project: Hive Issue Type: New Feature Components: UDF Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-1735.1.patch The explode() UDTF currently only accepts arrays as input. We should modify it so that it can also handle map inputs, in which case it will output two columns corresponding to the key and value fields. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1636) Implement SHOW TABLES {FROM | IN} db_name
[
https://issues.apache.org/jira/browse/HIVE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Natkins updated HIVE-1636:
---
Status: Patch Available (was: Open)
https://reviews.apache.org/r/323/diff/
Implement SHOW TABLES {FROM | IN} db_name
---
Key: HIVE-1636
URL: https://issues.apache.org/jira/browse/HIVE-1636
Project: Hive
Issue Type: New Feature
Components: Query Processor
Reporter: Carl Steinbach
Assignee: Jonathan Natkins
Attachments: HIVE-1636.1.patch.txt, HIVE-1636.2.patch.txt
Make it possible to list the tables in a specific database using the
following syntax borrowed from MySQL:
{noformat}
SHOW TABLES [{FROM|IN} db_name]
{noformat}
See http://dev.mysql.com/doc/refman/5.0/en/show-tables.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1636) Implement SHOW TABLES {FROM | IN} db_name
[
https://issues.apache.org/jira/browse/HIVE-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Natkins updated HIVE-1636:
---
Attachment: HIVE-1636.1.patch.txt
Implement SHOW TABLES {FROM | IN} db_name
---
Key: HIVE-1636
URL: https://issues.apache.org/jira/browse/HIVE-1636
Project: Hive
Issue Type: New Feature
Components: Query Processor
Reporter: Carl Steinbach
Assignee: Carl Steinbach
Attachments: HIVE-1636.1.patch.txt
Make it possible to list the tables in a specific database using the
following syntax borrowed from MySQL:
{noformat}
SHOW TABLES [{FROM|IN} db_name]
{noformat}
See http://dev.mysql.com/doc/refman/5.0/en/show-tables.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
