[jira] [Commented] (HIVE-1095) Hive in Maven
[ https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032842#comment-13032842 ] jirapos...@reviews.apache.org commented on HIVE-1095: - --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/740/ --- Review request for hive and Carl Steinbach. Summary --- This addresses bug HIVE-1095. https://issues.apache.org/jira/browse/HIVE-1095 Diffs - trunk/LICENSE-2.0.txt PRE-CREATION trunk/ant/ivy.xml 1095392 trunk/build-common.xml 1095392 trunk/build.xml 1095392 trunk/cli/ivy.xml 1095392 trunk/common/ivy.xml 1095392 trunk/contrib/ivy.xml 1095392 trunk/hbase-handler/ivy.xml 1095392 trunk/hwi/ivy.xml 1095392 trunk/ivy.xml 1095392 trunk/jdbc/ivy.xml PRE-CREATION trunk/metastore/ivy.xml 1095392 trunk/ql/ivy.xml 1095392 trunk/serde/ivy.xml 1095392 trunk/service/ivy.xml PRE-CREATION trunk/shims/ivy.xml 1095392 Diff: https://reviews.apache.org/r/740/diff Testing --- Thanks, Amareshwari Hive in Maven - Key: HIVE-1095 URL: https://issues.apache.org/jira/browse/HIVE-1095 Project: Hive Issue Type: Task Components: Build Infrastructure Affects Versions: 0.6.0 Reporter: Gerrit Jansen van Vuuren Priority: Minor Fix For: 0.7.1 Attachments: HIVE-1095-trunk.patch, HIVE-1095.v2.PATCH, HIVE-1095.v3.PATCH, HIVE-1095.v4.PATCH, HIVE-1095.v5.PATCH, HIVE-1095.v6.patch, hiveReleasedToMaven.tar.gz, make-maven.log Getting hive into maven main repositories Documentation on how to do this is on: http://maven.apache.org/guides/mini/guide-central-repository-upload.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Review Request: HIVE-1095 Hive in maven
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/740/ --- Review request for hive and Carl Steinbach. Summary --- This addresses bug HIVE-1095. https://issues.apache.org/jira/browse/HIVE-1095 Diffs - trunk/LICENSE-2.0.txt PRE-CREATION trunk/ant/ivy.xml 1095392 trunk/build-common.xml 1095392 trunk/build.xml 1095392 trunk/cli/ivy.xml 1095392 trunk/common/ivy.xml 1095392 trunk/contrib/ivy.xml 1095392 trunk/hbase-handler/ivy.xml 1095392 trunk/hwi/ivy.xml 1095392 trunk/ivy.xml 1095392 trunk/jdbc/ivy.xml PRE-CREATION trunk/metastore/ivy.xml 1095392 trunk/ql/ivy.xml 1095392 trunk/serde/ivy.xml 1095392 trunk/service/ivy.xml PRE-CREATION trunk/shims/ivy.xml 1095392 Diff: https://reviews.apache.org/r/740/diff Testing --- Thanks, Amareshwari
Re: Hive partioning
Partition correspond to one folder under the table folder on HDFS, that means you only need to scan the partition folder rather than the whole table folder when you specify the partition in sql. On Thu, May 12, 2011 at 6:20 PM, Pulkit Agrawal pulkit.agra...@ngicorporation.com wrote: Hi , Can you please explain what is partitioning in hive? I am newbie for hive. Thanks in advance. Regards, Pulkit Agrawal -- Best Regards Jeff Zhang
[jira] [Commented] (HIVE-2163) SquirrelSQL 3.2.1 doesn't work with Hive 0.7.0
[
https://issues.apache.org/jira/browse/HIVE-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032846#comment-13032846
]
Todd Lipcon commented on HIVE-2163:
---
Any idea of the root cause of this? Is SquirrelSQL doing something funky with
the thread's context classloader by any chance?
SquirrelSQL 3.2.1 doesn't work with Hive 0.7.0
--
Key: HIVE-2163
URL: https://issues.apache.org/jira/browse/HIVE-2163
Project: Hive
Issue Type: Bug
Components: JDBC
Affects Versions: 0.7.0
Reporter: Carl Steinbach
I tried using SquirrelSQL 3.2.1 with Hive 0.7.0 following the directions
located here: http://wiki.apache.org/hadoop/Hive/HiveJDBCInterface
I registered the Hive JDBC driver with SquirrelSQL, and then get the
following exception when I try to connect to the Hive Server process:
{noformat}
java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException:
java.lang.RuntimeException: java.io.IOException: failure to login
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:226)
at org.apache.hadoop.hive.jdbc.HiveConnection.init(HiveConnection.java:72)
at org.apache.hadoop.hive.jdbc.HiveDriver.connect(HiveDriver.java:110)
at
net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133)
at
net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.execute(OpenConnectionCommand.java:97)
at
net.sourceforge.squirrel_sql.client.mainframe.action.ConnectToAliasCommand$SheetHandler.run(ConnectToAliasCommand.java:281)
at
net.sourceforge.squirrel_sql.client.mainframe.action.ConnectToAliasCommand$SheetHandler.performOK(ConnectToAliasCommand.java:238)
at
net.sourceforge.squirrel_sql.client.gui.db.ConnectionInternalFrame.connect(ConnectionInternalFrame.java:311)
at
net.sourceforge.squirrel_sql.client.gui.db.ConnectionInternalFrame.access$300(ConnectionInternalFrame.java:56)
at
net.sourceforge.squirrel_sql.client.gui.db.ConnectionInternalFrame$MyOkClosePanelListener.okPressed(ConnectionInternalFrame.java:461)
at
net.sourceforge.squirrel_sql.client.gui.OkClosePanel.fireButtonPressed(OkClosePanel.java:148)
at
net.sourceforge.squirrel_sql.client.gui.OkClosePanel.access$100(OkClosePanel.java:33)
at
net.sourceforge.squirrel_sql.client.gui.OkClosePanel$1.actionPerformed(OkClosePanel.java:174)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2028)
at
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2351)
at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:6374)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6139)
at java.awt.Container.processEvent(Container.java:2085)
at java.awt.Component.dispatchEventImpl(Component.java:4736)
at java.awt.Container.dispatchEventImpl(Container.java:2143)
at java.awt.Component.dispatchEvent(Component.java:4566)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4621)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4282)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4212)
at java.awt.Container.dispatchEventImpl(Container.java:2129)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4566)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:680)
at java.awt.EventQueue.access$000(EventQueue.java:86)
at java.awt.EventQueue$1.run(EventQueue.java:639)
at java.awt.EventQueue$1.run(EventQueue.java:637)
at java.security.AccessController.doPrivileged(Native Method)
at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
at java.awt.EventQueue$2.run(EventQueue.java:653)
at java.awt.EventQueue$2.run(EventQueue.java:651)
at java.security.AccessController.doPrivileged(Native Method)
at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:650)
at net.sourceforge.squirrel_sql.client.Main$1.dispatchEvent(Main.java:93)
at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201)
at
[jira] [Commented] (HIVE-2160) Few code improvements in the metastore,hwi and ql packages.
[ https://issues.apache.org/jira/browse/HIVE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032966#comment-13032966 ] jirapos...@reviews.apache.org commented on HIVE-2160: - --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/742/ --- Review request for hive. Summary --- Few code improvements in the metastore,hwi and ql packages. 1) Little performance Improvements 2) Effective varaible management. This addresses bug HIVE-2160. https://issues.apache.org/jira/browse/HIVE-2160 Diffs - http://svn.apache.org/repos/asf/hive/trunk/hwi/src/java/org/apache/hadoop/hive/hwi/HWISessionItem.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/ColumnPrunerProcFactory.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMRUnion1.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/MapJoinProcessor.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/unionproc/UnionProcessor.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/FetchWork.java 1101752 Diff: https://reviews.apache.org/r/742/diff Testing --- Ran all tests Thanks, chinna Few code improvements in the metastore,hwi and ql packages. --- Key: HIVE-2160 URL: https://issues.apache.org/jira/browse/HIVE-2160 Project: Hive Issue Type: Bug Components: Metastore, Query Processor, Web UI Affects Versions: 0.8.0 Environment: Hadoop 0.20.1, Hive0.8.0 and SUSE Linux Enterprise Server 10 SP2 (i586) - Kernel 2.6.16.60-0.21-smp (5). Reporter: Chinna Rao Lalam Assignee: Chinna Rao Lalam Attachments: HIVE-2160.Patch Few code improvements in the metastore,hwi and ql packages. 1) Little performance Improvements 2) Effective varaible management. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2160) Few code improvements in the metastore,hwi and ql packages.
[ https://issues.apache.org/jira/browse/HIVE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13033100#comment-13033100 ] jirapos...@reviews.apache.org commented on HIVE-2160: - --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/742/#review667 --- Ship it! Thanks Chinna for the cleanup work. Looks good to me. - Ashutosh On 2011-05-13 11:07:56, chinna wrote: bq. bq. --- bq. This is an automatically generated e-mail. To reply, visit: bq. https://reviews.apache.org/r/742/ bq. --- bq. bq. (Updated 2011-05-13 11:07:56) bq. bq. bq. Review request for hive. bq. bq. bq. Summary bq. --- bq. bq. Few code improvements in the metastore,hwi and ql packages. bq. 1) Little performance Improvements bq. 2) Effective varaible management. bq. bq. bq. This addresses bug HIVE-2160. bq. https://issues.apache.org/jira/browse/HIVE-2160 bq. bq. bq. Diffs bq. - bq. bq. http://svn.apache.org/repos/asf/hive/trunk/hwi/src/java/org/apache/hadoop/hive/hwi/HWISessionItem.java 1101752 bq. http://svn.apache.org/repos/asf/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java 1101752 bq. http://svn.apache.org/repos/asf/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java 1101752 bq. http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/ColumnPrunerProcFactory.java 1101752 bq. http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMRUnion1.java 1101752 bq. http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/MapJoinProcessor.java 1101752 bq. http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/unionproc/UnionProcessor.java 1101752 bq. http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/FetchWork.java 1101752 bq. bq. Diff: https://reviews.apache.org/r/742/diff bq. bq. bq. Testing bq. --- bq. bq. Ran all tests bq. bq. bq. Thanks, bq. bq. chinna bq. bq. Few code improvements in the metastore,hwi and ql packages. --- Key: HIVE-2160 URL: https://issues.apache.org/jira/browse/HIVE-2160 Project: Hive Issue Type: Bug Components: Metastore, Query Processor, Web UI Affects Versions: 0.8.0 Environment: Hadoop 0.20.1, Hive0.8.0 and SUSE Linux Enterprise Server 10 SP2 (i586) - Kernel 2.6.16.60-0.21-smp (5). Reporter: Chinna Rao Lalam Assignee: Chinna Rao Lalam Attachments: HIVE-2160.Patch Few code improvements in the metastore,hwi and ql packages. 1) Little performance Improvements 2) Effective varaible management. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Review Request: HIVE-2160 : Few code improvements in the metastore, hwi and ql packages.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/742/#review667 --- Ship it! Thanks Chinna for the cleanup work. Looks good to me. - Ashutosh On 2011-05-13 11:07:56, chinna wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/742/ --- (Updated 2011-05-13 11:07:56) Review request for hive. Summary --- Few code improvements in the metastore,hwi and ql packages. 1) Little performance Improvements 2) Effective varaible management. This addresses bug HIVE-2160. https://issues.apache.org/jira/browse/HIVE-2160 Diffs - http://svn.apache.org/repos/asf/hive/trunk/hwi/src/java/org/apache/hadoop/hive/hwi/HWISessionItem.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/HiveMetaStore.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/ObjectStore.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/ColumnPrunerProcFactory.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMRUnion1.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/MapJoinProcessor.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/unionproc/UnionProcessor.java 1101752 http://svn.apache.org/repos/asf/hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/FetchWork.java 1101752 Diff: https://reviews.apache.org/r/742/diff Testing --- Ran all tests Thanks, chinna
[jira] [Commented] (HIVE-2162) Upgrade dependencies to Hadoop 0.20.2 and 0.20.203.0
[ https://issues.apache.org/jira/browse/HIVE-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13033107#comment-13033107 ] John Sichi commented on HIVE-2162: -- @Owen: Probably at the time we started doing this, the Maven jars weren't available yet (and Hive wasn't using ivy yet). We may also be depending on some stuff outside of the jars such as conf files and scripts. But it's definitely the case that the tarball contains way more than we need. Upgrade dependencies to Hadoop 0.20.2 and 0.20.203.0 Key: HIVE-2162 URL: https://issues.apache.org/jira/browse/HIVE-2162 Project: Hive Issue Type: Improvement Reporter: Owen O'Malley Hadoop has released 0.20.203.0 and we should upgrade Hive's dependency to it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2164) comments are not handled correctly
comments are not handled correctly -- Key: HIVE-2164 URL: https://issues.apache.org/jira/browse/HIVE-2164 Project: Hive Issue Type: Bug Reporter: Ning Zhang One example is hive -- comments; FAILED: Parse Error: line 0:-1 cannot recognize input 'EOF' Also we need to handle comments correctly in all unit tests (.q files). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Review Request: HIVE-2155 Improve error messages emitted during semantic analysis
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/731/#review669 --- ql/src/test/results/clientnegative/create_view_failure3.q.out https://reviews.apache.org/r/731/#comment1333 This is an example where an existing error should have been using the new Error encountered You can either take care of these now, or open a followup for that. ql/src/test/results/clientnegative/ddltime.q.out https://reviews.apache.org/r/731/#comment1332 Need a period before Error encountered That's true in general;. ql/src/test/results/clientnegative/groupby_key.q.out https://reviews.apache.org/r/731/#comment1331 This is kinda ugly... - John On 2011-05-12 23:44:48, Syed Albiz wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/731/ --- (Updated 2011-05-12 23:44:48) Review request for hive and John Sichi. Summary --- Attaches line/column number to the vast majority of SemanticExceptions thrown. In addition, the context strings for the error messages relating to UNION ALLs and GROUP BY keys have been changed to provide more meaningful context. This addresses bug HIVE-2155. https://issues.apache.org/jira/browse/HIVE-2155 Diffs - common/src/java/org/apache/hadoop/hive/conf/HiveConf.java dc96a1f ql/src/java/org/apache/hadoop/hive/ql/parse/BaseSemanticAnalyzer.java 2fe37b6 ql/src/java/org/apache/hadoop/hive/ql/parse/ErrorMsg.java 4ddf5b9 ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 9cb407c ql/src/java/org/apache/hadoop/hive/ql/parse/TypeCheckProcFactory.java bca37fd ql/src/test/queries/clientnegative/union3.q PRE-CREATION ql/src/test/results/clientnegative/analyze_view.q.out ef76106 ql/src/test/results/clientnegative/clusterbydistributeby.q.out 4c1ebfb ql/src/test/results/clientnegative/clusterbysortby.q.out f76d4a7 ql/src/test/results/clientnegative/clustern3.q.out da71016 ql/src/test/results/clientnegative/clustern4.q.out 1519e48 ql/src/test/results/clientnegative/create_view_failure3.q.out 70e365a ql/src/test/results/clientnegative/ddltime.q.out 11d00c3 ql/src/test/results/clientnegative/drop_partition_failure.q.out 1a0ac10 ql/src/test/results/clientnegative/dyn_part2.q.out cc0cd3c ql/src/test/results/clientnegative/fileformat_void_input.q.out 5a7a05a ql/src/test/results/clientnegative/groupby_key.q.out c6218a4 ql/src/test/results/clientnegative/input1.q.out 73f1657 ql/src/test/results/clientnegative/input2.q.out 0c460a6 ql/src/test/results/clientnegative/invalidate_view1.q.out 9f61228 ql/src/test/results/clientnegative/joinneg.q.out d85d508 ql/src/test/results/clientnegative/line_terminator.q.out b672bd8 ql/src/test/results/clientnegative/load_wrong_noof_part.q.out 4d8c8d8 ql/src/test/results/clientnegative/nopart_insert.q.out 42bca76 ql/src/test/results/clientnegative/notable_alias3.q.out d48d5e1 ql/src/test/results/clientnegative/orderbysortby.q.out 73b83a4 ql/src/test/results/clientnegative/regex_col_1.q.out 7547858 ql/src/test/results/clientnegative/regex_col_2.q.out f570010 ql/src/test/results/clientnegative/regex_col_groupby.q.out 8497718 ql/src/test/results/clientnegative/semijoin1.q.out 739931f ql/src/test/results/clientnegative/semijoin2.q.out 2b418de ql/src/test/results/clientnegative/semijoin3.q.out a803b50 ql/src/test/results/clientnegative/semijoin4.q.out 86a834b ql/src/test/results/clientnegative/split_sample_out_of_range.q.out 0761955 ql/src/test/results/clientnegative/split_sample_wrong_format.q.out 19b1417 ql/src/test/results/clientnegative/strict_orderby.q.out 2d3ba6b ql/src/test/results/clientnegative/subq_insert.q.out 8c3ce79 ql/src/test/results/clientnegative/udf_array_contains_wrong1.q.out d6b98b4 ql/src/test/results/clientnegative/udf_array_contains_wrong2.q.out 7b8dca6 ql/src/test/results/clientnegative/udf_case_type_wrong.q.out 75b9638 ql/src/test/results/clientnegative/udf_case_type_wrong2.q.out 126fa4e ql/src/test/results/clientnegative/udf_case_type_wrong3.q.out fd62771 ql/src/test/results/clientnegative/udf_coalesce.q.out a5279f5 ql/src/test/results/clientnegative/udf_elt_wrong_args_len.q.out 22a085a ql/src/test/results/clientnegative/udf_elt_wrong_type.q.out fc83f23 ql/src/test/results/clientnegative/udf_field_wrong_args_len.q.out 3bf97d9 ql/src/test/results/clientnegative/udf_field_wrong_type.q.out 2a2e944 ql/src/test/results/clientnegative/udf_if_not_bool.q.out a3c8902 ql/src/test/results/clientnegative/udf_if_wrong_args_len.q.out 89b23c8
[jira] [Commented] (HIVE-2155) Improve error messages emitted during semantic analysis
[ https://issues.apache.org/jira/browse/HIVE-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13033167#comment-13033167 ] John Sichi commented on HIVE-2155: -- Added a few comments in review board. Improve error messages emitted during semantic analysis --- Key: HIVE-2155 URL: https://issues.apache.org/jira/browse/HIVE-2155 Project: Hive Issue Type: Improvement Reporter: Syed S. Albiz Assignee: Syed S. Albiz Attachments: HIVE-2155.1.patch, HIVE-2155.2.patch, HIVE-2155.3.patch Follow-up to HIVE-1731. A number of issues raised in HIVE-1731 were caused by SemanticAnalyzer not reporting errors correctly. Specifically, the following issues need to be addressed: - Line numbers are not always provided and sometimes emitted as (0:-1), which is useless - Insufficient or unclear context strings are provided Specific issues described in HIVE-1731: FAILED: Error in semantic analysis: Schema of both sides of union should match: destinationid:_col1 _col2 * No line/col numbers, context strings provide internal aliases instead of actual column names FAILED: Error in semantic analysis: line 0:-1 Both Left and Right Aliases Encountered in Join time * Incorrect line/col number info, no context strings to describe the aliases encountered FAILED: Error in semantic analysis: AS clause has an invalid number of aliases * No line/col numbers, not context string to show the aliases encountered FAILED: Error in semantic analysis: line 1:94 Expression Not In Group By Key a * testcase: SELECT a.id, VAR(a.cnt) FROM mytable a * Context string is unhelpful, needs to provide the actual expression, not just the table reference -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Build failed in Jenkins: Hive-trunk-h0.20 #727
See https://builds.apache.org/hudson/job/Hive-trunk-h0.20/727/ -- [...truncated 30229 lines...] [junit] OK [junit] PREHOOK: query: select count(1) as cnt from testhivedrivertable [junit] PREHOOK: type: QUERY [junit] PREHOOK: Input: default@testhivedrivertable [junit] PREHOOK: Output: file:/tmp/hudson/hive_2011-05-13_12-37-18_518_2043163679882492163/-mr-1 [junit] Total MapReduce jobs = 1 [junit] Launching Job 1 out of 1 [junit] Number of reduce tasks determined at compile time: 1 [junit] In order to change the average load for a reducer (in bytes): [junit] set hive.exec.reducers.bytes.per.reducer=number [junit] In order to limit the maximum number of reducers: [junit] set hive.exec.reducers.max=number [junit] In order to set a constant number of reducers: [junit] set mapred.reduce.tasks=number [junit] Job running in-process (local Hadoop) [junit] Hadoop job information for null: number of mappers: 0; number of reducers: 0 [junit] 2011-05-13 12:37:21,633 null map = 100%, reduce = 100% [junit] Ended Job = job_local_0001 [junit] POSTHOOK: query: select count(1) as cnt from testhivedrivertable [junit] POSTHOOK: type: QUERY [junit] POSTHOOK: Input: default@testhivedrivertable [junit] POSTHOOK: Output: file:/tmp/hudson/hive_2011-05-13_12-37-18_518_2043163679882492163/-mr-1 [junit] OK [junit] PREHOOK: query: drop table testhivedrivertable [junit] PREHOOK: type: DROPTABLE [junit] PREHOOK: Input: default@testhivedrivertable [junit] PREHOOK: Output: default@testhivedrivertable [junit] POSTHOOK: query: drop table testhivedrivertable [junit] POSTHOOK: type: DROPTABLE [junit] POSTHOOK: Input: default@testhivedrivertable [junit] POSTHOOK: Output: default@testhivedrivertable [junit] OK [junit] Hive history file=https://builds.apache.org/hudson/job/Hive-trunk-h0.20/ws/hive/build/service/tmp/hive_job_log_hudson_201105131237_61248177.txt [junit] PREHOOK: query: drop table testhivedrivertable [junit] PREHOOK: type: DROPTABLE [junit] POSTHOOK: query: drop table testhivedrivertable [junit] POSTHOOK: type: DROPTABLE [junit] OK [junit] PREHOOK: query: create table testhivedrivertable (num int) [junit] PREHOOK: type: CREATETABLE [junit] POSTHOOK: query: create table testhivedrivertable (num int) [junit] POSTHOOK: type: CREATETABLE [junit] POSTHOOK: Output: default@testhivedrivertable [junit] OK [junit] PREHOOK: query: load data local inpath 'https://builds.apache.org/hudson/job/Hive-trunk-h0.20/ws/hive/data/files/kv1.txt' into table testhivedrivertable [junit] PREHOOK: type: LOAD [junit] PREHOOK: Output: default@testhivedrivertable [junit] Copying data from https://builds.apache.org/hudson/job/Hive-trunk-h0.20/ws/hive/data/files/kv1.txt [junit] Loading data to table default.testhivedrivertable [junit] POSTHOOK: query: load data local inpath 'https://builds.apache.org/hudson/job/Hive-trunk-h0.20/ws/hive/data/files/kv1.txt' into table testhivedrivertable [junit] POSTHOOK: type: LOAD [junit] POSTHOOK: Output: default@testhivedrivertable [junit] OK [junit] PREHOOK: query: select * from testhivedrivertable limit 10 [junit] PREHOOK: type: QUERY [junit] PREHOOK: Input: default@testhivedrivertable [junit] PREHOOK: Output: file:/tmp/hudson/hive_2011-05-13_12-37-23_220_4207906368269239878/-mr-1 [junit] POSTHOOK: query: select * from testhivedrivertable limit 10 [junit] POSTHOOK: type: QUERY [junit] POSTHOOK: Input: default@testhivedrivertable [junit] POSTHOOK: Output: file:/tmp/hudson/hive_2011-05-13_12-37-23_220_4207906368269239878/-mr-1 [junit] OK [junit] PREHOOK: query: drop table testhivedrivertable [junit] PREHOOK: type: DROPTABLE [junit] PREHOOK: Input: default@testhivedrivertable [junit] PREHOOK: Output: default@testhivedrivertable [junit] POSTHOOK: query: drop table testhivedrivertable [junit] POSTHOOK: type: DROPTABLE [junit] POSTHOOK: Input: default@testhivedrivertable [junit] POSTHOOK: Output: default@testhivedrivertable [junit] OK [junit] Hive history file=https://builds.apache.org/hudson/job/Hive-trunk-h0.20/ws/hive/build/service/tmp/hive_job_log_hudson_201105131237_1778656147.txt [junit] PREHOOK: query: drop table testhivedrivertable [junit] PREHOOK: type: DROPTABLE [junit] POSTHOOK: query: drop table testhivedrivertable [junit] POSTHOOK: type: DROPTABLE [junit] OK [junit] PREHOOK: query: create table testhivedrivertable (num int) [junit] PREHOOK: type: CREATETABLE [junit] POSTHOOK: query: create table testhivedrivertable (num int) [junit] POSTHOOK: type: CREATETABLE [junit] POSTHOOK: Output: default@testhivedrivertable [junit] OK [junit] PREHOOK: query: drop table testhivedrivertable [junit] PREHOOK: type: DROPTABLE
[jira] [Commented] (HIVE-1694) Accelerate GROUP BY execution using indexes
[ https://issues.apache.org/jira/browse/HIVE-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13033254#comment-13033254 ] John Sichi commented on HIVE-1694: -- Need a rebase now that the refactoring from HIVE-1803 has been committed. Accelerate GROUP BY execution using indexes --- Key: HIVE-1694 URL: https://issues.apache.org/jira/browse/HIVE-1694 Project: Hive Issue Type: New Feature Components: Indexing, Query Processor Affects Versions: 0.7.0 Reporter: Nikhil Deshpande Assignee: Prajakta Kalmegh Attachments: HIVE-1694.1.patch.txt, HIVE-1694.2.patch.txt, HIVE-1694.3.patch.txt, HIVE-1694_2010-10-28.diff, demo_q1.hql, demo_q2.hql The index building patch (Hive-417) is checked into trunk, this JIRA issue tracks supporting indexes in Hive compiler execution engine for SELECT queries. This is in ref. to John's comment at https://issues.apache.org/jira/browse/HIVE-417?focusedCommentId=12884869page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12884869 on creating separate JIRA issue for tracking index usage in optimizer query execution. The aim of this effort is to use indexes to accelerate query execution (for certain class of queries). E.g. - Filters and range scans (already being worked on by He Yongqiang as part of HIVE-417?) - Joins (index based joins) - Group By, Order By and other misc cases The proposal is multi-step: 1. Building index based operators, compiler and execution engine changes 2. Optimizer enhancements (e.g. cost-based optimizer to compare and choose between index scans, full table scans etc.) This JIRA initially focuses on the first step. This JIRA is expected to hold the information about index based plans operator implementations for above mentioned cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2165) variable to be assigned with an atomic value from a query
variable to be assigned with an atomic value from a query
-
Key: HIVE-2165
URL: https://issues.apache.org/jira/browse/HIVE-2165
Project: Hive
Issue Type: Sub-task
Reporter: Ning Zhang
Currently variable can only be assigned by a constant. There are cases where a
query generate a single value that should be used by the second query. It would
be nice to assign this value to a variable and pass it to the second query. For
exmaple:
{code}
hive set x_avg = `select avg(x) from T`;
hive select my_udf(${hiveconf:x_avg}, y) from T2;
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2165) variable to be assigned with an atomic value from a query
[
https://issues.apache.org/jira/browse/HIVE-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13033277#comment-13033277
]
Edward Capriolo commented on HIVE-2165:
---
I was thinking about this. Getting 1 row result is simple enough. We can tap
the the result set as it streamed back to it and store it and provide access
with something like: ${LASTROW}[0]. The question is how many of these type of
features do we need before should tackle a stored procedure like language.
variable to be assigned with an atomic value from a query
-
Key: HIVE-2165
URL: https://issues.apache.org/jira/browse/HIVE-2165
Project: Hive
Issue Type: Sub-task
Components: Query Processor
Reporter: Ning Zhang
Currently variable can only be assigned by a constant. There are cases where
a query generate a single value that should be used by the second query. It
would be nice to assign this value to a variable and pass it to the second
query. For exmaple:
{code}
hive set x_avg = `select avg(x) from T`;
hive select my_udf(${hiveconf:x_avg}, y) from T2;
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2165) variable to be assigned with an atomic value from a query
[
https://issues.apache.org/jira/browse/HIVE-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1302#comment-1302
]
Ning Zhang commented on HIVE-2165:
--
Yeah, I think we should draw a line between a necessary feature and a whole SP
language. This small feature can solve some cases that prevent hive from being
a data flow processing language itself, but I don't think a lot of features in
SP language is necessary because they can be implemented by Hive's UDFs
(transform etc.). And UDFs have the benefits of pushing down computation close
to data. So I think implementing a full-blown SP's control flow is an overkill
and unnecessary, but some small feature like this has its value.
variable to be assigned with an atomic value from a query
-
Key: HIVE-2165
URL: https://issues.apache.org/jira/browse/HIVE-2165
Project: Hive
Issue Type: Sub-task
Components: Query Processor
Reporter: Ning Zhang
Currently variable can only be assigned by a constant. There are cases where
a query generate a single value that should be used by the second query. It
would be nice to assign this value to a variable and pass it to the second
query. For exmaple:
{code}
hive set x_avg = `select avg(x) from T`;
hive select my_udf(${hiveconf:x_avg}, y) from T2;
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2155) Improve error messages emitted during semantic analysis
[ https://issues.apache.org/jira/browse/HIVE-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Syed S. Albiz updated HIVE-2155: Attachment: HIVE-2155.4.patch Updated patch based on reviewboard comments (Changes described there) Improve error messages emitted during semantic analysis --- Key: HIVE-2155 URL: https://issues.apache.org/jira/browse/HIVE-2155 Project: Hive Issue Type: Improvement Reporter: Syed S. Albiz Assignee: Syed S. Albiz Attachments: HIVE-2155.1.patch, HIVE-2155.2.patch, HIVE-2155.3.patch, HIVE-2155.4.patch Follow-up to HIVE-1731. A number of issues raised in HIVE-1731 were caused by SemanticAnalyzer not reporting errors correctly. Specifically, the following issues need to be addressed: - Line numbers are not always provided and sometimes emitted as (0:-1), which is useless - Insufficient or unclear context strings are provided Specific issues described in HIVE-1731: FAILED: Error in semantic analysis: Schema of both sides of union should match: destinationid:_col1 _col2 * No line/col numbers, context strings provide internal aliases instead of actual column names FAILED: Error in semantic analysis: line 0:-1 Both Left and Right Aliases Encountered in Join time * Incorrect line/col number info, no context strings to describe the aliases encountered FAILED: Error in semantic analysis: AS clause has an invalid number of aliases * No line/col numbers, not context string to show the aliases encountered FAILED: Error in semantic analysis: line 1:94 Expression Not In Group By Key a * testcase: SELECT a.id, VAR(a.cnt) FROM mytable a * Context string is unhelpful, needs to provide the actual expression, not just the table reference -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2166) support tar+gzip files in table import
support tar+gzip files in table import -- Key: HIVE-2166 URL: https://issues.apache.org/jira/browse/HIVE-2166 Project: Hive Issue Type: New Feature Reporter: danny Priority: Minor Allow tar.gz input format when loading hdfs data into hive table -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
