[jira] [Resolved] (HIVE-2741) Single binary built against 0.20 and 0.23, does not work against 0.23 clusters.
[ https://issues.apache.org/jira/browse/HIVE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2741. Resolution: Not A Problem > Single binary built against 0.20 and 0.23, does not work against 0.23 > clusters. > --- > > Key: HIVE-2741 > URL: https://issues.apache.org/jira/browse/HIVE-2741 > Project: Hive > Issue Type: Bug > Components: Shims >Affects Versions: 0.8.1 >Reporter: Amareshwari Sriramadasu > Fix For: 0.9.0 > > > After HIVE-2629, if single binary is built for 0.20 and 0.23, it results in > following exception in 0.23 clusters: > java.lang.IncompatibleClassChangeError: Found interface > org.apache.hadoop.mapred.Counters$Counter, but class was > expected > at > org.apache.hadoop.hive.ql.exec.HadoopJobExecHelper.progress(HadoopJobExecHelper.java:341) > at > org.apache.hadoop.hive.ql.exec.HadoopJobExecHelper.progress(HadoopJobExecHelper.java:685) > at > org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:458) > at > org.apache.hadoop.hive.ql.exec.MapRedTask.execute(MapRedTask.java:136) > at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:133) > at > org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57) > at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1332) > at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1123) > at org.apache.hadoop.hive.ql.Driver.run(Driver.java:931) > at > org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:255) > at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212) > at > org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403) > at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671) > at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.hadoop.util.RunJar.main(RunJar.java:200) > FAILED: Execution Error, return code -101 from > org.apache.hadoop.hive.ql.exec.MapRedTask > If we have to make single binary work against both 0.20 and 0.23, we need to > move all such in-compatibilities to Shims. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2339) Preserve RS key columns in columnExprMap after CP optimization, which might be useful to other optimizers
[ https://issues.apache.org/jira/browse/HIVE-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2339. Resolution: Duplicate Fix Version/s: (was: 0.9.0) 0.8.0 Fixed starting 0.8 by HIVE-1989 > Preserve RS key columns in columnExprMap after CP optimization, which might > be useful to other optimizers > - > > Key: HIVE-2339 > URL: https://issues.apache.org/jira/browse/HIVE-2339 > Project: Hive > Issue Type: Sub-task > Components: Query Processor >Reporter: Navis >Assignee: Navis >Priority: Trivial > Fix For: 0.8.0 > > Attachments: HIVE-2339.1.patch > > > In ColumnPrunerProcFactory#pruneReduceSinkOperator, only VALUE parts are > retained from columnExprMap. Doesn't anyone want KEY parts to retained, > either? In my case, it was very useful for backtracking column names and > removing RS in *-RS-*-RS-GBY case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2946) Hive metastore does not have any log messages while shutting itself down.
[ https://issues.apache.org/jira/browse/HIVE-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2946. Resolution: Fixed Fix Version/s: 0.9.0 Committed to trunk and 0.9 Thanks, Vandana! > Hive metastore does not have any log messages while shutting itself down. > -- > > Key: HIVE-2946 > URL: https://issues.apache.org/jira/browse/HIVE-2946 > Project: Hive > Issue Type: Improvement > Components: Metastore >Reporter: Vandana Ayyalasomayajula >Assignee: Vandana Ayyalasomayajula >Priority: Minor > Labels: metastore > Fix For: 0.9.0 > > Attachments: HIVE-2946.D2745.1.patch, HIVE-2946.D2787.1.patch > > > When hive metastore is started, the event is logged with good amount of > information. But when it is stopped ( using a kill) command, no information > is being written to the logs. It will be good if we can add a shutdown event > to the HiveMetastore class. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2936) Warehouse table subdirectories should inherit the group permissions of the warehouse parent directory
[ https://issues.apache.org/jira/browse/HIVE-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2936. Resolution: Fixed Committed. > Warehouse table subdirectories should inherit the group permissions of the > warehouse parent directory > - > > Key: HIVE-2936 > URL: https://issues.apache.org/jira/browse/HIVE-2936 > Project: Hive > Issue Type: New Feature > Components: Metastore >Reporter: Rohini Palaniswamy >Assignee: Rohini Palaniswamy > Fix For: 0.9.0 > > Attachments: HIVE-2504-1.patch, HIVE-2504.patch, HIVE-2504.patch, > HIVE-2936-2.patch > > > When the Hive Metastore creates a subdirectory in the Hive warehouse for > a new table it does so with the default HDFS permissions derived from > dfs.umask or dfs.umaskmode. There should be a option to inherit the > permissions of the parent directory (default warehouse or custom database > directory) so that the table directories have the same permissions as the > database directories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2767) Optionally use framed transport with metastore
[
https://issues.apache.org/jira/browse/HIVE-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan resolved HIVE-2767.
Resolution: Fixed
Fix Version/s: 0.10
Committed. Thanks, Travis!
> Optionally use framed transport with metastore
> --
>
> Key: HIVE-2767
> URL: https://issues.apache.org/jira/browse/HIVE-2767
> Project: Hive
> Issue Type: New Feature
> Components: Metastore
>Reporter: Travis Crawford
>Assignee: Travis Crawford
> Fix For: 0.10
>
> Attachments: HIVE-2767.D2661.1.patch, HIVE-2767.D2661.2.patch,
> HIVE-2767.D2661.3.patch, HIVE-2767.patch.txt, HIVE-2767_a.patch.txt
>
>
> Users may want/need to use thrift's framed transport when communicating with
> the Hive MetaStore. This patch adds a new property
> {{hive.metastore.thrift.framed.transport.enabled}} that enables the framed
> transport (defaults to off, aka no change from before the patch). This
> property must be set for both clients and the HMS server.
> It wasn't immediately clear how to use the framed transport with SASL, so as
> written an exception is thrown if you try starting the server with both
> options. If SASL and the framed transport will indeed work together I can
> update the patch (although I don't have a secured environment to test in).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2888) Creating an external table using the 'LIKE' clause actually creates a managed table.
[ https://issues.apache.org/jira/browse/HIVE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2888. Resolution: Fixed Fix Version/s: 0.8.0 Fixed in HIVE-2086. > Creating an external table using the 'LIKE' clause actually creates a managed > table. > > > Key: HIVE-2888 > URL: https://issues.apache.org/jira/browse/HIVE-2888 > Project: Hive > Issue Type: Bug > Components: Metastore >Affects Versions: 0.7.1 >Reporter: Craig Swift > Fix For: 0.8.0 > > Original Estimate: 12h > Remaining Estimate: 12h > > When creating a new table with both the EXTERNAL and LIKE clauses, the new > table does not behave as an EXTERNAL table thus resulting in potential data > loss. > Example: > create external table test1 (VAL string) location '/user/craig/test1'; > create external table test2 like test1 location '/user/craig/test2'; > drop table test1; > /user/craig/test1 - still exists > drop table test2; > /user/craig/test2 - is deleted (bad) > If I do an extended describe on both tables, test1 shows up as being external > while test2 is a managed table. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2764) Obtain delegation tokens for MR jobs in secure hbase setup
[ https://issues.apache.org/jira/browse/HIVE-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2764. Resolution: Fixed Fix Version/s: 0.9.0 Checked-in trunk. Thanks, Enis! > Obtain delegation tokens for MR jobs in secure hbase setup > > > Key: HIVE-2764 > URL: https://issues.apache.org/jira/browse/HIVE-2764 > Project: Hive > Issue Type: Improvement > Components: HBase Handler, Security >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: 0.9.0 > > Attachments: HIVE-2764.D2205.1.patch, HIVE-2764.D2205.2.patch, > HIVE-2764.D2205.3.patch, HIVE-2764.D2205.4.patch, HIVE-2764.D2205.5.patch, > HIVE-2764_v0.patch > > > As discussed in HCATALOG-244, in a secure hbase setup with 0.92, we need to > obtain delegation tokens for hbase and save it in jobconf, so that tasks can > access region servers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2822) Add JSON output to the hive ddl commands
[
https://issues.apache.org/jira/browse/HIVE-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan resolved HIVE-2822.
Resolution: Fixed
Fix Version/s: 0.9.0
Committed to trunk. Thanks, Chris!
> Add JSON output to the hive ddl commands
>
>
> Key: HIVE-2822
> URL: https://issues.apache.org/jira/browse/HIVE-2822
> Project: Hive
> Issue Type: Improvement
>Reporter: Chris Dean
>Assignee: Chris Dean
> Fix For: 0.9.0
>
> Attachments: HIVE-2822.03-branch0-8.patch, HIVE-2822.03.patch,
> HIVE-2822.03b.patch, HIVE-2822.04-branch-08.patch,
> HIVE-2822.05-branch0-8-1.patch, HIVE-2822.05-branch0-8.patch,
> HIVE-2822.05.patch, HIVE-2822.D2475.1.patch, HIVE-2822.D2475.2.patch,
> HIVE-2822.D2475.3.patch, HIVE-2822.D2475.4.patch,
> hive-json-01-branch0-8.patch, hive-json-01.patch,
> hive-json-02-branch0-8.patch, hive-json-02.patch
>
>
> The goal is to have an option to produce JSON output of the DDL commands that
> is easily machine parseable.
> For example, "desc my_table" currently gives
> {noformat}
> idbigint
> user string
> {noformat}
> and we want to allow a json output:
> {noformat}
> {
> "columns": [
> {"name": "id", "type": "bigint"},
> {"name": "user", "type": "string"}
> ]
> }
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2891) TextConverter for UDF's is inefficient if the input object is already Text or Lazy
[ https://issues.apache.org/jira/browse/HIVE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2891. Resolution: Fixed Fix Version/s: 0.9.0 Committed to trunk. Thanks, Cliff! > TextConverter for UDF's is inefficient if the input object is already Text or > Lazy > -- > > Key: HIVE-2891 > URL: https://issues.apache.org/jira/browse/HIVE-2891 > Project: Hive > Issue Type: Improvement > Components: Serializers/Deserializers >Affects Versions: 0.7.0, 0.7.1, 0.8.1 >Reporter: Cliff Engle >Assignee: Cliff Engle >Priority: Minor > Fix For: 0.9.0 > > Attachments: HIVE-2891.1.patch.txt, HIVE-2891.2.patch.txt > > > The TextConverter in PrimitiveObjectInspectorConverter.java is very > inefficient if the input object is already Text or Lazy. Since it calls > getPrimitiveJavaObject, each Text is decoded into a String and then > re-encoded into Text. The solution is to check if preferWritable() is true, > then call getPrimitiveWritable(input). > To test performance, I ran the Grep query from > https://issues.apache.org/jira/browse/HIVE-396 on a cluster of 3 ec2 large > nodes (2 slaves 1 master) on 6GB of data. It took 21 map tasks. With the > current 0.8.1 version, it took 81 seconds. After patching, it took 66 seconds. > I will attach a patch and testcases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2262) mapjoin followed by union all, groupby does not work
[ https://issues.apache.org/jira/browse/HIVE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2262. Resolution: Fixed This is no longer reproducible on trunk. Feel free to reopen if there is some other variant which can produce this. > mapjoin followed by union all, groupby does not work > > > Key: HIVE-2262 > URL: https://issues.apache.org/jira/browse/HIVE-2262 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.7.1 >Reporter: yu xiang >Priority: Trivial > > sql: > CREATE TABLE nulltest2(int_data1 INT, int_data2 INT, boolean_data BOOLEAN, > double_data DOUBLE, string_data STRING) ROW FORMAT DELIMITED FIELDS > TERMINATED BY ','; > CREATE TABLE nulltest3(int_data1 INT) ROW FORMAT DELIMITED FIELDS TERMINATED > BY ','; > explain select int_data2,count(1) from (select /*+mapjoin(a)*/ int_data2, 1 > as c1, 0 as c2 from nulltest2 a join nulltest3 b on(a.int_data1 = > b.int_data1) union all select /*+mapjoin(a)*/ int_data2, 1 as c1, 2 as c2 > from nulltest2 a join nulltest3 b on(a.int_data1 = b.int_data1)) mapjointable > group by int_data2; > exception: > FAILED: Hive Internal Error: java.lang.NullPointerException(null) > java.lang.NullPointerException > at > org.apache.hadoop.hive.ql.optimizer.ppr.PartitionPruner.prune(PartitionPruner.java:156) > at > org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.setTaskPlan(GenMapRedUtils.java:551) > at > org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.setTaskPlan(GenMapRedUtils.java:514) > at > org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.initPlan(GenMapRedUtils.java:125) > at > org.apache.hadoop.hive.ql.optimizer.GenMRRedSink1.process(GenMRRedSink1.java:76) > at > org.apache.hadoop.hive.ql.optimizer.GenMRRedSink3.process(GenMRRedSink3.java:64) > at > org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:89) > Analyse the reason: > 1.When use mapjoin,union,groupby together,the > UnionProcFactory.MapJoinUnion()(optimizer) will set the MapJoinSubq true, and > set up the UnionParseContext. > 2.In GenMRUnion1, hive will call mergeMapJoinUnion, and also set task plan. > 3.In GenMRRedSink3, hive judges the uCtx.isMapOnlySubq(), and call > GenMRRedSink1()).process() to init the plan.But the utask's plan has been set > yet, it just need to set reducer.And also the utask is processing temporary > table, there is no topOp map to table.So here we get null exception. > Solutions: > 1.SQL solution:use a sub query to modify the sql; > 2.Code solution:when in mergeMapJoinUnion, after the task plan have been set, > set a settaskplan flag true to indicate the plan for this utask has been > set.When in GenMRRedSink3 ,if this flag sets true, don't use the > GenMRRedSink1()).process() to reinit the plan. > > if (uCtx.isMapOnlySubq()&&!upc.isIssetTaskPlan()) > > I don't know whether the code solution is suitable. > Is there any better solution? > thx -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2857) QTestUtil.cleanUp() fails with FileNotException on 0.23
[ https://issues.apache.org/jira/browse/HIVE-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2857. Resolution: Fixed Committed to trunk. > QTestUtil.cleanUp() fails with FileNotException on 0.23 > --- > > Key: HIVE-2857 > URL: https://issues.apache.org/jira/browse/HIVE-2857 > Project: Hive > Issue Type: Bug > Components: Testing Infrastructure >Affects Versions: 0.9.0 >Reporter: Carl Steinbach >Assignee: Carl Steinbach > Fix For: 0.9.0 > > Attachments: HIVE-2857.D2229.1.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2761) Remove lib/javaewah-0.3.jar
[ https://issues.apache.org/jira/browse/HIVE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2761. Resolution: Fixed Committed to trunk. Thanks, Ed! > Remove lib/javaewah-0.3.jar > --- > > Key: HIVE-2761 > URL: https://issues.apache.org/jira/browse/HIVE-2761 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Affects Versions: 0.8.0, 0.8.1, 0.9.0 >Reporter: Ashutosh Chauhan >Assignee: Edward Capriolo > Fix For: 0.9.0 > > Attachments: HIVE-2761.2.patch.txt, HIVE-2761.3.patch.txt, > HIVE-2761.D1911.1.patch, HIVE-2761.D1911.2.patch > > > After HIVE-2391 it is retrieved from maven repo via ivy, we can get rid of it > from our lib/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2731) Precommit builds at Jenkins
[ https://issues.apache.org/jira/browse/HIVE-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2731. Resolution: Duplicate Dupe of HIVE-1175 > Precommit builds at Jenkins > > > Key: HIVE-2731 > URL: https://issues.apache.org/jira/browse/HIVE-2731 > Project: Hive > Issue Type: Improvement > Components: Build Infrastructure, Testing Infrastructure >Reporter: Enis Soztutar > > Precommit builds, similar to what Hadoop/Hbase/ZK do is a great developer > tool, so that we can enforce tests, test coverage, audit checks, etc. I guess > we can ask Yahoo folks to use one of the Hadoop build machines. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2277) Use Ivy to satisfy unresolved commons-codec dependencies
[ https://issues.apache.org/jira/browse/HIVE-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2277. Resolution: Not A Problem No further work required on this one. > Use Ivy to satisfy unresolved commons-codec dependencies > > > Key: HIVE-2277 > URL: https://issues.apache.org/jira/browse/HIVE-2277 > Project: Hive > Issue Type: Bug > Components: Contrib >Reporter: Carl Steinbach >Assignee: Carl Steinbach > Attachments: HIVE-2277-codec.1.patch.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1237) select coalesce(null) from src dies
[ https://issues.apache.org/jira/browse/HIVE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1237. Resolution: Duplicate This is getting worked upon at HIVE-2726 through an alternative approach. > select coalesce(null) from src dies > --- > > Key: HIVE-1237 > URL: https://issues.apache.org/jira/browse/HIVE-1237 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.7.0, 0.8.0 >Reporter: Namit Jain >Assignee: Ashutosh Chauhan > Attachments: hive-1237.patch, hive-1237_1.patch > > > select coalesce(null) from src ; > FAILED: Unknown exception: null -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2135) Refactor HiveMetaStore.java
[ https://issues.apache.org/jira/browse/HIVE-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2135. Resolution: Duplicate This got taken care of in a better fashion in HIVE-2716. > Refactor HiveMetaStore.java > --- > > Key: HIVE-2135 > URL: https://issues.apache.org/jira/browse/HIVE-2135 > Project: Hive > Issue Type: Improvement > Components: Metastore >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: hive_2135.patch, refactor.patch > > > HiveMetaStore.java is more then 3000 LOC which contains wide variety of code. > It will be good to refactor it so that its easier to maintain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2768) Add a getAuthorizationProvider to HiveStorageHandler
[ https://issues.apache.org/jira/browse/HIVE-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2768. Resolution: Fixed Fix Version/s: 0.9.0 Committed to trunk. Thanks, Francis! > Add a getAuthorizationProvider to HiveStorageHandler > > > Key: HIVE-2768 > URL: https://issues.apache.org/jira/browse/HIVE-2768 > Project: Hive > Issue Type: Task > Components: HBase Handler >Reporter: Alan Gates >Assignee: Francis Liu > Fix For: 0.9.0 > > Attachments: HIVE-2768.D1869.1.patch > > > In version 0.92 HBase supports ACLs for tables. In HCatalog, since we > delegate security to the underlying storage layer, we would like to be able > to obtain a HiveAuthorizationProvider specific to a HiveStorageHandler > instance. This can be done by adding a getAuthorizationProvider method to > HiveStorageHandler. In the case where Hive is configured to use the > DefaultHiveAuthorizationProvider this call will return the same default > provider, since Hive handles all of the authorization itself in that case. > In the case where it is configured to use the HCatAuthorizationProvider, it > would return an instance specific to the underlying storage. > For more background on this proposed change see HCATALOG-237 and > https://cwiki.apache.org/confluence/display/HCATALOG/Hcat+Security+Design -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2792) SUBSTR(CAST( AS BINARY)) produces unexpected results
[ https://issues.apache.org/jira/browse/HIVE-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2792. Resolution: Fixed Committed to trunk. Thanks, Navis! > SUBSTR(CAST( AS BINARY)) produces unexpected results > > > Key: HIVE-2792 > URL: https://issues.apache.org/jira/browse/HIVE-2792 > Project: Hive > Issue Type: Bug > Components: UDF >Affects Versions: 0.8.0, 0.8.1 >Reporter: Carl Steinbach >Assignee: Navis > Fix For: 0.9.0 > > Attachments: HIVE-2792.D1797.1.patch, HIVE-2792.D1797.2.patch, > HIVE-2792.D1797.2.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2725) Fix flaky testing infrastructure
[ https://issues.apache.org/jira/browse/HIVE-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2725. Resolution: Fixed Fix Version/s: 0.9.0 Assignee: Ashutosh Chauhan Trunk is green now. Resolving this as fixed. Only remaining issue is HIVE-2811 > Fix flaky testing infrastructure > - > > Key: HIVE-2725 > URL: https://issues.apache.org/jira/browse/HIVE-2725 > Project: Hive > Issue Type: Bug > Components: Testing Infrastructure >Affects Versions: 0.9.0 >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > > To begin with > org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_insert2_overwrite_partitions > and org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_inputddl5 are > failing on trunk for a while now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2735) PlanUtils.configureTableJobPropertiesForStorageHandler() is not called for partitioned table
[ https://issues.apache.org/jira/browse/HIVE-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2735. Resolution: Fixed Fix Version/s: 0.9.0 Committed to trunk. Thanks, Sushanth! > PlanUtils.configureTableJobPropertiesForStorageHandler() is not called for > partitioned table > > > Key: HIVE-2735 > URL: https://issues.apache.org/jira/browse/HIVE-2735 > Project: Hive > Issue Type: Bug >Affects Versions: 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.9.0 >Reporter: Ashutosh Chauhan >Assignee: Sushanth Sowmyan > Fix For: 0.9.0 > > Attachments: sem_patch.patch > > > As a result, if there is a query which results in a MR job which needs to be > configured via storage handler, it returns in failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2616) Passing user identity from metastore client to server in non-secure mode
[ https://issues.apache.org/jira/browse/HIVE-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2616. Resolution: Fixed Fix Version/s: 0.9.0 Thanks, Carl for the review. Committed to trunk. > Passing user identity from metastore client to server in non-secure mode > > > Key: HIVE-2616 > URL: https://issues.apache.org/jira/browse/HIVE-2616 > Project: Hive > Issue Type: Bug > Components: Metastore >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: hive-2616.patch, hive-2616_1.patch, hive-2616_3.patch, > hive-2616_4.patch, hive-2616_5.patch > > > Currently in unsecure mode client don't pass on user identity. As a result > hdfs and other operations done by server gets executed by user running > metastore process instead of being done in context of client. This results in > problem as reported here: > http://mail-archives.apache.org/mod_mbox/hive-user/20.mbox/%3CCAK0mCrRC3aPqtRHDe2J25Rm0JX6TS1KXxd7KPjqJjoqBjg=a...@mail.gmail.com%3E -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2681) SUCESS is misspelled
[ https://issues.apache.org/jira/browse/HIVE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2681. Resolution: Fixed Fix Version/s: 0.9.0 HIVE-2686 passed on another machine. So, looks like some problem in my local environment. Committed this one to trunk. > SUCESS is misspelled > > > Key: HIVE-2681 > URL: https://issues.apache.org/jira/browse/HIVE-2681 > Project: Hive > Issue Type: Bug >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Fix For: 0.9.0 > > Attachments: HIVE-2681.D1029.1.patch, HIVE-2681.D1029.1.patch > > > C'mon! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2290) Improve error messages for DESCRIBE command
[ https://issues.apache.org/jira/browse/HIVE-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2290. Resolution: Fixed Fix Version/s: 0.9.0 Fixed as part of HIVE-11 which results in a better error message. > Improve error messages for DESCRIBE command > --- > > Key: HIVE-2290 > URL: https://issues.apache.org/jira/browse/HIVE-2290 > Project: Hive > Issue Type: Improvement > Components: Diagnosability, SQL >Reporter: Carl Steinbach > Fix For: 0.9.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1302) describe parse_url throws an error
[ https://issues.apache.org/jira/browse/HIVE-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1302. Resolution: Fixed Fix Version/s: 0.9.0 Fixed as part of HIVE-11 which results in a better error message. > describe parse_url throws an error > -- > > Key: HIVE-1302 > URL: https://issues.apache.org/jira/browse/HIVE-1302 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain > Fix For: 0.9.0 > > > descHive history > file=/tmp/njain/hive_job_log_njain_201004121528_1840617354.txt > hive> describe parse_url; > FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask > hive> describe extended parse_url; > FAILED: Execution Error, return code 1 from > org.apache.hadoop.hive.ql.exec.DDLTask > hive> [njain@dev029 clientpositive]$ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1698) Improve error log in HiveInputFormat
[ https://issues.apache.org/jira/browse/HIVE-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1698. Resolution: Fixed Fix Version/s: 0.7.0 This got resolved as part of HIVE-1203 > Improve error log in HiveInputFormat > > > Key: HIVE-1698 > URL: https://issues.apache.org/jira/browse/HIVE-1698 > Project: Hive > Issue Type: Improvement > Components: Server Infrastructure >Affects Versions: 0.7.0 >Reporter: Ted Yu > Fix For: 0.7.0 > > > When newInstance() call fails in getInputFormatFromCache(), the exception > isn't displayed in the log. > java.io.IOException: Cannot create an instance of InputFormat class > org.apache.hadoop.mapred.TextInputFormat as specified in mapredWork! > It would help debug the issue by including the exception in log, e.g.: > Caused by: java.lang.RuntimeException: Error in configuring object > at > org.apache.hadoop.util.ReflectionUtils.setJobConf(ReflectionUtils.java:93) > at > org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:64) > at > org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:117) > at > org.apache.hadoop.hive.ql.io.HiveInputFormat.getInputFormatFromCache(HiveInputFormat.java:194) > ... 19 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.hadoop.util.ReflectionUtils.setJobConf(ReflectionUtils.java:88) > ... 22 more > Caused by: java.lang.IllegalArgumentException: Compression codec > com.hadoop.compression.lzo.LzoCodec not found. > at > org.apache.hadoop.io.compress.CompressionCodecFactory.getCodecClasses(CompressionCodecFactory.java:96) > at > org.apache.hadoop.io.compress.CompressionCodecFactory.(CompressionCodecFactory.java:134) > at > org.apache.hadoop.mapred.TextInputFormat.configure(TextInputFormat.java:41) > ... 27 more > Caused by: java.lang.ClassNotFoundException: > com.hadoop.compression.lzo.LzoCodec > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-49) [Hive] display column header on CLI
[ https://issues.apache.org/jira/browse/HIVE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-49. -- Resolution: Fixed Fix Version/s: 0.7.0 Got resolved as part of HIVE-138 > [Hive] display column header on CLI > --- > > Key: HIVE-49 > URL: https://issues.apache.org/jira/browse/HIVE-49 > Project: Hive > Issue Type: Bug > Components: Clients >Reporter: YoungWoo Kim >Assignee: Edward Capriolo >Priority: Minor > Fix For: 0.7.0 > > > The result row(s) on CLI are displayed without column header. > It would be useful to be able to set header on or off by users. > for example, > hive> SET HEAD [ON|OFF]/* similar to oracle sql*plus syntax */ > or > hive> SET [GLOBAL|SESSION] HEADER=[ON|OFF]/* similar to mysql's "SET" > syntax */ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1209) alter table replace columns does not check for partitioned columns
[ https://issues.apache.org/jira/browse/HIVE-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1209. Resolution: Duplicate Marking as duplicate of HIVE-2415 which has more discussion. > alter table replace columns does not check for partitioned columns > -- > > Key: HIVE-1209 > URL: https://issues.apache.org/jira/browse/HIVE-1209 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain >Assignee: Paul Yang > > create table foo (a int) partitioned by (b int); > alter table foo replace columns (a int, b int); > succeeds. It should fail appropriately -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1932) testnegativeclidriver broken in trunk
[ https://issues.apache.org/jira/browse/HIVE-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1932. Resolution: Invalid There are no such query files show_bad_tables1.q or show_bad_tables2.q > testnegativeclidriver broken in trunk > - > > Key: HIVE-1932 > URL: https://issues.apache.org/jira/browse/HIVE-1932 > Project: Hive > Issue Type: Bug >Reporter: Namit Jain > > show_bad_tables1.q and show_bad_tables2.q tests are breaking in trunk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1021) string to double conversion may have side effects
[
https://issues.apache.org/jira/browse/HIVE-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan resolved HIVE-1021.
Resolution: Cannot Reproduce
When I ran the above query it didn't return any result which was expected.
{code}
hive> create table src (key string, value string);
load data local inpath '../../../../data/files/kv1.txt' into table src;
hive> select k.key, v.value from src k join src v on k.key=v.key and
k.value=v.value+1;
Total MapReduce jobs = 1
Launching Job 1 out of 1
Number of reduce tasks not specified. Estimated from input data size: 1
In order to change the average load for a reducer (in bytes):
set hive.exec.reducers.bytes.per.reducer=
In order to limit the maximum number of reducers:
set hive.exec.reducers.max=
In order to set a constant number of reducers:
set mapred.reduce.tasks=
Starting Job = job_20012116_0002, Tracking URL =
http://localhost:50030/jobdetails.jsp?jobid=job_20012116_0002
Hadoop job information for Stage-1: number of mappers: 1; number of reducers: 1
2011-11-02 18:01:15,591 Stage-1 map = 0%, reduce = 0%
2011-11-02 18:01:21,643 Stage-1 map = 100%, reduce = 0%
2011-11-02 18:01:37,007 Stage-1 map = 100%, reduce = 100%
Ended Job = job_20012116_0002
MapReduce Jobs Launched:
Job 0: Map: 1 Reduce: 1 HDFS Read: 6019 HDFS Write: 0 SUCESS
Total MapReduce CPU Time Spent: 0 msec
OK
Time taken: 39.108 seconds
{code}
> string to double conversion may have side effects
> -
>
> Key: HIVE-1021
> URL: https://issues.apache.org/jira/browse/HIVE-1021
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: Namit Jain
>
> select k.key, v.value from src k join src v on k.key=v.key and
> k.value=v.value+1;
> returns results, because v.value + 1 becomes null and so does the LHS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1683) Column aliases cannot be used in a group by clause
[ https://issues.apache.org/jira/browse/HIVE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1683. Resolution: Invalid John's explanation makes sense. Projections are handled after aggregations. There is no easy way to make it work. > Column aliases cannot be used in a group by clause > -- > > Key: HIVE-1683 > URL: https://issues.apache.org/jira/browse/HIVE-1683 > Project: Hive > Issue Type: Bug > Components: Metastore >Reporter: Shrikrishna Lawande > Labels: SQL > > Column aliases cannot be used in a group by clause > Following query would fail : > select col1 as t, count(col2) from test group by t; > FAILED: Error in semantic analysis: line 1:49 Invalid Table Alias or Column > Reference t -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1825) Different defaults for hive.metastore.local
[
https://issues.apache.org/jira/browse/HIVE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan resolved HIVE-1825.
Resolution: Fixed
Fix Version/s: 0.9.0
This got resolved as part of HIVE-1461
> Different defaults for hive.metastore.local
> ---
>
> Key: HIVE-1825
> URL: https://issues.apache.org/jira/browse/HIVE-1825
> Project: Hive
> Issue Type: Bug
> Components: Configuration, Metastore
>Affects Versions: 0.6.0
>Reporter: Lars Francke
> Fix For: 0.9.0
>
>
> hive-default.xml sets {{hive.metastore.local}} to {{true}}. In the code
> however there is this:
> {code:title=HiveMetaStoreClient.java}
> boolean localMetaStore = conf.getBoolean("hive.metastore.local", false);
> {code}
> This leads to different behaviour depending on whether hbase-default.xml is
> on the classpath or not.which can lead to some confusion ;-)
> I can supply a patch - should be pretty similar. I just don't know what the
> "real" default should be. My guess would be {{true}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1458) Table aliases are case sensitive.
[ https://issues.apache.org/jira/browse/HIVE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1458. Resolution: Cannot Reproduce No longer a problem in trunk. > Table aliases are case sensitive. > - > > Key: HIVE-1458 > URL: https://issues.apache.org/jira/browse/HIVE-1458 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Jonathan Chang >Assignee: Paul Yang >Priority: Minor > > This query: > SELECT exploded, COUNT(1) > > FROM ( > > SELECT SPLIT(value, "0") AS value > > FROM tmp_jonchang_hive_test > > ) B LATERAL VIEW explode(value) C AS exploded > > GROUP BY exploded > produces the error: > FAILED: Error in semantic analysis: line 7:9 Invalid Table Alias or Column > Reference exploded > However, when B is changed to lowercase, the query works as expected: > SELECT exploded, COUNT(1) > > FROM ( > > SELECT SPLIT(value, "0") AS value > > FROM tmp_jonchang_hive_test > > ) b LATERAL VIEW explode(value) C AS exploded > > GROUP BY exploded > Table aliases shouldn't be case sensitive AFAIK. And even if they are, I > can't see the cause for the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2119) Optimizer on partition field
[ https://issues.apache.org/jira/browse/HIVE-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2119. Resolution: Fixed Fix Version/s: 0.9.0 Fixed as part of HIVE-1003 > Optimizer on partition field > > > Key: HIVE-2119 > URL: https://issues.apache.org/jira/browse/HIVE-2119 > Project: Hive > Issue Type: Improvement >Reporter: Ron Bodkin > Fix For: 0.9.0 > > > The optimizer doesn't use partition metadata, e.g., > select max(dt) from big_partitioned_table; > Instead of just returning the biggest date in the table, it runs a full table > scan. This kind of expression can also be useful in more interesting cases > like: > select count(*) from big_partitioned_table a join (select max(dt) m from > big_partitioned_table) b on a.dt=b.m; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1784) Ctrl+c should kill currently running query, but not exit the CLI
[ https://issues.apache.org/jira/browse/HIVE-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1784. Resolution: Duplicate Fix Version/s: 0.8.0 Fixed in HIVE-243 > Ctrl+c should kill currently running query, but not exit the CLI > > > Key: HIVE-1784 > URL: https://issues.apache.org/jira/browse/HIVE-1784 > Project: Hive > Issue Type: Improvement > Components: CLI >Affects Versions: 0.7.0 >Reporter: Paul Yang >Priority: Minor > Fix For: 0.8.0 > > > When a query is running and Ctrl+C is pressed, the query is killed and the > CLI is exited. Instead, Ctrl+c should kill the query but return the user to > the Hive prompt. This will make it easier to modify and re-submit the query. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1632) Column length not sufficient for large STRUCT definitions
[
https://issues.apache.org/jira/browse/HIVE-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan resolved HIVE-1632.
Resolution: Fixed
Fix Version/s: 0.6.0
This got resolved as part of HIVE-1364
> Column length not sufficient for large STRUCT definitions
> -
>
> Key: HIVE-1632
> URL: https://issues.apache.org/jira/browse/HIVE-1632
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 0.5.0
>Reporter: Wolfgang Nagele
>Priority: Trivial
> Fix For: 0.6.0
>
>
> Can be reproduced by adding the following table:
> {code}hive> CREATE TABLE test (big struct prop2: int,
> prop3: int,
> prop4: int,
> prop5: int,
> prop6: int,
> prop7: int,
> prop8: int,
> prop9: int,
> prop10: int,
> prop10: int,
> prop11: int,
> prop12: int,
> prop13: int,
> prop14: int,
> prop15: int,
> prop16: int,
> prop17: int,
> prop18: int,
> prop19: int>);{code}
> Error:
> {noformat}FAILED: Error in metadata: javax.jdo.JDODataStoreException: Add
> request failed : INSERT INTO COLUMNS
> (SD_ID,COMMENT,"COLUMN_NAME",TYPE_NAME,INTEGER_IDX) VALUES (?,?,?,?,?)
> NestedThrowables:
> java.sql.SQLDataException: A truncation error was encountered trying to
> shrink VARCHAR
> 'struct FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.DDLTask{noformat}
> Workaround:
> Change column length in metastore. Derby example: {{ALTER TABLE columns ALTER
> type_name SET DATA TYPE VARCHAR(1000);}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-379) TestHWISessionManager.testHiveDriver fails
[ https://issues.apache.org/jira/browse/HIVE-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-379. --- Resolution: Fixed This doesn't look like a problem any longer. Builds are passing on jenkins. > TestHWISessionManager.testHiveDriver fails > -- > > Key: HIVE-379 > URL: https://issues.apache.org/jira/browse/HIVE-379 > Project: Hive > Issue Type: Bug >Affects Versions: 0.3.0 >Reporter: Johan Oskarsson >Assignee: Ashish Thusoo >Priority: Critical > > The TestHWISessionManager.testHiveDriver fails with the following error: > junit.framework.AssertionFailedError: expected:<9> but was:<0> > at > org.apache.hadoop.hive.hwi.TestHWISessionManager.testHiveDriver(TestHWISessionManager.java:124) > See build for more details: > http://hudson.zones.apache.org/hudson/job/Hive-trunk-h0.17/47/testReport/org.apache.hadoop.hive.hwi/TestHWISessionManager/testHiveDriver/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1318) External Tables: Selecting a partition that does not exist produces errors
[
https://issues.apache.org/jira/browse/HIVE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan resolved HIVE-1318.
Resolution: Cannot Reproduce
Works for me too on trunk, with 0 rows returned.
> External Tables: Selecting a partition that does not exist produces errors
> --
>
> Key: HIVE-1318
> URL: https://issues.apache.org/jira/browse/HIVE-1318
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.5.0
>Reporter: Edward Capriolo
> Attachments: partdoom.q
>
>
> {noformat}
> dfs -mkdir /tmp/a;
> dfs -mkdir /tmp/a/b;
> dfs -mkdir /tmp/a/c;
> create external table abc( key string, val string )
> partitioned by (part int)
> location '/tmp/a/';
> alter table abc ADD PARTITION (part=1) LOCATION 'b';
> alter table abc ADD PARTITION (part=2) LOCATION 'c';
> select key from abc where part=1;
> select key from abct where part=70;
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2341) SemanticAnalyzer.genJoinReduceSinkChild fails with NPE unless you specify an un-necessary table alias
[ https://issues.apache.org/jira/browse/HIVE-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2341. Resolution: Cannot Reproduce This is not reproducible on trunk. > SemanticAnalyzer.genJoinReduceSinkChild fails with NPE unless you specify an > un-necessary table alias > - > > Key: HIVE-2341 > URL: https://issues.apache.org/jira/browse/HIVE-2341 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.7.1 >Reporter: Ido Hadanny > > Following query: > select * from > V_EMF_LEARNING_ACTUAL_CHURN > join > (select count(*) as total from standard_connections) b > fails with the NPE listed below. It doesn't if you add an alias to the table > like so: > select * from > V_EMF_LEARNING_ACTUAL_CHURN a > join > (select count(*) as total from standard_connections) b > The exception I'm getting: > java.lang.NullPointerException > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genJoinReduceSinkChild(SemanticAnalyzer.java:4440) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genJoinOperator(SemanticAnalyzer.java:4545) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genJoinPlan(SemanticAnalyzer.java:4704) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:6011) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:6603) > at > org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:238) > at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:340) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-46) derbyclient.jar and derbytools.jar should be included in hive/lib
[ https://issues.apache.org/jira/browse/HIVE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-46. -- Resolution: Fixed derby.jar is now present in lib/ dir. No more NPE. > derbyclient.jar and derbytools.jar should be included in hive/lib > - > > Key: HIVE-46 > URL: https://issues.apache.org/jira/browse/HIVE-46 > Project: Hive > Issue Type: Bug > Components: Metastore > Environment: Cent OS 5 x86-64 JDK 1.6 >Reporter: Edward Capriolo >Priority: Minor > > Attempting to use the Derby ClientDriver will cause a null pointer exception > because derbyclient.jar and derbytools.jar are not in lib. > hive> show tables; > 08/10/02 15:17:12 INFO hive.metastore: Trying to connect to metastore > with URI jdbc:derby://nyhadoop1:1527/metastore_db > FAILED: Error in semantic analysis: java.lang.NullPointerException > 08/10/02 15:17:12 ERROR ql.Driver: FAILED: Error in semantic analysis: > java.lang.NullPointerException > derbyclient.jar and derbytools.jar should probably be put in the hive/lib > directory. Also this type of exception could happen often with different JDBC > libraries the exception should be trapped better -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-851) Thrift Client: BaseException.message deprecation warning in Python 2.6
[ https://issues.apache.org/jira/browse/HIVE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-851. --- Resolution: Invalid This is in thrift generated code. Needs to be fixed in Thrift project. > Thrift Client: BaseException.message deprecation warning in Python 2.6 > -- > > Key: HIVE-851 > URL: https://issues.apache.org/jira/browse/HIVE-851 > Project: Hive > Issue Type: Bug > Components: Clients >Reporter: Matt Pestritto >Priority: Minor > Attachments: hive_851.patch > > > In Python 2.6 BaseException.message has been deprecated. This is a patch to > remove these warnings. > src/thrift/Thrift.py:62: DeprecationWarning: BaseException.message has been > deprecated as of Python 2.6 > self.message = message > Also note. I could only replicate this error in two clases and there were > other classes that inherited (Exception). > Patch is only attached for those two classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2197) SessionState used before ThreadLocal set
[ https://issues.apache.org/jira/browse/HIVE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2197. Resolution: Fixed Fix Version/s: 0.9.0 This no longer true in trunk. > SessionState used before ThreadLocal set > > > Key: HIVE-2197 > URL: https://issues.apache.org/jira/browse/HIVE-2197 > Project: Hive > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Zizon >Priority: Minor > Fix For: 0.9.0 > > > while invoke the method like : > SessionState.start(new HiveConf(HiveConf.class)) > it comes out following exception stack: > at > org.apache.hadoop.hive.ql.session.CreateTableAutomaticGrant.getGrantorInfoList(CreateTableAutomaticGrant.java:101) > at > org.apache.hadoop.hive.ql.session.CreateTableAutomaticGrant.getGrantMap(CreateTableAutomaticGrant.java:79) > at > org.apache.hadoop.hive.ql.session.CreateTableAutomaticGrant.create(CreateTableAutomaticGrant.java:41) > at > org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:194) > because the CreateTableAutomaticGrant.getGrantorInfoList will try to get > Authenticator via SessionState.get().getAuthenticator() while the > 'tts'(thread local) is still null(it is being set at line 195 but the invoke > happended at line 194 in SessionState.start(conf) ). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-192) Add TIMESTAMP column type for thrift dynamic_type
[ https://issues.apache.org/jira/browse/HIVE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-192. --- Resolution: Fixed Fix Version/s: 0.8.0 HIVE-2272 added TIMESTAMP as primitive type. > Add TIMESTAMP column type for thrift dynamic_type > - > > Key: HIVE-192 > URL: https://issues.apache.org/jira/browse/HIVE-192 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Johan Oskarsson >Assignee: Shyam Sundar Sarkar > Labels: SQL > Fix For: 0.8.0 > > Attachments: Hive-192.patch.txt, TIMESTAMP_specification.txt, > create_2.q.txt > > > create table something2 (test timestamp); > ERROR: DDL specifying type timestamp which has not been defined > java.lang.RuntimeException: specifying type timestamp which has not been > defined > at > org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.FieldType(thrift_grammar.java:1879) > at > org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.Field(thrift_grammar.java:1545) > at > org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.FieldList(thrift_grammar.java:1501) > at > org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.Struct(thrift_grammar.java:1171) > at > org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.TypeDefinition(thrift_grammar.java:497) > at > org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.Definition(thrift_grammar.java:439) > at > org.apache.hadoop.hive.serde2.dynamic_type.thrift_grammar.Start(thrift_grammar.java:101) > at > org.apache.hadoop.hive.serde2.dynamic_type.DynamicSerDe.initialize(DynamicSerDe.java:97) > at > org.apache.hadoop.hive.metastore.MetaStoreUtils.getDeserializer(MetaStoreUtils.java:180) > at org.apache.hadoop.hive.ql.metadata.Table.initSerDe(Table.java:141) > at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:202) > at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:641) > at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:98) > at org.apache.hadoop.hive.ql.Driver.run(Driver.java:215) > at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:174) > at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:207) > at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:305) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-128) Fix dependencies between hive modules (ql, metastore, serde and common) in order to enable module based compilation
[ https://issues.apache.org/jira/browse/HIVE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-128. --- Resolution: Invalid After HIVE-2243 its not even possible to compile from within any subdir. > Fix dependencies between hive modules (ql, metastore, serde and common) in > order to enable module based compilation > --- > > Key: HIVE-128 > URL: https://issues.apache.org/jira/browse/HIVE-128 > Project: Hive > Issue Type: Bug > Components: Build Infrastructure >Reporter: Ashish Thusoo > > Currently due to broken dependencies, a compile within the metastore > directory does not automatically trigger the compile in common etc... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-846) move hive tables from one database to another
[ https://issues.apache.org/jira/browse/HIVE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-846. --- Resolution: Duplicate This will get covered in HIVE-2496 > move hive tables from one database to another > - > > Key: HIVE-846 > URL: https://issues.apache.org/jira/browse/HIVE-846 > Project: Hive > Issue Type: New Feature >Reporter: Namit Jain > > The support for moving tables from one database to another is not present -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-465) support alter partition from CLI
[ https://issues.apache.org/jira/browse/HIVE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-465. --- Resolution: Fixed Partitions can be resolved according to the ddl in https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-AlterTable%2FPartitionStatements > support alter partition from CLI > > > Key: HIVE-465 > URL: https://issues.apache.org/jira/browse/HIVE-465 > Project: Hive > Issue Type: New Feature > Components: Metastore >Reporter: Prasad Chakka > > HIVE-464 adds support for alter partition in metastore interface. this JIRA > is to expose that interface through CLI similar to that of 'alter table ...' > @Prasad - not a blocker for 0.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-788) Triggers when a new partition is created for a table
[ https://issues.apache.org/jira/browse/HIVE-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-788. --- Resolution: Fixed Fix Version/s: 0.8.0 This is taken care of in HIVE-2038 > Triggers when a new partition is created for a table > > > Key: HIVE-788 > URL: https://issues.apache.org/jira/browse/HIVE-788 > Project: Hive > Issue Type: New Feature >Reporter: Zheng Shao > Fix For: 0.8.0 > > > One requirement for HIVE-787 is that users would like to run a command > whenever a new partition of a Hive table gets created. > There are several ways to achieve this functionality: > A. Probe and wait: We can have the scripts running in a loop checking if a > new partition is created. > Pros: easy to write, easy to control > Cons: will introduce another delay based on the probing interval. > B. Triggered: The command is registered inside the hive metastore. Whenever a > partition gets created, we run the registered command. > Several questions around option B are: > 1. whether to support registration of HiveQL or shell command; > 2. which machine/environment to run the command; > 3. what to do if the registered command failed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-112) support for compacting the number of files not present
[ https://issues.apache.org/jira/browse/HIVE-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-112. --- Resolution: Fixed Fix Version/s: 0.6.0 I think HIVE-1332 fixes this. If not, please reopen providing details about what else needs to be done. > support for compacting the number of files not present > -- > > Key: HIVE-112 > URL: https://issues.apache.org/jira/browse/HIVE-112 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Namit Jain > Fix For: 0.6.0 > > > There should be support for compacting the number of files for a > table/partition. > For example: the following syntax might be OK: > alter table partition compact; > We can optionally provide the number of files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1618) Expression in sort by throws NPE
[ https://issues.apache.org/jira/browse/HIVE-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1618. Resolution: Cannot Reproduce No longer a problem on trunk. Error message is: FAILED: Error in semantic analysis: functions are not supported in order by > Expression in sort by throws NPE > > > Key: HIVE-1618 > URL: https://issues.apache.org/jira/browse/HIVE-1618 > Project: Hive > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Paul Yang > > A query such as: > SELECT count(1) FROM src SORT BY count(1); > Will throw a null pointer exception: > 2010-09-07 15:27:27,059 ERROR ql.Driver (SessionState.java:printError(277)) - > FAILED: Hive Internal Error: java.lang.NullPointerException(null) > java.lang.NullPointerException > at > org.apache.hadoop.hive.ql.plan.ExprNodeGenericFuncDesc.newInstance(ExprNodeGenericFuncDesc.java:153) > at > org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.getXpathOrFuncExprNodeDesc(TypeCheckProcFactory.java:587) > at > org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:708) > at > org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:89) > at > org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatch(DefaultGraphWalker.java:88) > at > org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.walk(DefaultGraphWalker.java:128) > at > org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.startWalking(DefaultGraphWalker.java:102) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:6418) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genReduceSinkPlan(SemanticAnalyzer.java:4029) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genBodyPlan(SemanticAnalyzer.java:5148) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:5661) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:6229) > at > org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:240) > at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:326) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1706) Support BLOB data type
[ https://issues.apache.org/jira/browse/HIVE-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1706. Resolution: Duplicate This got resolved as a part of HIVE-2380 > Support BLOB data type > -- > > Key: HIVE-1706 > URL: https://issues.apache.org/jira/browse/HIVE-1706 > Project: Hive > Issue Type: Improvement > Components: Serializers/Deserializers >Affects Versions: 0.7.0 >Reporter: Ted Yu > > Quite often, we want to import blob data type from mysql/SQL Server to Hive. > Currently we either have to store BLOB data in HBase or pass the data as > base64 encoded string. Neither of which is efficient. > We should support byte array as native data type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-830) disable hive.optimize.ppd
[ https://issues.apache.org/jira/browse/HIVE-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-830. --- Resolution: Not A Problem In trunk, it is on by default. Closing the ticket. > disable hive.optimize.ppd > - > > Key: HIVE-830 > URL: https://issues.apache.org/jira/browse/HIVE-830 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Namit Jain > > Predicate pushdown has been running for some time, and seems reasonably > stable. > The new partition pruner depends on that - we should not let the use disale > it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1243) CombineHiveInputFormat breaks.
[ https://issues.apache.org/jira/browse/HIVE-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1243. Resolution: Cannot Reproduce Closing as no longer reproducible on trunk. > CombineHiveInputFormat breaks. > -- > > Key: HIVE-1243 > URL: https://issues.apache.org/jira/browse/HIVE-1243 > Project: Hive > Issue Type: Bug >Affects Versions: 0.6.0 >Reporter: He Yongqiang > > set hive.input.format = > org.apache.hadoop.hive.ql.io.CombineHiveInputFormat;set > mapred.min.split.size.per.node=8;set hive.exec.compress.output = true;set > mapred.min.split.size=256; > drop table combine1_1;create table combine1_1(key string, value string) > stored as textfile; > insert overwrite table combine1_1 select * from src; -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1730) Keep the mapping between jdbm file name with bucket file name during the compile time
[ https://issues.apache.org/jira/browse/HIVE-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1730. Resolution: Not A Problem With HIVE-1754 jdbm is removed so this is no longer relevant. > Keep the mapping between jdbm file name with bucket file name during the > compile time > - > > Key: HIVE-1730 > URL: https://issues.apache.org/jira/browse/HIVE-1730 > Project: Hive > Issue Type: Sub-task > Components: Query Processor >Affects Versions: 0.7.0 >Reporter: Liyin Tang >Assignee: Liyin Tang > > Right now, the new map join operator will figure out the jdbm file name > during the run time based some string function. > But we need to keep this mapping during the compile time, so the explain task > can understand which jdbm file the mapred task will need. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1208) Bug with error "cannot find ObjectInspector for VOID"
[
https://issues.apache.org/jira/browse/HIVE-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan resolved HIVE-1208.
Resolution: Cannot Reproduce
This is no longer reproducible on trunk.
> Bug with error "cannot find ObjectInspector for VOID"
> -
>
> Key: HIVE-1208
> URL: https://issues.apache.org/jira/browse/HIVE-1208
> Project: Hive
> Issue Type: Bug
>Reporter: Zheng Shao
>
> This happens when using constant "null", but not when using "CAST(null AS
> STRING)".
> {code}
> explain extended FROM
> (select 1 as a, null as b
> from zshao_tt
> distribute by a) tmp
> SELECT transform(a, b)
> USING 'cat';
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-919) distinct on multiple columns should be supported
[ https://issues.apache.org/jira/browse/HIVE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-919. --- Resolution: Fixed Fix Version/s: 0.7.0 This is not reproducible on trunk. Probably got fixed as part of HIVE-474 > distinct on multiple columns should be supported > > > Key: HIVE-919 > URL: https://issues.apache.org/jira/browse/HIVE-919 > Project: Hive > Issue Type: New Feature >Reporter: Namit Jain > Fix For: 0.7.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-1866) -101 should not swallow the exception.
[ https://issues.apache.org/jira/browse/HIVE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-1866. Resolution: Fixed Fix Version/s: 0.7.0 As per Ning's comments this has been fixed. Marking resolved. > -101 should not swallow the exception. > --- > > Key: HIVE-1866 > URL: https://issues.apache.org/jira/browse/HIVE-1866 > Project: Hive > Issue Type: Improvement >Reporter: He Yongqiang > Fix For: 0.7.0 > > > The exception stack trace will be good to have for debug purpose. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-2407) File extensions not preserved in Hive.checkPaths when renaming new destination file
[ https://issues.apache.org/jira/browse/HIVE-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan resolved HIVE-2407. Resolution: Fixed Fix Version/s: 0.8.0 This got fixed as part of HIVE-2296. > File extensions not preserved in Hive.checkPaths when renaming new > destination file > --- > > Key: HIVE-2407 > URL: https://issues.apache.org/jira/browse/HIVE-2407 > Project: Hive > Issue Type: Bug >Affects Versions: 0.7.1 >Reporter: Brian Muller > Fix For: 0.8.0 > > > In the checkPaths method of Hive.java, a new destination filename will be > chosen if the source filename already exists in the destination directory. > This new filename follows the simple schema of adding _copy_N to the source > filename (with increasing N until a non-existing filename is found). > If the file has been LZO compressed it is imperative that the extension > remain ".lzo" so that the LZO indexer can find it and create a corresponding > index file. It would be much better to use a prefix of "copy_N_" or insert > "_copy_N" somewhere else in the filename. > Without this, Hive and LZO compression will not work when identical source > filenames are inserted into Hive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
