[jira] [Created] (HIVE-6341) ORCFileWriter does not overwrite preempted task's final file
Zhenxiao Luo created HIVE-6341: -- Summary: ORCFileWriter does not overwrite preempted task's final file Key: HIVE-6341 URL: https://issues.apache.org/jira/browse/HIVE-6341 Project: Hive Issue Type: Bug Components: File Formats Reporter: Zhenxiao Luo Insert overwrite partition get "File already exists" exception, the problem is, insert overwrite attemp0 creates and writes the final file, then it get preempted. (attempt0 did not cleanup its output final file), then attempt1 comes, attempt1 tries to write a final file, and found that file already existed, so throw the exception. Here is the stacktrace: Caused by: java.io.IOException: File already exists:s3n://netflix-dataoven-prod-users/hive/warehouse/miket.db/un_gps_group_info_v2/dateint=20140120/device_category=PS3/c49b3223-34f2-420d-a1d9-fa8164dcb7bb_000449 at org.apache.hadoop.fs.s3native.NativeS3FileSystem.create_aroundBody0(NativeS3FileSystem.java:647) at org.apache.hadoop.fs.s3native.NativeS3FileSystem$AjcClosure1.run(NativeS3FileSystem.java:1) at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) at com.netflix.bdp.s3mper.listing.ConsistentListingAspect.metastoreUpdate(ConsistentListingAspect.java:197) at org.apache.hadoop.fs.s3native.NativeS3FileSystem.create(NativeS3FileSystem.java:646) at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:557) at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:538) at org.apache.hadoop.hive.ql.io.orc.WriterImpl.ensureWriter(WriterImpl.java:1320) at org.apache.hadoop.hive.ql.io.orc.WriterImpl.flushStripe(WriterImpl.java:1337) at org.apache.hadoop.hive.ql.io.orc.WriterImpl.checkMemory(WriterImpl.java:173) at org.apache.hadoop.hive.ql.io.orc.MemoryManager.notifyWriters(MemoryManager.java:162) at org.apache.hadoop.hive.ql.io.orc.MemoryManager.addedRow(MemoryManager.java:151) at org.apache.hadoop.hive.ql.io.orc.WriterImpl.addRow(WriterImpl.java:1475) at org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat$OrcRecordWriter.write(OrcOutputFormat.java:88) at org.apache.hadoop.hive.ql.exec.FileSinkOperator.processOp(FileSinkOperator.java:688) ... 12 more It is ORCFileWriter does not overwrite that causes the problem: 1. org.apache.hadoop.hive.ql.io.orc.WriterImpl.ensureWriter rawWriter = fs.create(path, false, HDFS_BUFFER_SIZE, 2. org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat.getHiveRecordWriter final OutputStream outStream = Utilities.createCompressedStream(jc, fs .create(outPath), isCompressed); 3. org.apache.hadoop.io.SequenceFile.BlockCompressWriter.BlockCompressWriter fs.create(name, true, bufferSize, replication, blockSize, progress), In the latter 2 cases, fs.create is called with the parameter overwrite == true (overwrite defaults to true). We should set overwrite = true in ORCWriterImpl to fix this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HIVE-3797) Add option for hive server to initialize and add resources registered to it to clients
[ https://issues.apache.org/jira/browse/HIVE-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555736#comment-13555736 ] Zhenxiao Luo commented on HIVE-3797: The patch looks good to me. Non-committer +1. > Add option for hive server to initialize and add resources registered to it > to clients > -- > > Key: HIVE-3797 > URL: https://issues.apache.org/jira/browse/HIVE-3797 > Project: Hive > Issue Type: Improvement > Components: Server Infrastructure >Reporter: Navis >Assignee: Navis >Priority: Minor > Attachments: HIVE-3797.D7353.1.patch, HIVE-3797.D7353.2.patch, > HIVE-3797.D7353.3.patch > > > CliDriver has -i option for initializing the session. HiveServer also should > have one and make resources usable for clients if needed. > hive --service hiveserver -i init.q -u > -i for init script > -u for publishing resources(file,jar,etc.) to clients -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3799) Better error message if metalisteners or hookContext cannot be loaded/instantiated
[
https://issues.apache.org/jira/browse/HIVE-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554127#comment-13554127
]
Zhenxiao Luo commented on HIVE-3799:
Non-committer +1.
> Better error message if metalisteners or hookContext cannot be
> loaded/instantiated
> --
>
> Key: HIVE-3799
> URL: https://issues.apache.org/jira/browse/HIVE-3799
> Project: Hive
> Issue Type: Improvement
> Components: Diagnosability, Logging
>Reporter: Sudhanshu Arora
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-3799.D7719.1.patch, HIVE-3799.D7719.2.patch
>
>
> If I am not able to instantiate MetaListener or HookContext because of some
> dependent class missing, the only error I get is InvocationTargetException.
> MetaStoreUtils.getMetaListener should be changed as following:
> try {
> T listener = (T) Class.forName(
> listenerImpl.trim(), true,
> JavaUtils.getClassLoader()).getConstructor(
> Configuration.class).newInstance(conf);
> listeners.add(listener);
> } catch (InvocationTargetException e) {
> throw new MetaException("Failed to instantiate listener named: "+
> listenerImpl + " reason: " + e.getCause().toString());
> } catch (Exception e) {
> throw new MetaException("Failed to instantiate listener named: "+
> listenerImpl + " reason: " + e.toString());
> }
> Similarly Driver.getHooks should be changed to handle
> InvocationTargetException in a better way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3603) Enable client-side caching for scans on HBase
[ https://issues.apache.org/jira/browse/HIVE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554121#comment-13554121 ] Zhenxiao Luo commented on HIVE-3603: Looks good to me. Non-committer +1. > Enable client-side caching for scans on HBase > - > > Key: HIVE-3603 > URL: https://issues.apache.org/jira/browse/HIVE-3603 > Project: Hive > Issue Type: Improvement >Reporter: Karthik Ranganathan >Assignee: Navis >Priority: Minor > Attachments: HIVE-3603.D7761.1.patch > > > HBaseHandler sets up a TableInputFormat MR job against HBase to read data in. > The underlying implementation (in HBaseHandler.java) makes an RPC call per > row-key, which makes it very inefficient. Need to specify a client side cache > size on the scan. > Note that HBase currently only supports num-rows based caching (no way to > specify a memory limit). Created HBASE-6770 to address this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3582) NPE in union processing followed by lateral view followed by 2 group bys
[ https://issues.apache.org/jira/browse/HIVE-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554114#comment-13554114 ] Zhenxiao Luo commented on HIVE-3582: Non-commiter +1. > NPE in union processing followed by lateral view followed by 2 group bys > > > Key: HIVE-3582 > URL: https://issues.apache.org/jira/browse/HIVE-3582 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain >Assignee: Navis > Attachments: HIVE-3582.D6051.1.patch, HIVE-3582.D6051.2.patch > > > EXPLAIN > SELECT e.key, e.arr_ele, count(1) FROM ( > SELECT d.key as key, d.arr_ele as arr_ele, d.value as value, count(1) as > cnt FROM ( > SELECT c.arr_ele as arr_ele, a.key as key, a.value as value FROM ( > SELECT key, value, array(1,2,3) as arr > FROM src > UNION ALL > > SELECT key, value, array(1,2,3) as arr > FROM srcpart > WHERE ds = '2008-04-08' and hr='12' > ) a LATERAL VIEW EXPLODE(arr) c AS arr_ele > ) d group by d.key, d.arr_ele, d.value > ) e group by e.key, e.arr_ele; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3428) Fix log4j configuration errors when running hive on hadoop23
[ https://issues.apache.org/jira/browse/HIVE-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553395#comment-13553395 ] Zhenxiao Luo commented on HIVE-3428: Hi Gunther, would you please add a review request at: https://reviews.facebook.net/ It is easy to review there. > Fix log4j configuration errors when running hive on hadoop23 > > > Key: HIVE-3428 > URL: https://issues.apache.org/jira/browse/HIVE-3428 > Project: Hive > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3428.1.patch.txt, HIVE-3428.2.patch.txt, > HIVE-3428.3.patch.txt, HIVE-3428.4.patch.txt, HIVE-3428.5.patch.txt, > HIVE-3428.6.patch.txt, HIVE-3428_SHIM_EVENT_COUNTER.patch > > > There are log4j configuration errors when running hive on hadoop23, some of > them may fail testcases, since the following log4j error message could > printed to console, or to output file, which diffs from the expected output: > [junit] < log4j:ERROR Could not find value for key log4j.appender.NullAppender > [junit] < log4j:ERROR Could not instantiate appender named "NullAppender". > [junit] < 12/09/04 11:34:42 WARN conf.HiveConf: hive-site.xml not found on > CLASSPATH -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2264) Hive server is SHUTTING DOWN when invalid queries beeing executed.
[
https://issues.apache.org/jira/browse/HIVE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549405#comment-13549405
]
Zhenxiao Luo commented on HIVE-2264:
This patch is very useful. like the idea.
Non-Committer +1.
> Hive server is SHUTTING DOWN when invalid queries beeing executed.
> --
>
> Key: HIVE-2264
> URL: https://issues.apache.org/jira/browse/HIVE-2264
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Affects Versions: 0.9.0
> Environment: SuSE-Linux-11
>Reporter: rohithsharma
>Assignee: Navis
>Priority: Critical
> Attachments: HIVE-2264.1.patch.txt
>
>
> When invalid query is beeing executed, Hive server is shutting down.
> {noformat}
> "CREATE TABLE SAMPLETABLE(IP STRING , showtime BIGINT ) partitioned by (ds
> string,ipz int) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\040'"
> "ALTER TABLE SAMPLETABLE add Partition(ds='sf') location
> '/user/hive/warehouse' Partition(ipz=100) location '/user/hive/warehouse'"
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3235) Support jobId notification for MaredTasks
[ https://issues.apache.org/jira/browse/HIVE-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3235: --- Status: Open (was: Patch Available) comments on Phabricator > Support jobId notification for MaredTasks > - > > Key: HIVE-3235 > URL: https://issues.apache.org/jira/browse/HIVE-3235 > Project: Hive > Issue Type: Improvement > Components: Diagnosability >Affects Versions: 0.10.0 >Reporter: Navis >Assignee: Navis >Priority: Trivial > > JobId for each MapredTask is requested for monitoring purpose. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3235) Support jobId notification for MaredTasks
[ https://issues.apache.org/jira/browse/HIVE-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549401#comment-13549401 ] Zhenxiao Luo commented on HIVE-3235: How about file a Hadoop Jira to get JobStartNotification, and make this Jira depends on that one? > Support jobId notification for MaredTasks > - > > Key: HIVE-3235 > URL: https://issues.apache.org/jira/browse/HIVE-3235 > Project: Hive > Issue Type: Improvement > Components: Diagnosability >Affects Versions: 0.10.0 >Reporter: Navis >Assignee: Navis >Priority: Trivial > > JobId for each MapredTask is requested for monitoring purpose. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3797) Add option for hive server to initialize and add resources registered to it to clients
[ https://issues.apache.org/jira/browse/HIVE-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3797: --- Status: Open (was: Patch Available) Comments at Phabricator > Add option for hive server to initialize and add resources registered to it > to clients > -- > > Key: HIVE-3797 > URL: https://issues.apache.org/jira/browse/HIVE-3797 > Project: Hive > Issue Type: Improvement > Components: Server Infrastructure >Reporter: Navis >Assignee: Navis >Priority: Minor > Attachments: HIVE-3797.D7353.1.patch > > > CliDriver has -i option for initializing the session. HiveServer also should > have one and make resources usable for clients if needed. > hive --service hiveserver -i init.q -u > -i for init script > -u for publishing resources(file,jar,etc.) to clients -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3799) Better error message if metalisteners or hookContext cannot be loaded/instantiated
[
https://issues.apache.org/jira/browse/HIVE-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3799:
---
Status: Open (was: Patch Available)
Looks good. Minor comments at phabricator.
> Better error message if metalisteners or hookContext cannot be
> loaded/instantiated
> --
>
> Key: HIVE-3799
> URL: https://issues.apache.org/jira/browse/HIVE-3799
> Project: Hive
> Issue Type: Improvement
> Components: Diagnosability, Logging
>Affects Versions: 0.9.0
>Reporter: Sudhanshu Arora
>Assignee: Navis
>Priority: Trivial
> Attachments: HIVE-3799.D7719.1.patch
>
>
> If I am not able to instantiate MetaListener or HookContext because of some
> dependent class missing, the only error I get is InvocationTargetException.
> MetaStoreUtils.getMetaListener should be changed as following:
> try {
> T listener = (T) Class.forName(
> listenerImpl.trim(), true,
> JavaUtils.getClassLoader()).getConstructor(
> Configuration.class).newInstance(conf);
> listeners.add(listener);
> } catch (InvocationTargetException e) {
> throw new MetaException("Failed to instantiate listener named: "+
> listenerImpl + " reason: " + e.getCause().toString());
> } catch (Exception e) {
> throw new MetaException("Failed to instantiate listener named: "+
> listenerImpl + " reason: " + e.toString());
> }
> Similarly Driver.getHooks should be changed to handle
> InvocationTargetException in a better way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3603) Enable client-side caching for scans on HBase
[ https://issues.apache.org/jira/browse/HIVE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3603: --- Status: Open (was: Patch Available) > Enable client-side caching for scans on HBase > - > > Key: HIVE-3603 > URL: https://issues.apache.org/jira/browse/HIVE-3603 > Project: Hive > Issue Type: Improvement >Reporter: Karthik Ranganathan >Assignee: Navis >Priority: Minor > Attachments: HIVE-3603.D7761.1.patch > > > HBaseHandler sets up a TableInputFormat MR job against HBase to read data in. > The underlying implementation (in HBaseHandler.java) makes an RPC call per > row-key, which makes it very inefficient. Need to specify a client side cache > size on the scan. > Note that HBase currently only supports num-rows based caching (no way to > specify a memory limit). Created HBASE-6770 to address this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3582) NPE in union processing followed by lateral view followed by 2 group bys
[ https://issues.apache.org/jira/browse/HIVE-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3582: --- Status: Open (was: Patch Available) > NPE in union processing followed by lateral view followed by 2 group bys > > > Key: HIVE-3582 > URL: https://issues.apache.org/jira/browse/HIVE-3582 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain >Assignee: Navis > Attachments: HIVE-3582.D6051.1.patch > > > EXPLAIN > SELECT e.key, e.arr_ele, count(1) FROM ( > SELECT d.key as key, d.arr_ele as arr_ele, d.value as value, count(1) as > cnt FROM ( > SELECT c.arr_ele as arr_ele, a.key as key, a.value as value FROM ( > SELECT key, value, array(1,2,3) as arr > FROM src > UNION ALL > > SELECT key, value, array(1,2,3) as arr > FROM srcpart > WHERE ds = '2008-04-08' and hr='12' > ) a LATERAL VIEW EXPLODE(arr) c AS arr_ele > ) d group by d.key, d.arr_ele, d.value > ) e group by e.key, e.arr_ele; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3603) Enable client-side caching for scans on HBase
[ https://issues.apache.org/jira/browse/HIVE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547610#comment-13547610 ] Zhenxiao Luo commented on HIVE-3603: Non-Committer Review, minor comments at: https://reviews.facebook.net/D7761 > Enable client-side caching for scans on HBase > - > > Key: HIVE-3603 > URL: https://issues.apache.org/jira/browse/HIVE-3603 > Project: Hive > Issue Type: Improvement >Reporter: Karthik Ranganathan >Assignee: Navis >Priority: Minor > Attachments: HIVE-3603.D7761.1.patch > > > HBaseHandler sets up a TableInputFormat MR job against HBase to read data in. > The underlying implementation (in HBaseHandler.java) makes an RPC call per > row-key, which makes it very inefficient. Need to specify a client side cache > size on the scan. > Note that HBase currently only supports num-rows based caching (no way to > specify a memory limit). Created HBASE-6770 to address this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3582) NPE in union processing followed by lateral view followed by 2 group bys
[ https://issues.apache.org/jira/browse/HIVE-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547605#comment-13547605 ] Zhenxiao Luo commented on HIVE-3582: Hi Navis, I did an non-committer review. Mostly Good. Leave comments at: https://reviews.facebook.net/D6051 Also, maybe we could CC Namit in the Revision? Thanks, Zhenxiao > NPE in union processing followed by lateral view followed by 2 group bys > > > Key: HIVE-3582 > URL: https://issues.apache.org/jira/browse/HIVE-3582 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain >Assignee: Navis > Attachments: HIVE-3582.D6051.1.patch > > > EXPLAIN > SELECT e.key, e.arr_ele, count(1) FROM ( > SELECT d.key as key, d.arr_ele as arr_ele, d.value as value, count(1) as > cnt FROM ( > SELECT c.arr_ele as arr_ele, a.key as key, a.value as value FROM ( > SELECT key, value, array(1,2,3) as arr > FROM src > UNION ALL > > SELECT key, value, array(1,2,3) as arr > FROM srcpart > WHERE ds = '2008-04-08' and hr='12' > ) a LATERAL VIEW EXPLODE(arr) c AS arr_ele > ) d group by d.key, d.arr_ele, d.value > ) e group by e.key, e.arr_ele; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3788) testCliDriver_repair fails on hadoop-1
[ https://issues.apache.org/jira/browse/HIVE-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545287#comment-13545287 ] Zhenxiao Luo commented on HIVE-3788: Agree with Ashutosh. This patch looks good to me. Non-committer +1 Also, Gunther, would you please submit a review request next time at: https://reviews.facebook.net/ It is easier to review code there. Thanks, Zhenxiao > testCliDriver_repair fails on hadoop-1 > -- > > Key: HIVE-3788 > URL: https://issues.apache.org/jira/browse/HIVE-3788 > Project: Hive > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Gunther Hagleitner >Assignee: Gunther Hagleitner > Attachments: HIVE-3788.2.patch, HIVE-3788.patch > > > Actually functionality is working correctly, but incorrect include/exclude > macro make cause the wrong query file to be run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3862) testNegativeCliDriver_cascade_dbdrop fails on hadoop-1
[ https://issues.apache.org/jira/browse/HIVE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545286#comment-13545286 ] Zhenxiao Luo commented on HIVE-3862: Looks good to me. Non-committer +1 BTW, Gunther, would you please submit a review request next time at: https://reviews.facebook.net/ It is easier to review code there. Thanks, Zhenxiao > testNegativeCliDriver_cascade_dbdrop fails on hadoop-1 > -- > > Key: HIVE-3862 > URL: https://issues.apache.org/jira/browse/HIVE-3862 > Project: Hive > Issue Type: Bug >Affects Versions: 0.10.0 >Reporter: Gunther Hagleitner >Assignee: Gunther Hagleitner > Attachments: HIVE-3862.patch > > > Actually functionality is working correctly, but incorrect include/exclude > macro make cause the wrong query file to be run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3733) Improve Hive's logic for conditional merge
[ https://issues.apache.org/jira/browse/HIVE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo reassigned HIVE-3733: -- Assignee: Zhenxiao Luo (was: Pradeep Kamath) > Improve Hive's logic for conditional merge > -- > > Key: HIVE-3733 > URL: https://issues.apache.org/jira/browse/HIVE-3733 > Project: Hive > Issue Type: Improvement >Reporter: Pradeep Kamath >Assignee: Zhenxiao Luo > Attachments: HIVE-3733.1.patch.txt, HIVE-3733.3.patch.txt, > HIVE-3733.4.patch.txt, HIVE-3733.5.patch.txt, HIVE-3733.optimizer.patch.txt > > > If the config hive.merge.mapfiles is set to true and hive.merge.mapredfiles > is set to false then when hive encounters a FileSinkOperator when generating > map reduce tasks, it will look at the entire job to see if it has a reducer, > if it does it will not merge. Instead it should be check if the > FileSinkOperator is a child of the reducer. This means that outputs generated > in the mapper will be merged, and outputs generated in the reducer will not > be, the intended effect of setting those configs. > Simple repro: > set hive.merge.mapfiles=true; > set hive.merge.mapredfiles=false; > EXPLAIN > FROM > INSERT OVERWRITE TABLE SELECT key, COUNT(*) group by key > INSERT OVERWRITE TABLE SELECT *; > The output should contain a Conditional Operator, Mapred Stages, and Move > tasks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3837) Three Table BucketMapJoin is failing
[ https://issues.apache.org/jira/browse/HIVE-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3837: --- Description: The following three table bucketmapjoin query returns 0 as result: set hive.optimize.bucketmapjoin = true; set hive.input.format = org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat; CREATE TABLE t1 (key1 int, value1 string) partitioned by (ds1 string) CLUSTERED BY (key1) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part1'); load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part2'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part2'); CREATE TABLE t2 (key2 int, value2 string) partitioned by (ds2 string) CLUSTERED BY (key2) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part1'); load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part2'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part2'); CREATE TABLE t3 (key3 int, value3 string) partitioned by (ds3 string) CLUSTERED BY (key3) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t3 partition(ds3='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t3 partition(ds3='part1'); -- Three Tables Join explain extended select /*+mapjoin(b,c)*/ count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (a.key1=c.key3 and a.ds1=c.ds3); select /*+mapjoin(b,c)*/ count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (a.key1=c.key3 and a.ds1=c.ds3); It should return 1114(if we run a join without mapjoin). was: The following testcase shows that three table BucketMapJoin is failing: set hive.optimize.bucketmapjoin = true; CREATE TABLE t1 (key1 int, value1 string) partitioned by (ds1 string) CLUSTERED BY (key1) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part1'); load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part2'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part2'); CREATE TABLE t2 (key2 int, value2 string) partitioned by (ds2 string) CLUSTERED BY (key2) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part1'); load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part2'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part2'); CREATE TABLE t3 (key3 int, value3 string) partitioned by (ds3 string) CLUSTERED BY (key3) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t3 partition(ds3='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t3 partition(ds3='part1'); -- Three Tables Join explain extended select /*+mapjoin(b,c)*/ count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (b.key2=c.key3 and b.ds2=c.ds3); select /*+mapjoin(b,c)*/ count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (b.key2=c.key3 and b.ds2=c.ds3); select count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (b.key2=c.key3 and b.ds2=c.ds3); The result is: PREHOOK: query: CREATE TABLE t1 (key1 int, value1 string) partitioned by (ds1 string) CLUSTERED BY (key1) INTO 2 BUCKETS STORED AS TEXTFILE PREHOOK: type: CREATETABLE POSTHOOK: query: CREATE TABLE t1 (key1 int, value1 string) partitioned by (ds1 string) CLUSTERED BY (key1) INTO 2 BUCKETS STORED AS TEXTFILE POSTHOOK: type: CREATETABLE POSTHOOK: Output: default@t1 PREHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part1') PREHOOK: type: LOAD PREHOOK: Output: default@t1 POSTHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part1') POSTHOOK: type: LOAD POSTHOOK: Output: default@t1 POSTHOOK: Output: default@t1@ds1=part1 PREHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part1') PREHOOK: type: LOAD PREHOOK: Output: default@t1@ds1=part1 POSTHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part1') POSTHOOK: type: LO
[jira] [Updated] (HIVE-581) improve group by syntax
[ https://issues.apache.org/jira/browse/HIVE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-581: -- Status: Patch Available (was: Open) > improve group by syntax > --- > > Key: HIVE-581 > URL: https://issues.apache.org/jira/browse/HIVE-581 > Project: Hive > Issue Type: Improvement > Components: Clients, Query Processor >Reporter: Larry Ogrodnek >Assignee: Zhenxiao Luo > Labels: features > Attachments: HIVE-581.1.patch.txt, HIVE-581.2.patch.txt > > > It would be nice if group by allowed either column aliases or column position > (like mysql). > It can be burdensome to have to repeat UDFs both in the select and in the > group by. > e.g. instead of: > select f1(col1), f2(col2), f3(col3), count(1) group by f1(col1), f2(col2), > f3(col3); > it would allow: > select f1(col1), f2(col2), f3(col3), count(1) group by 1, 2, 3; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-581) improve group by syntax
[ https://issues.apache.org/jira/browse/HIVE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539837#comment-13539837 ] Zhenxiao Luo commented on HIVE-581: --- Hi Namit, I updated my patch at: https://reviews.facebook.net/D7623 > improve group by syntax > --- > > Key: HIVE-581 > URL: https://issues.apache.org/jira/browse/HIVE-581 > Project: Hive > Issue Type: Improvement > Components: Clients, Query Processor >Reporter: Larry Ogrodnek >Assignee: Zhenxiao Luo > Labels: features > Attachments: HIVE-581.1.patch.txt, HIVE-581.2.patch.txt > > > It would be nice if group by allowed either column aliases or column position > (like mysql). > It can be burdensome to have to repeat UDFs both in the select and in the > group by. > e.g. instead of: > select f1(col1), f2(col2), f3(col3), count(1) group by f1(col1), f2(col2), > f3(col3); > it would allow: > select f1(col1), f2(col2), f3(col3), count(1) group by 1, 2, 3; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-581) improve group by syntax
[ https://issues.apache.org/jira/browse/HIVE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-581: -- Attachment: HIVE-581.2.patch.txt > improve group by syntax > --- > > Key: HIVE-581 > URL: https://issues.apache.org/jira/browse/HIVE-581 > Project: Hive > Issue Type: Improvement > Components: Clients, Query Processor >Reporter: Larry Ogrodnek >Assignee: Zhenxiao Luo > Labels: features > Attachments: HIVE-581.1.patch.txt, HIVE-581.2.patch.txt > > > It would be nice if group by allowed either column aliases or column position > (like mysql). > It can be burdensome to have to repeat UDFs both in the select and in the > group by. > e.g. instead of: > select f1(col1), f2(col2), f3(col3), count(1) group by f1(col1), f2(col2), > f3(col3); > it would allow: > select f1(col1), f2(col2), f3(col3), count(1) group by 1, 2, 3; -- 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-3837) Three Table BucketMapJoin is failing
Zhenxiao Luo created HIVE-3837: -- Summary: Three Table BucketMapJoin is failing Key: HIVE-3837 URL: https://issues.apache.org/jira/browse/HIVE-3837 Project: Hive Issue Type: Bug Reporter: Zhenxiao Luo Assignee: Zhenxiao Luo The following testcase shows that three table BucketMapJoin is failing: set hive.optimize.bucketmapjoin = true; CREATE TABLE t1 (key1 int, value1 string) partitioned by (ds1 string) CLUSTERED BY (key1) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part1'); load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part2'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part2'); CREATE TABLE t2 (key2 int, value2 string) partitioned by (ds2 string) CLUSTERED BY (key2) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part1'); load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part2'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part2'); CREATE TABLE t3 (key3 int, value3 string) partitioned by (ds3 string) CLUSTERED BY (key3) INTO 2 BUCKETS STORED AS TEXTFILE; load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t3 partition(ds3='part1'); load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t3 partition(ds3='part1'); -- Three Tables Join explain extended select /*+mapjoin(b,c)*/ count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (b.key2=c.key3 and b.ds2=c.ds3); select /*+mapjoin(b,c)*/ count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (b.key2=c.key3 and b.ds2=c.ds3); select count(*) from t1 a join t2 b on (a.key1=b.key2 and a.ds1=b.ds2) join t3 c on (b.key2=c.key3 and b.ds2=c.ds3); The result is: PREHOOK: query: CREATE TABLE t1 (key1 int, value1 string) partitioned by (ds1 string) CLUSTERED BY (key1) INTO 2 BUCKETS STORED AS TEXTFILE PREHOOK: type: CREATETABLE POSTHOOK: query: CREATE TABLE t1 (key1 int, value1 string) partitioned by (ds1 string) CLUSTERED BY (key1) INTO 2 BUCKETS STORED AS TEXTFILE POSTHOOK: type: CREATETABLE POSTHOOK: Output: default@t1 PREHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part1') PREHOOK: type: LOAD PREHOOK: Output: default@t1 POSTHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part1') POSTHOOK: type: LOAD POSTHOOK: Output: default@t1 POSTHOOK: Output: default@t1@ds1=part1 PREHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part1') PREHOOK: type: LOAD PREHOOK: Output: default@t1@ds1=part1 POSTHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part1') POSTHOOK: type: LOAD POSTHOOK: Output: default@t1@ds1=part1 PREHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part2') PREHOOK: type: LOAD PREHOOK: Output: default@t1 POSTHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t1 partition(ds1='part2') POSTHOOK: type: LOAD POSTHOOK: Output: default@t1 POSTHOOK: Output: default@t1@ds1=part2 PREHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part2') PREHOOK: type: LOAD PREHOOK: Output: default@t1@ds1=part2 POSTHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t1 partition(ds1='part2') POSTHOOK: type: LOAD POSTHOOK: Output: default@t1@ds1=part2 PREHOOK: query: CREATE TABLE t2 (key2 int, value2 string) partitioned by (ds2 string) CLUSTERED BY (key2) INTO 2 BUCKETS STORED AS TEXTFILE PREHOOK: type: CREATETABLE POSTHOOK: query: CREATE TABLE t2 (key2 int, value2 string) partitioned by (ds2 string) CLUSTERED BY (key2) INTO 2 BUCKETS STORED AS TEXTFILE POSTHOOK: type: CREATETABLE POSTHOOK: Output: default@t2 PREHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part1') PREHOOK: type: LOAD PREHOOK: Output: default@t2 POSTHOOK: query: load data local inpath '../data/files/srcbucket20.txt' INTO TABLE t2 partition(ds2='part1') POSTHOOK: type: LOAD POSTHOOK: Output: default@t2 POSTHOOK: Output: default@t2@ds2=part1 PREHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part1') PREHOOK: type: LOAD PREHOOK: Output: default@t2@ds2=part1 POSTHOOK: query: load data local inpath '../data/files/srcbucket21.txt' INTO TABLE t2 partition(ds2='part1') POSTHOOK
[jira] [Updated] (HIVE-581) improve group by syntax
[ https://issues.apache.org/jira/browse/HIVE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-581: -- Status: Patch Available (was: Open) > improve group by syntax > --- > > Key: HIVE-581 > URL: https://issues.apache.org/jira/browse/HIVE-581 > Project: Hive > Issue Type: Improvement > Components: Clients, Query Processor >Reporter: Larry Ogrodnek >Assignee: Zhenxiao Luo > Labels: features > Attachments: HIVE-581.1.patch.txt > > > It would be nice if group by allowed either column aliases or column position > (like mysql). > It can be burdensome to have to repeat UDFs both in the select and in the > group by. > e.g. instead of: > select f1(col1), f2(col2), f3(col3), count(1) group by f1(col1), f2(col2), > f3(col3); > it would allow: > select f1(col1), f2(col2), f3(col3), count(1) group by 1, 2, 3; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-581) improve group by syntax
[ https://issues.apache.org/jira/browse/HIVE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539750#comment-13539750 ] Zhenxiao Luo commented on HIVE-581: --- Review Request submitted at: https://reviews.facebook.net/D7623 > improve group by syntax > --- > > Key: HIVE-581 > URL: https://issues.apache.org/jira/browse/HIVE-581 > Project: Hive > Issue Type: Improvement > Components: Clients, Query Processor >Reporter: Larry Ogrodnek >Assignee: Weizhe Shi > Labels: features > Attachments: HIVE-581.1.patch.txt > > > It would be nice if group by allowed either column aliases or column position > (like mysql). > It can be burdensome to have to repeat UDFs both in the select and in the > group by. > e.g. instead of: > select f1(col1), f2(col2), f3(col3), count(1) group by f1(col1), f2(col2), > f3(col3); > it would allow: > select f1(col1), f2(col2), f3(col3), count(1) group by 1, 2, 3; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-581) improve group by syntax
[ https://issues.apache.org/jira/browse/HIVE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo reassigned HIVE-581: - Assignee: Zhenxiao Luo (was: Weizhe Shi) > improve group by syntax > --- > > Key: HIVE-581 > URL: https://issues.apache.org/jira/browse/HIVE-581 > Project: Hive > Issue Type: Improvement > Components: Clients, Query Processor >Reporter: Larry Ogrodnek >Assignee: Zhenxiao Luo > Labels: features > Attachments: HIVE-581.1.patch.txt > > > It would be nice if group by allowed either column aliases or column position > (like mysql). > It can be burdensome to have to repeat UDFs both in the select and in the > group by. > e.g. instead of: > select f1(col1), f2(col2), f3(col3), count(1) group by f1(col1), f2(col2), > f3(col3); > it would allow: > select f1(col1), f2(col2), f3(col3), count(1) group by 1, 2, 3; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-581) improve group by syntax
[ https://issues.apache.org/jira/browse/HIVE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-581: -- Attachment: HIVE-581.1.patch.txt > improve group by syntax > --- > > Key: HIVE-581 > URL: https://issues.apache.org/jira/browse/HIVE-581 > Project: Hive > Issue Type: Improvement > Components: Clients, Query Processor >Reporter: Larry Ogrodnek >Assignee: Zhenxiao Luo > Labels: features > Attachments: HIVE-581.1.patch.txt > > > It would be nice if group by allowed either column aliases or column position > (like mysql). > It can be burdensome to have to repeat UDFs both in the select and in the > group by. > e.g. instead of: > select f1(col1), f2(col2), f3(col3), count(1) group by f1(col1), f2(col2), > f3(col3); > it would allow: > select f1(col1), f2(col2), f3(col3), count(1) group by 1, 2, 3; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3834) Support ALTER VIEW AS SELECT in Hive
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539440#comment-13539440 ] Zhenxiao Luo commented on HIVE-3834: Thanks Namit. I added documentation at: https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-AlterViewAsSelect > Support ALTER VIEW AS SELECT in Hive > > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Fix For: 0.11 > > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt, HIVE-3834.4.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3834) Support ALTER VIEW AS SELECT in Hive
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539371#comment-13539371 ] Zhenxiao Luo commented on HIVE-3834: Hi Namit, Sorry for the failure. I fixed the failure at: https://reviews.facebook.net/D7605 Sure. I will add documentation about ALTER VIEW AS SELECT when this task is committed. Thanks, Zhenxiao > Support ALTER VIEW AS SELECT in Hive > > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt, HIVE-3834.4.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support ALTER VIEW AS SELECT in Hive
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Attachment: HIVE-3834.4.patch.txt > Support ALTER VIEW AS SELECT in Hive > > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt, HIVE-3834.4.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support ALTER VIEW AS SELECT in Hive
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Status: Patch Available (was: Open) > Support ALTER VIEW AS SELECT in Hive > > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt, HIVE-3834.4.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Attachment: HIVE-3834.3.patch.txt > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Status: Patch Available (was: Open) > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support ALTER VIEW AS SELECT in Hive
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Summary: Support ALTER VIEW AS SELECT in Hive (was: Support hive: alter view ... as ..) > Support ALTER VIEW AS SELECT in Hive > > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539269#comment-13539269 ] Zhenxiao Luo commented on HIVE-3834: Hi Namit, I updated my patch at: https://reviews.facebook.net/D7605 > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt, > HIVE-3834.3.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Status: Patch Available (was: Open) > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539227#comment-13539227 ] Zhenxiao Luo commented on HIVE-3834: Comments addressed. Review request at: https://reviews.facebook.net/D7605 > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Attachment: HIVE-3834.2.patch.txt > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt, HIVE-3834.2.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539199#comment-13539199 ] Zhenxiao Luo commented on HIVE-3834: Review request submitted at: https://reviews.facebook.net/D7605 > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Attachment: HIVE-3834.1.patch.txt > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3834) Support hive: alter view ... as ..
[ https://issues.apache.org/jira/browse/HIVE-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3834: --- Status: Patch Available (was: Open) > Support hive: alter view ... as .. > -- > > Key: HIVE-3834 > URL: https://issues.apache.org/jira/browse/HIVE-3834 > Project: Hive > Issue Type: New Feature >Reporter: Zhenxiao Luo >Assignee: Zhenxiao Luo > Attachments: HIVE-3834.1.patch.txt > > > Hive supports "alter view" on setting property, add/drop partition etc but > not "as". > If you want to change "as" part, you have to drop view, recreate it and > backfill partition etc. pretty painful. > It will be nice to support this. The reference is mysql syntax > http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Status: Patch Available (was: Open)
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt,
> HIVE-3829.3.patch.txt, HIVE-3829.4.patch.txt, HIVE-3829.5.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Attachment: HIVE-3829.5.patch.txt
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt,
> HIVE-3829.3.patch.txt, HIVE-3829.4.patch.txt, HIVE-3829.5.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
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-3834) Support hive: alter view ... as ..
Zhenxiao Luo created HIVE-3834: -- Summary: Support hive: alter view ... as .. Key: HIVE-3834 URL: https://issues.apache.org/jira/browse/HIVE-3834 Project: Hive Issue Type: New Feature Reporter: Zhenxiao Luo Assignee: Zhenxiao Luo Hive supports "alter view" on setting property, add/drop partition etc but not "as". If you want to change "as" part, you have to drop view, recreate it and backfill partition etc. pretty painful. It will be nice to support this. The reference is mysql syntax http://dev.mysql.com/doc/refman/5.0/en/alter-view.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Status: Patch Available (was: Open)
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt,
> HIVE-3829.3.patch.txt, HIVE-3829.4.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Attachment: HIVE-3829.4.patch.txt
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt,
> HIVE-3829.3.patch.txt, HIVE-3829.4.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538880#comment-13538880
]
Zhenxiao Luo commented on HIVE-3829:
Hi Namit, Thanks for the comments. I updated my patch at:
https://reviews.facebook.net/D7593
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt,
> HIVE-3829.3.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Status: Patch Available (was: Open)
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt,
> HIVE-3829.3.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Attachment: HIVE-3829.3.patch.txt
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt,
> HIVE-3829.3.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538670#comment-13538670
]
Zhenxiao Luo commented on HIVE-3829:
[~kevinwilfong] and [~mgrover]: Thanks a lot for the review. My patch is
updated for review:
https://reviews.facebook.net/D7593
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Status: Patch Available (was: Open)
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Status: Open (was: Patch Available)
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Attachment: HIVE-3829.2.patch.txt
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt, HIVE-3829.2.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Attachment: HIVE-3829.1.patch.txt
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538611#comment-13538611
]
Zhenxiao Luo commented on HIVE-3829:
review request submitted at:
https://reviews.facebook.net/D7593
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3829) Hive CLI needs UNSET TBLPROPERTY command
[
https://issues.apache.org/jira/browse/HIVE-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3829:
---
Status: Patch Available (was: Open)
> Hive CLI needs UNSET TBLPROPERTY command
>
>
> Key: HIVE-3829
> URL: https://issues.apache.org/jira/browse/HIVE-3829
> Project: Hive
> Issue Type: Bug
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Attachments: HIVE-3829.1.patch.txt
>
>
> The Hive CLI currently supports
> ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
> ...);
> To add/change the value of table properties.
> It would be really useful if Hive also supported
> ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
> Which would remove table properties
--
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-3829) Hive CLI needs UNSET TBLPROPERTY command
Zhenxiao Luo created HIVE-3829:
--
Summary: Hive CLI needs UNSET TBLPROPERTY command
Key: HIVE-3829
URL: https://issues.apache.org/jira/browse/HIVE-3829
Project: Hive
Issue Type: Bug
Reporter: Zhenxiao Luo
Assignee: Zhenxiao Luo
The Hive CLI currently supports
ALTER TABLE SET TBLPROPERTIES ('key1' = 'value1', 'key2' = 'value2',
...);
To add/change the value of table properties.
It would be really useful if Hive also supported
ALTER TABLE UNSET TBLPROPERTIES ('key1', 'key2', ...);
Which would remove table properties
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3467) BucketMapJoinOptimizer should optimize joins on partition columns
[ https://issues.apache.org/jira/browse/HIVE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3467: --- Status: Patch Available (was: Open) > BucketMapJoinOptimizer should optimize joins on partition columns > - > > Key: HIVE-3467 > URL: https://issues.apache.org/jira/browse/HIVE-3467 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.10.0 >Reporter: Kevin Wilfong >Assignee: Zhenxiao Luo > Attachments: HIVE-3467.1.patch.txt, HIVE-3467.2.patch.txt, > HIVE-3467.3.patch.txt > > > Consider the query: > SELECT * FROM t1 JOIN t2 on t1.part = t2.part and t1.key = t2.key; > Where t1 and t2 are partitioned by part and bucketed by key. > Suppose part take values 1 and 2 and t1 and t2 are bucketed into 2 buckets. > The bucket map join optimizer will put the first bucket of part=1 and part=2 > partitions of t2 into the same mapper as that of part=1 partition of t1. It > will do the same for the part=2 partition of t1. > It could take advantage of the partition values and send the first bucket of > only the part=1 partitions of t1 and t2 into one mapper and the first bucket > of only the part=2 partitions into another. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3467) BucketMapJoinOptimizer should optimize joins on partition columns
[ https://issues.apache.org/jira/browse/HIVE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527749#comment-13527749 ] Zhenxiao Luo commented on HIVE-3467: Review request updated at: https://reviews.facebook.net/D5769 > BucketMapJoinOptimizer should optimize joins on partition columns > - > > Key: HIVE-3467 > URL: https://issues.apache.org/jira/browse/HIVE-3467 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.10.0 >Reporter: Kevin Wilfong >Assignee: Zhenxiao Luo > Attachments: HIVE-3467.1.patch.txt, HIVE-3467.2.patch.txt, > HIVE-3467.3.patch.txt > > > Consider the query: > SELECT * FROM t1 JOIN t2 on t1.part = t2.part and t1.key = t2.key; > Where t1 and t2 are partitioned by part and bucketed by key. > Suppose part take values 1 and 2 and t1 and t2 are bucketed into 2 buckets. > The bucket map join optimizer will put the first bucket of part=1 and part=2 > partitions of t2 into the same mapper as that of part=1 partition of t1. It > will do the same for the part=2 partition of t1. > It could take advantage of the partition values and send the first bucket of > only the part=1 partitions of t1 and t2 into one mapper and the first bucket > of only the part=2 partitions into another. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3467) BucketMapJoinOptimizer should optimize joins on partition columns
[ https://issues.apache.org/jira/browse/HIVE-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3467: --- Attachment: HIVE-3467.3.patch.txt > BucketMapJoinOptimizer should optimize joins on partition columns > - > > Key: HIVE-3467 > URL: https://issues.apache.org/jira/browse/HIVE-3467 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.10.0 >Reporter: Kevin Wilfong >Assignee: Zhenxiao Luo > Attachments: HIVE-3467.1.patch.txt, HIVE-3467.2.patch.txt, > HIVE-3467.3.patch.txt > > > Consider the query: > SELECT * FROM t1 JOIN t2 on t1.part = t2.part and t1.key = t2.key; > Where t1 and t2 are partitioned by part and bucketed by key. > Suppose part take values 1 and 2 and t1 and t2 are bucketed into 2 buckets. > The bucket map join optimizer will put the first bucket of part=1 and part=2 > partitions of t2 into the same mapper as that of part=1 partition of t1. It > will do the same for the part=2 partition of t1. > It could take advantage of the partition values and send the first bucket of > only the part=1 partitions of t1 and t2 into one mapper and the first bucket > of only the part=2 partitions into another. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
[ https://issues.apache.org/jira/browse/HIVE-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526480#comment-13526480 ] Zhenxiao Luo commented on HIVE-3760: Sure Will do it. > TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1 > - > > Key: HIVE-3760 > URL: https://issues.apache.org/jira/browse/HIVE-3760 > Project: Hive > Issue Type: Bug >Reporter: Ashutosh Chauhan >Assignee: Gunther Hagleitner > Attachments: HIVE-3760.2.patch, hive-3760.patch > > > Actually functionality is working correctly, but incorrect include/exclude > macro in test directive is making its .q.out comparison against incorrect > results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3761) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q.out contains incorrect data.
[ https://issues.apache.org/jira/browse/HIVE-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo reassigned HIVE-3761: -- Assignee: Zhenxiao Luo > TestNegativeMinimrCliDriver_mapreduce_stack_trace.q.out contains incorrect > data. > > > Key: HIVE-3761 > URL: https://issues.apache.org/jira/browse/HIVE-3761 > Project: Hive > Issue Type: Bug >Reporter: Ashutosh Chauhan >Assignee: Zhenxiao Luo > > In particular, it doesn't contain the stack trace of failed job, which it > should. After HIVE-3760, this will run only against hadoop23, pointing out > problem is only on hadoop23 and not on hadoop20 or hadoop1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3140: --- Status: Patch Available (was: Open) > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, > hive.3140.3.patch, HIVE-3140.3.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3140: --- Attachment: HIVE-3140.3.patch.txt > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, > hive.3140.3.patch, HIVE-3140.3.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526336#comment-13526336 ] Zhenxiao Luo commented on HIVE-3140: Updated and fixed the failing testcases, which fail due to the result format change of "describe TABLE_NAME". Review request submitted at: https://reviews.facebook.net/D7173 > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, > hive.3140.3.patch > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3760) TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
[ https://issues.apache.org/jira/browse/HIVE-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526231#comment-13526231 ] Zhenxiao Luo commented on HIVE-3760: Hi, [~ashutoshc] and [~hagleitn]: I'd like to say that this is my fault. I did not set the configuration correctly when doing the EXCLUDE/INCLUDE versions. Sorry about that, and thanks a lot for the fix. Zhenixao > TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1 > - > > Key: HIVE-3760 > URL: https://issues.apache.org/jira/browse/HIVE-3760 > Project: Hive > Issue Type: Bug >Reporter: Ashutosh Chauhan >Assignee: Gunther Hagleitner > Attachments: HIVE-3760.2.patch, hive-3760.patch > > > Actually functionality is working correctly, but incorrect include/exclude > macro in test directive is making its .q.out comparison against incorrect > results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526199#comment-13526199 ] Zhenxiao Luo commented on HIVE-3140: Sure. Sorry, I did not run the whole testcases. > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt, > hive.3140.3.patch > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3140: --- Status: Patch Available (was: Open) > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3140: --- Attachment: HIVE-3140.2.patch.txt > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13514647#comment-13514647 ] Zhenxiao Luo commented on HIVE-3140: [~namit], thanks for the comments. I addressed them and patch resubmitted at: https://reviews.facebook.net/D7173 > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt, HIVE-3140.2.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3140: --- Status: Patch Available (was: Open) > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511101#comment-13511101 ] Zhenxiao Luo commented on HIVE-3140: [~namit], A review request is submitted at: https://reviews.facebook.net/D7173 > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo reassigned HIVE-3140: -- Assignee: Zhenxiao Luo > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou >Assignee: Zhenxiao Luo > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510350#comment-13510350 ] Zhenxiao Luo commented on HIVE-3140: Review Request submitted at: https://phabricator.fb.com/D648742 > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3140) Comment indenting is broken for "describe" in CLI
[ https://issues.apache.org/jira/browse/HIVE-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhenxiao Luo updated HIVE-3140: --- Attachment: HIVE-3140.1.patch.txt > Comment indenting is broken for "describe" in CLI > - > > Key: HIVE-3140 > URL: https://issues.apache.org/jira/browse/HIVE-3140 > Project: Hive > Issue Type: Bug > Components: CLI >Reporter: Xiaoxiao Hou > Labels: patch > Fix For: 0.10.0 > > Attachments: HIVE-3140.1.patch.txt > > Original Estimate: 72h > Remaining Estimate: 72h > > Just go into the CLI and type "describe [TABLE_NAME]". If a comment has > multiple lines, it is completely unreadable due to poor comment indenting. > For example: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > But it supposed to display as: > birthdayParam string 1 = comment1 > 2 = comment2 > 3 = comment3 > Comments should be indented the same amount on each line, i.e., if the > comment starts at row k for the first line of the comment, it should be > indented by k on line 2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2691) Specify location of log4j configuration files via configuration properties
[
https://issues.apache.org/jira/browse/HIVE-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-2691:
---
Status: Patch Available (was: Open)
> Specify location of log4j configuration files via configuration properties
> --
>
> Key: HIVE-2691
> URL: https://issues.apache.org/jira/browse/HIVE-2691
> Project: Hive
> Issue Type: New Feature
> Components: Configuration, Logging
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1131.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.2.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.3.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.4.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.5.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.6.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D2667.1.patch, HIVE-2691.1.patch.txt,
> HIVE-2691.2.patch.txt, HIVE-2691.D2667.1.patch
>
>
> Oozie needs to be able to override the default location of the log4j
> configuration
> files from the Hive command line, e.g:
> {noformat}
> hive -hiveconf hive.log4j.file=/home/carl/hive-log4j.properties -hiveconf
> hive.log4j.exec.file=/home/carl/hive-exec-log4j.properties
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2691) Specify location of log4j configuration files via configuration properties
[
https://issues.apache.org/jira/browse/HIVE-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-2691:
---
Attachment: HIVE-2691.2.patch.txt
> Specify location of log4j configuration files via configuration properties
> --
>
> Key: HIVE-2691
> URL: https://issues.apache.org/jira/browse/HIVE-2691
> Project: Hive
> Issue Type: New Feature
> Components: Configuration, Logging
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1131.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.2.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.3.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.4.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.5.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.6.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D2667.1.patch, HIVE-2691.1.patch.txt,
> HIVE-2691.2.patch.txt, HIVE-2691.D2667.1.patch
>
>
> Oozie needs to be able to override the default location of the log4j
> configuration
> files from the Hive command line, e.g:
> {noformat}
> hive -hiveconf hive.log4j.file=/home/carl/hive-log4j.properties -hiveconf
> hive.log4j.exec.file=/home/carl/hive-exec-log4j.properties
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2691) Specify location of log4j configuration files via configuration properties
[
https://issues.apache.org/jira/browse/HIVE-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1347#comment-1347
]
Zhenxiao Luo commented on HIVE-2691:
Updated patch submitted at:
https://reviews.facebook.net/D6789
> Specify location of log4j configuration files via configuration properties
> --
>
> Key: HIVE-2691
> URL: https://issues.apache.org/jira/browse/HIVE-2691
> Project: Hive
> Issue Type: New Feature
> Components: Configuration, Logging
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1131.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.2.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.3.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.4.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.5.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.6.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D2667.1.patch, HIVE-2691.1.patch.txt,
> HIVE-2691.2.patch.txt, HIVE-2691.D2667.1.patch
>
>
> Oozie needs to be able to override the default location of the log4j
> configuration
> files from the Hive command line, e.g:
> {noformat}
> hive -hiveconf hive.log4j.file=/home/carl/hive-log4j.properties -hiveconf
> hive.log4j.exec.file=/home/carl/hive-exec-log4j.properties
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2691) Specify location of log4j configuration files via configuration properties
[
https://issues.apache.org/jira/browse/HIVE-2691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499635#comment-13499635
]
Zhenxiao Luo commented on HIVE-2691:
@Carl and Ashutosh:
I will rebase the patch, and resubmit it soon.
Thanks,
Zhenxiao
> Specify location of log4j configuration files via configuration properties
> --
>
> Key: HIVE-2691
> URL: https://issues.apache.org/jira/browse/HIVE-2691
> Project: Hive
> Issue Type: New Feature
> Components: Configuration, Logging
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1131.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.1.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.2.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.3.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.4.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.5.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D1203.6.patch,
> ASF.LICENSE.NOT.GRANTED--HIVE-2691.D2667.1.patch, HIVE-2691.1.patch.txt,
> HIVE-2691.D2667.1.patch
>
>
> Oozie needs to be able to override the default location of the log4j
> configuration
> files from the Hive command line, e.g:
> {noformat}
> hive -hiveconf hive.log4j.file=/home/carl/hive-log4j.properties -hiveconf
> hive.log4j.exec.file=/home/carl/hive-exec-log4j.properties
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3561) Build a full SQL-compliant parser for Hive
[ https://issues.apache.org/jira/browse/HIVE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472956#comment-13472956 ] Zhenxiao Luo commented on HIVE-3561: +1 for the first approach. HiveQL is very similar to Standard SQL, yet not exactly the same. The current Hive Parser is doing good for HiveQL. There are something missing from standardSQL, I think we could add them one by one, extending the existing parser, and maybe also add some UDFs for any missing functionality. > Build a full SQL-compliant parser for Hive > -- > > Key: HIVE-3561 > URL: https://issues.apache.org/jira/browse/HIVE-3561 > Project: Hive > Issue Type: Sub-task > Components: Query Processor >Affects Versions: 0.10.0 >Reporter: Shengsheng Huang > > To build a full SQL compliant engine on Hive, we'll need a full SQL complant > parser. The current Hive parser missed a lot of grammar units from standard > SQL. To support full SQL there're possibly four approaches: > 1.Extend the existing Hive parser to support full SQL constructs. We need to > modify the current Hive.g and add any missing grammar units and resolve > conflicts. > 2.Reuse an existing open source SQL compliant parser and extend it to support > Hive extensions. We may need to adapt Semantic Analyzers to the new AST > structure. > 3.Reuse an existing SQL compliant parser and make it co-exist with the > existing Hive parser. Both parsers share the same CliDriver interface. Use a > query mode configuration to switch the query mode between SQL and HQL (this > is the approach we're now using in the 0.9.0 demo project) > 4.Reuse an existing SQL compliant parser and make it co-exist with the > existing Hive parser. Use a separate xxxCliDriver interface for standard SQL. > > Let's discuss which is the best approach. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2228) Can't use DB qualified column names in WHERE or GROUP BY clauses
[
https://issues.apache.org/jira/browse/HIVE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-2228:
---
Status: Patch Available (was: Open)
> Can't use DB qualified column names in WHERE or GROUP BY clauses
>
>
> Key: HIVE-2228
> URL: https://issues.apache.org/jira/browse/HIVE-2228
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-2228.1.patch.txt, HIVE-2228.2.patch.txt
>
>
> Hive doesn't allow you to use DB qualified column names in the WHERE or GROUP
> BY clauses. The workaround is to define a table alias:
> {noformat}
> hive> CREATE DATABASE db1;
> OK
> hive> CREATE TABLE db1.t(a INT, b INT);
> OK
> hive> SELECT * FROM db1.t WHERE db1.t.a > 100;
> FAILED: Error in semantic analysis: Line 1:26 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t WHERE t.a > 100;
> OK
> hive> SELECT * FROM db1.t GROUP BY db1.t.a;
> FAILED: Error in semantic analysis: Line 1:29 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t GROUP BY t.a;
> OK
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2228) Can't use DB qualified column names in WHERE or GROUP BY clauses
[
https://issues.apache.org/jira/browse/HIVE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471928#comment-13471928
]
Zhenxiao Luo commented on HIVE-2228:
Comments addressed. Review Request submitted at:
https://reviews.facebook.net/D5913
> Can't use DB qualified column names in WHERE or GROUP BY clauses
>
>
> Key: HIVE-2228
> URL: https://issues.apache.org/jira/browse/HIVE-2228
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-2228.1.patch.txt, HIVE-2228.2.patch.txt
>
>
> Hive doesn't allow you to use DB qualified column names in the WHERE or GROUP
> BY clauses. The workaround is to define a table alias:
> {noformat}
> hive> CREATE DATABASE db1;
> OK
> hive> CREATE TABLE db1.t(a INT, b INT);
> OK
> hive> SELECT * FROM db1.t WHERE db1.t.a > 100;
> FAILED: Error in semantic analysis: Line 1:26 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t WHERE t.a > 100;
> OK
> hive> SELECT * FROM db1.t GROUP BY db1.t.a;
> FAILED: Error in semantic analysis: Line 1:29 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t GROUP BY t.a;
> OK
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2228) Can't use DB qualified column names in WHERE or GROUP BY clauses
[
https://issues.apache.org/jira/browse/HIVE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-2228:
---
Attachment: HIVE-2228.2.patch.txt
> Can't use DB qualified column names in WHERE or GROUP BY clauses
>
>
> Key: HIVE-2228
> URL: https://issues.apache.org/jira/browse/HIVE-2228
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-2228.1.patch.txt, HIVE-2228.2.patch.txt
>
>
> Hive doesn't allow you to use DB qualified column names in the WHERE or GROUP
> BY clauses. The workaround is to define a table alias:
> {noformat}
> hive> CREATE DATABASE db1;
> OK
> hive> CREATE TABLE db1.t(a INT, b INT);
> OK
> hive> SELECT * FROM db1.t WHERE db1.t.a > 100;
> FAILED: Error in semantic analysis: Line 1:26 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t WHERE t.a > 100;
> OK
> hive> SELECT * FROM db1.t GROUP BY db1.t.a;
> FAILED: Error in semantic analysis: Line 1:29 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t GROUP BY t.a;
> OK
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-1977:
---
Status: Patch Available (was: Open)
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt, HIVE-1977.5.patch.txt,
> HIVE-1977.6.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471366#comment-13471366
]
Zhenxiao Luo commented on HIVE-1977:
@Carl: Thanks a lot for the comments. I updated my patch and submitted review
request at:
https://reviews.facebook.net/D5763
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt, HIVE-1977.5.patch.txt,
> HIVE-1977.6.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-1977:
---
Attachment: HIVE-1977.6.patch.txt
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt, HIVE-1977.5.patch.txt,
> HIVE-1977.6.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-1977:
---
Status: Patch Available (was: Open)
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt, HIVE-1977.5.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-1977:
---
Status: Open (was: Patch Available)
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt, HIVE-1977.5.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471160#comment-13471160
]
Zhenxiao Luo commented on HIVE-1977:
testcase failure fixed in last patch. Also fix a comment error.
New review request submitted at:
https://reviews.facebook.net/D5763
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt, HIVE-1977.5.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-1977:
---
Attachment: HIVE-1977.5.patch.txt
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt, HIVE-1977.5.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2228) Can't use DB qualified column names in WHERE or GROUP BY clauses
[
https://issues.apache.org/jira/browse/HIVE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470919#comment-13470919
]
Zhenxiao Luo commented on HIVE-2228:
@Namit: Thanks for the comment.
You are correct, none of the other clauses working: SORT BY, ORDER BY, CLUSTER
BY, and DISTRIBUTE BY.
I filed HIVE-3542 and link with this ticket.
> Can't use DB qualified column names in WHERE or GROUP BY clauses
>
>
> Key: HIVE-2228
> URL: https://issues.apache.org/jira/browse/HIVE-2228
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-2228.1.patch.txt
>
>
> Hive doesn't allow you to use DB qualified column names in the WHERE or GROUP
> BY clauses. The workaround is to define a table alias:
> {noformat}
> hive> CREATE DATABASE db1;
> OK
> hive> CREATE TABLE db1.t(a INT, b INT);
> OK
> hive> SELECT * FROM db1.t WHERE db1.t.a > 100;
> FAILED: Error in semantic analysis: Line 1:26 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t WHERE t.a > 100;
> OK
> hive> SELECT * FROM db1.t GROUP BY db1.t.a;
> FAILED: Error in semantic analysis: Line 1:29 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t GROUP BY t.a;
> OK
> {noformat}
--
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-3542) Can not use DB Qualified Name in Order By, Sort By, Distribute By, and Cluster By
Zhenxiao Luo created HIVE-3542: -- Summary: Can not use DB Qualified Name in Order By, Sort By, Distribute By, and Cluster By Key: HIVE-3542 URL: https://issues.apache.org/jira/browse/HIVE-3542 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.9.0 Reporter: Zhenxiao Luo Assignee: Zhenxiao Luo Fix For: 0.10.0 CREATE DATABASE db1; CREATE TABLE db1.t(a INT, b INT); SELECT * FROM db1.t ORDER BY db1.t.a; FAILED: SemanticException [Error 10004]: Line 3:29 Invalid table alias or column reference 'db1': (possible column names are: a, b) SELECT * FROM db1.t SORT BY db1.t.a; FAILED: SemanticException [Error 10004]: Line 3:28 Invalid table alias or column reference 'db1': (possible column names are: a, b) SELECT * FROM db1.t CLUSTER BY db1.t.a; FAILED: SemanticException [Error 10004]: Line 3:31 Invalid table alias or column reference 'db1': (possible column names are: a, b) SELECT * FROM db1.t DISTRIBUTE BY db1.t.a; FAILED: SemanticException [Error 10004]: Line 3:34 Invalid table alias or column reference 'db1': (possible column names are: a, b) alias is working OK: SELECT * FROM db1.t t ORDER BY t.a; OK SELECT * FROM db1.t t SORT BY t.a; OK SELECT * FROM db1.t t CLUSTER BY t.a; OK SELECT * FROM db1.t t DISTRIBUTE BY t.a; OK -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-1977:
---
Attachment: HIVE-1977.4.patch.txt
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-1977:
---
Status: Patch Available (was: Open)
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1977) DESCRIBE TABLE syntax doesn't support specifying a database qualified table name
[
https://issues.apache.org/jira/browse/HIVE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470911#comment-13470911
]
Zhenxiao Luo commented on HIVE-1977:
Comments addressed and review request submitted at:
https://reviews.facebook.net/D5763
> DESCRIBE TABLE syntax doesn't support specifying a database qualified table
> name
>
>
> Key: HIVE-1977
> URL: https://issues.apache.org/jira/browse/HIVE-1977
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-1977.1.patch.txt, HIVE-1977.2.patch.txt,
> HIVE-1977.3.patch.txt, HIVE-1977.4.patch.txt
>
>
> The syntax for DESCRIBE is broken. It should be:
> {code}
> DESCRIBE [EXTENDED] [database DOT]table [column]
> {code}
> but is actually
> {code}
> DESCRIBE [EXTENDED] table[DOT col_name]
> {code}
> Ref: http://dev.mysql.com/doc/refman/5.0/en/describe.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2228) Can't use DB qualified column names in WHERE or GROUP BY clauses
[
https://issues.apache.org/jira/browse/HIVE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-2228:
---
Status: Patch Available (was: Open)
> Can't use DB qualified column names in WHERE or GROUP BY clauses
>
>
> Key: HIVE-2228
> URL: https://issues.apache.org/jira/browse/HIVE-2228
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-2228.1.patch.txt
>
>
> Hive doesn't allow you to use DB qualified column names in the WHERE or GROUP
> BY clauses. The workaround is to define a table alias:
> {noformat}
> hive> CREATE DATABASE db1;
> OK
> hive> CREATE TABLE db1.t(a INT, b INT);
> OK
> hive> SELECT * FROM db1.t WHERE db1.t.a > 100;
> FAILED: Error in semantic analysis: Line 1:26 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t WHERE t.a > 100;
> OK
> hive> SELECT * FROM db1.t GROUP BY db1.t.a;
> FAILED: Error in semantic analysis: Line 1:29 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t GROUP BY t.a;
> OK
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2228) Can't use DB qualified column names in WHERE or GROUP BY clauses
[
https://issues.apache.org/jira/browse/HIVE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470002#comment-13470002
]
Zhenxiao Luo commented on HIVE-2228:
propose to add dbName into ColumnInfo. The logic is mainly in
TypeCheckProcFactory. While, lots of updates in TestParse.
Review Request submitted at:
https://reviews.facebook.net/D5913
> Can't use DB qualified column names in WHERE or GROUP BY clauses
>
>
> Key: HIVE-2228
> URL: https://issues.apache.org/jira/browse/HIVE-2228
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-2228.1.patch.txt
>
>
> Hive doesn't allow you to use DB qualified column names in the WHERE or GROUP
> BY clauses. The workaround is to define a table alias:
> {noformat}
> hive> CREATE DATABASE db1;
> OK
> hive> CREATE TABLE db1.t(a INT, b INT);
> OK
> hive> SELECT * FROM db1.t WHERE db1.t.a > 100;
> FAILED: Error in semantic analysis: Line 1:26 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t WHERE t.a > 100;
> OK
> hive> SELECT * FROM db1.t GROUP BY db1.t.a;
> FAILED: Error in semantic analysis: Line 1:29 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t GROUP BY t.a;
> OK
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2228) Can't use DB qualified column names in WHERE or GROUP BY clauses
[
https://issues.apache.org/jira/browse/HIVE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-2228:
---
Attachment: HIVE-2228.1.patch.txt
> Can't use DB qualified column names in WHERE or GROUP BY clauses
>
>
> Key: HIVE-2228
> URL: https://issues.apache.org/jira/browse/HIVE-2228
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema, Query Processor, SQL
>Affects Versions: 0.7.0
>Reporter: Carl Steinbach
>Assignee: Zhenxiao Luo
> Attachments: HIVE-2228.1.patch.txt
>
>
> Hive doesn't allow you to use DB qualified column names in the WHERE or GROUP
> BY clauses. The workaround is to define a table alias:
> {noformat}
> hive> CREATE DATABASE db1;
> OK
> hive> CREATE TABLE db1.t(a INT, b INT);
> OK
> hive> SELECT * FROM db1.t WHERE db1.t.a > 100;
> FAILED: Error in semantic analysis: Line 1:26 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t WHERE t.a > 100;
> OK
> hive> SELECT * FROM db1.t GROUP BY db1.t.a;
> FAILED: Error in semantic analysis: Line 1:29 Invalid table alias or column
> reference 'db1'
> hive> SELECT * FROM db1.t t GROUP BY t.a;
> OK
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3535) derby metastore upgrade script throw errors when updating from 0.7 to 0.8
[
https://issues.apache.org/jira/browse/HIVE-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenxiao Luo updated HIVE-3535:
---
Status: Patch Available (was: Open)
> derby metastore upgrade script throw errors when updating from 0.7 to 0.8
> -
>
> Key: HIVE-3535
> URL: https://issues.apache.org/jira/browse/HIVE-3535
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 0.9.0
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Fix For: 0.10.0
>
> Attachments: HIVE-3535.1.patch.txt
>
>
> $DERBY_HOME/bin/ij upgrade.sql
> ij version 10.4
> ij> CONNECT 'jdbc:derby:/var/lib/hive/metastore/metastore_db';
> ij> RUN
> '/usr/lib/hive/scripts/metastore/upgrade/derby/upgrade-0.7.0-to-0.8.0.derby.sql';
> ij> -- Upgrade MetaStore schema from 0.7.0 to 0.8.0
> RUN '008-HIVE-2246.derby.sql';
> ij> /*
> * Creates the following tables:
> * - CDS
> * - COLUMNS_V2
> * The new columns table is called COLUMNS_V2
> * because many columns are removed, and the schema is changed.
> * It'd take too long to migrate and keep the same table.
> */
> CREATE TABLE "CDS" (
> "CD_ID" bigint NOT NULL,
> PRIMARY KEY ("CD_ID")
> );
> 0 rows inserted/updated/deleted
> ij> CREATE TABLE "COLUMNS_V2" (
> "CD_ID" bigint NOT NULL,
> "COMMENT" varchar(4000),
> "COLUMN_NAME" varchar(128) NOT NULL,
> "TYPE_NAME" varchar(4000),
> "INTEGER_IDX" INTEGER NOT NULL,
> PRIMARY KEY ("CD_ID", "COLUMN_NAME")
> );
> 0 rows inserted/updated/deleted
> ij> ALTER TABLE "COLUMNS_V2"
> ADD CONSTRAINT "COLUMNS_V2_FK1"
> FOREIGN KEY ("CD_ID") REFERENCES "CDS" ("CD_ID")
> ON DELETE NO ACTION ON UPDATE NO ACTION
> ;
> 0 rows inserted/updated/deleted
> ij> /* Alter the SDS table to:
> * - add the column CD_ID
> * - add a foreign key on CD_ID
> * - create an index on CD_ID
> */
> ALTER TABLE SDS
> ADD COLUMN "CD_ID" bigint
> ;
> 0 rows inserted/updated/deleted
> ij> ALTER TABLE SDS
> ADD CONSTRAINT "SDS_FK2"
> FOREIGN KEY ("CD_ID") REFERENCES "CDS" ("CD_ID")
> ;
> 0 rows inserted/updated/deleted
> ij> /*
> * Migrate the TBLS table
> * Add entries into CDS.
> * Populate the CD_ID field in SDS for tables
> * Add entires to COLUMNS_V2 based on this table's sd's columns
> */
> /* In the migration, there is a 1:1 mapping between CD_ID and SD_ID
> * for tables. For speed, just let CD_ID = SD_ID for tables
> */
> INSERT INTO CDS (CD_ID)
> SELECT t.SD_ID FROM TBLS t WHERE t.SD_ID IS NOT NULL ORDER BY t.SD_ID;
> ERROR 42X01: Syntax error: Encountered "ORDER" at line 13, column 54.
> ij> UPDATE SDS
> SET CD_ID = SD_ID
> WHERE SD_ID in
> (SELECT t.SD_ID FROM TBLS t WHERE t.SD_ID IS NOT NULL ORDER BY t.SD_ID);
> ERROR 42X01: Syntax error: Encountered "ORDER" at line 4, column 55.
> ij> INSERT INTO COLUMNS_V2
> (CD_ID, COMMENT, COLUMN_NAME, TYPE_NAME, INTEGER_IDX)
> SELECT
> c.SD_ID, c.COMMENT, c.COLUMN_NAME, c.TYPE_NAME, c.INTEGER_IDX
> FROM
> COLUMNS c
> JOIN
> TBLS t
> ON
> t.SD_ID = c.SD_ID
> ;
> ERROR 23503: INSERT on table 'COLUMNS_V2' caused a violation of foreign key
> constraint 'COLUMNS_V2_FK1' for key (1). The statement has been rolled back.
> ij> /*
> * Migrate the partitions.
> * Update the partitions' SDS to use the parent tables' CD_ID BEGIN
> * Derby does not allow joins in update statements,
> * so we have to make a temporary tableh
> */
> DECLARE GLOBAL TEMPORARY TABLE "TMP_TBL" (
> "SD_ID" bigint not null,
> "CD_ID" bigint not null
> ) ON COMMIT PRESERVE ROWS NOT LOGGED;
> 0 rows inserted/updated/deleted
> ij> INSERT INTO "SESSION"."TMP_TBL" SELECT
> p.SD_ID, sds.CD_ID
> FROM PARTITIONS p
> JOIN TBLS t ON t.TBL_ID = p.TBL_ID
> JOIN SDS sds on t.SD_ID = sds.SD_ID
> WHERE p.SD_ID IS NOT NULL;
> ERROR 23502: Column 'CD_ID' cannot accept a NULL value.
> ij> UPDATE SDS sd
> SET sd.CD_ID =
> (SELECT tt.CD_ID FROM SESSION.TMP_TBL tt WHERE tt.SD_ID = sd.SD_ID)
> WHERE sd.SD_ID IN (SELECT SD_ID FROM SESSION.TMP_TBL);
> 0 rows inserted/updated/deleted
> WARNING 02000: No row was found for FETCH, UPDATE or DELETE; or the result of
> a query is an empty table.
> ij> /*
> * Migrate IDXS
> */
> INSERT INTO CDS (CD_ID)
> SELECT i.SD_ID FROM IDXS i WHERE i.SD_ID IS NOT NULL ORDER BY i.SD_ID;
> ERROR 42X01: Syntax error: Encountered "ORDER" at line 5, column 54.
> ij> UPDATE SDS
> SET CD_ID = SD_ID
> WHERE SD_ID in
> (SELECT i.SD_ID FROM IDXS i WHERE i.SD_ID IS NOT NULL ORDER BY i.SD_ID);
> ERROR 42X01: Syntax error: Encountered "ORDER" at line 4, column 55.
> ij> INSERT INTO COLUMNS_V2
> (CD_ID, COMMENT, COLUMN_NAME, TYPE_NAME, INTEGER_IDX)
> SELECT
> c.SD_ID, c.COMMENT, c.COLUMN_NAME, c.TYPE_NAME, c.INTEGER_IDX
> FROM
> COLUMNS c
> JOIN
> IDXS i
> ON
> i.SD_ID = c.SD_ID
> ;
> ERROR 42X05: Table/
[jira] [Commented] (HIVE-3535) derby metastore upgrade script throw errors when updating from 0.7 to 0.8
[
https://issues.apache.org/jira/browse/HIVE-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469778#comment-13469778
]
Zhenxiao Luo commented on HIVE-3535:
The new upgrade script gets rid of all the errors:
ij> run 'upgrade-0.7.0-to-0.8.0.derby.sql';
ij> – Upgrade MetaStore schema from 0.7.0 to 0.8.0
RUN '008-HIVE-2246.derby.sql';
ij> /*
Creates the following tables:
- CDS
- COLUMNS_V2
The new columns table is called COLUMNS_V2
because many columns are removed, and the schema is changed.
It'd take too long to migrate and keep the same table.
*/
CREATE TABLE "CDS" (
"CD_ID" bigint NOT NULL,
PRIMARY KEY ("CD_ID")
);
0 rows inserted/updated/deleted
ij> CREATE TABLE "COLUMNS_V2" (
"CD_ID" bigint NOT NULL,
"COMMENT" varchar(4000),
"COLUMN_NAME" varchar(128) NOT NULL,
"TYPE_NAME" varchar(4000),
"INTEGER_IDX" INTEGER NOT NULL,
PRIMARY KEY ("CD_ID", "COLUMN_NAME")
);
0 rows inserted/updated/deleted
ij> ALTER TABLE "COLUMNS_V2"
ADD CONSTRAINT "COLUMNS_V2_FK1"
FOREIGN KEY ("CD_ID") REFERENCES "CDS" ("CD_ID")
ON DELETE NO ACTION ON UPDATE NO ACTION
;
0 rows inserted/updated/deleted
ij> /* Alter the SDS table to:
- add the column CD_ID
- add a foreign key on CD_ID
- create an index on CD_ID
*/
ALTER TABLE SDS
ADD COLUMN "CD_ID" bigint
;
0 rows inserted/updated/deleted
ij> ALTER TABLE SDS
ADD CONSTRAINT "SDS_FK2"
FOREIGN KEY ("CD_ID") REFERENCES "CDS" ("CD_ID")
;
0 rows inserted/updated/deleted
ij> /*
Migrate the TBLS table
Add entries into CDS.
Populate the CD_ID field in SDS for tables
Add entires to COLUMNS_V2 based on this table's sd's columns
*/
/* In the migration, there is a 1:1 mapping between CD_ID and SD_ID
for tables. For speed, just let CD_ID = SD_ID for tables
*/
INSERT INTO CDS (CD_ID)
SELECT t.SD_ID FROM TBLS t WHERE t.SD_ID IS NOT NULL;
1 row inserted/updated/deleted
ij> UPDATE SDS
SET CD_ID = SD_ID
WHERE SD_ID in
(SELECT t.SD_ID FROM TBLS t WHERE t.SD_ID IS NOT NULL);
1 row inserted/updated/deleted
ij> INSERT INTO COLUMNS_V2
(CD_ID, COMMENT, COLUMN_NAME, TYPE_NAME, INTEGER_IDX)
SELECT
c.SD_ID, c.COMMENT, c.COLUMN_NAME, c.TYPE_NAME, c.INTEGER_IDX
FROM
COLUMNS c
JOIN
TBLS t
ON
t.SD_ID = c.SD_ID
;
2 rows inserted/updated/deleted
ij> /*
Migrate the partitions.
Update the partitions' SDS to use the parent tables' CD_ID BEGIN
Derby does not allow joins in update statements,
so we have to make a temporary tableh
*/
DECLARE GLOBAL TEMPORARY TABLE "TMP_TBL" (
"SD_ID" bigint not null,
"CD_ID" bigint not null
) ON COMMIT PRESERVE ROWS NOT LOGGED;
0 rows inserted/updated/deleted
ij> INSERT INTO "SESSION"."TMP_TBL" SELECT
p.SD_ID, sds.CD_ID
FROM PARTITIONS p
JOIN TBLS t ON t.TBL_ID = p.TBL_ID
JOIN SDS sds on t.SD_ID = sds.SD_ID
WHERE p.SD_ID IS NOT NULL AND sds.CD_ID IS NOT NULL;
0 rows inserted/updated/deleted
ij> UPDATE SDS sd
SET sd.CD_ID =
(SELECT tt.CD_ID FROM SESSION.TMP_TBL tt WHERE tt.SD_ID = sd.SD_ID)
WHERE sd.SD_ID IN (SELECT SD_ID FROM SESSION.TMP_TBL);
0 rows inserted/updated/deleted
WARNING 02000: No row was found for FETCH, UPDATE or DELETE; or the result of a
query is an empty table.
ij> /*
Migrate IDXS
*/
INSERT INTO CDS (CD_ID)
SELECT i.SD_ID FROM IDXS i WHERE i.SD_ID IS NOT NULL;
0 rows inserted/updated/deleted
ij> UPDATE SDS
SET CD_ID = SD_ID
WHERE SD_ID in
(SELECT i.SD_ID FROM IDXS i WHERE i.SD_ID IS NOT NULL);
0 rows inserted/updated/deleted
WARNING 02000: No row was found for FETCH, UPDATE or DELETE; or the result of a
query is an empty table.
ij> INSERT INTO COLUMNS_V2
(CD_ID, COMMENT, COLUMN_NAME, TYPE_NAME, INTEGER_IDX)
SELECT
c.SD_ID, c.COMMENT, c.COLUMN_NAME, c.TYPE_NAME, c.INTEGER_IDX
FROM
COLUMNS c
JOIN
IDXS i
ON
i.SD_ID = c.SD_ID
;
0 rows inserted/updated/deleted
ij> /*
rename the old COLUMNS table
*/
RENAME TABLE COLUMNS TO COLUMNS_OLD;
0 rows inserted/updated/deleted
ij> RUN '009-HIVE-2215.derby.sql';
ij> – Table PARTITION_EVENTS for classes
[org.apache.hadoop.hive.metastore.model.MPartitionEvent]
CREATE TABLE PARTITION_EVENTS
(
PART_NAME_ID BIGINT NOT NULL,
DB_NAME VARCHAR(128),
EVENT_TIME BIGINT NOT NULL,
EVENT_TYPE INTEGER NOT NULL,
PARTITION_NAME VARCHAR(767),
TBL_NAME VARCHAR(128)
);
0 rows inserted/updated/deleted
ij> ALTER TABLE PARTITION_EVENTS ADD CONSTRAINT PARTITION_EVENTS_PK PRIMARY KEY
(PART_NAME_ID);
0 rows inserted/updated/deleted
ij>
> derby metastore upgrade script throw errors when updating from 0.7 to 0.8
> -
>
> Key: HIVE-3535
> URL: https://issues.apache.org/jira/browse/HIVE-3535
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 0.9.0
>Reporter: Zhenxiao Luo
>Assignee: Zhenxiao Luo
> Fix For: 0.10.0
>
> Attachments: HIVE-3535.1.patch.txt
>
>
> $DERBY_HOME/bin/ij upgrade.sql
> ij version 10.4
> ij> CONNECT 'jdbc:derby:/var/lib/hive/metasto
