[jira] [Updated] (HIVE-2957) Hive JDBC doesn't support TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2957: --- Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > Hive JDBC doesn't support TIMESTAMP column > -- > > Key: HIVE-2957 > URL: https://issues.apache.org/jira/browse/HIVE-2957 > Project: Hive > Issue Type: Bug > Components: JDBC >Affects Versions: 0.8.1, 0.9.0 >Reporter: Bharath Ganesh >Assignee: Bharath Ganesh >Priority: Minor > Attachments: HIVE-2957.patch > > > Steps to replicate: > 1. Create a table with at least one column of type TIMESTAMP > 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is > part of the resultset. > 3. When you iterate over the TIMESTAMP column it would fail, throwing the > below exception: > Exception in thread "main" java.sql.SQLException: Unrecognized column type: > timestamp > at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) > at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) > at > org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2859) STRING data corruption in internationalized data -- based on LANG env variable
[ https://issues.apache.org/jira/browse/HIVE-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2859: --- Affects Version/s: 0.9.0 0.8.0 0.8.1 Fix Version/s: (was: 0.9.0) (was: 0.7.1) Unlinking from 0.9 > STRING data corruption in internationalized data -- based on LANG env variable > -- > > Key: HIVE-2859 > URL: https://issues.apache.org/jira/browse/HIVE-2859 > Project: Hive > Issue Type: Bug > Components: Configuration, Import/Export, Serializers/Deserializers, > Types >Affects Versions: 0.7.1, 0.8.0, 0.8.1, 0.9.0 > Environment: Windows / RHEL5 with LANG = en_US.CP1252 >Reporter: John Gordon > Original Estimate: 6h > Remaining Estimate: 6h > > This is a bug in Hive that is exacerbated by replatforming it to Windows > without CYGWIN. Basically, it assumes that the default file.encoding is > UTF8. There are something like 6-7 getBytes() calls and write() calls that > don't specify the encoding. The rest specify UTF-8 explicitly, which blocks > auto-detection of UTF-16 data in files with a BOM present. The mix of > explicit encodings and default encoding assumptions means that Hive must be > run in a JVM whose default encoding is UTF-8 and only UTF-8. > > When the JVM starts up, it derives the default encoding from the C runtime > setlocale() call. On Linux/Unix, this would use the LANG env variable (which > is almost always .UTF8 for machines handling internationalized data, > but not guaranteed to be so). On Windows, this is derived from the user's > language settings, and cannot return a UTF-8 encoding, right now. So there > isn't an environment setting for Windows that would reliably provide the JVM > with a set of inputs to cause it to set the default encoding to UTF-8 on > startup without additional options. > However, there are 2 feasible options: > 1.) the JVM has a startup option -Dfile.encoding=UTF-8 which should > explicitly override the default encoding detection behavior in the JVM to > make it always UTF-8 regardless of the environmental configuration. This > would make all deployments on all OS/environment configs behave consistently. > I don't know where Hive sets the JVM options we use when it starts the > service. > 2.) We could add "UTF8" explicitly to all the remaining getBytes() calls that > need it, and make all the string I/O explicitly UTF-8 encoded. This is > probably being changed right now as part of Hive-1505, so we would duplicate > effort and maybe make that change harder. Seems easier to trick the JVM into > behaving like it is on a well-configured machine WRT default encoding instead > of setting explicit encodings everywhere. > > So: > - Pretty much any globalized strings than Western European are going to > be corrupted in the current Hive service on Windows with this bug present > because there really isn't a way to have the JVM read the environment and > determine by default that UTF8 should be the default encoding. > - Anyone can repro this on Linux fairly easily -- Add "export > LANG=en_US.CP1252" to /etc/profile to modify the global LANG default encoding > to CP1252 explicitly, then restart the service and do a query over > internationalized UTF-8 data. > - We shouldn't rely on JVM default codepage selection if we want to > support UTF-8 consistently and reliably as the default encoding. > - The estimate can range wildly, but adding an explicit default > encoding on startup should only take a little while if you know where to do > it, theoretically. > - I don't know where to update the start arguments of the JVM when the > service is started, just getting into the code for the first time with this > bug investigation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2860) TestNegativeCliDriver autolocal1.q fails on 0.23
[ https://issues.apache.org/jira/browse/HIVE-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2860: --- Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > TestNegativeCliDriver autolocal1.q fails on 0.23 > > > Key: HIVE-2860 > URL: https://issues.apache.org/jira/browse/HIVE-2860 > Project: Hive > Issue Type: Bug > Components: Testing Infrastructure >Affects Versions: 0.9.0 >Reporter: Carl Steinbach >Assignee: Carl Steinbach > Attachments: HIVE-2860.D2253.1.patch, HIVE-2860.D2253.1.patch, > HIVE-2860.D2565.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] [Updated] (HIVE-2839) Filters on outer join with mapjoin hint is not applied correctly
[
https://issues.apache.org/jira/browse/HIVE-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2839:
---
Affects Version/s: 0.9.0
Fix Version/s: (was: 0.9.0)
Unlinking from 0.9
> Filters on outer join with mapjoin hint is not applied correctly
>
>
> Key: HIVE-2839
> URL: https://issues.apache.org/jira/browse/HIVE-2839
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Affects Versions: 0.9.0
>Reporter: Navis
>Assignee: Navis
>Priority: Minor
> Attachments: HIVE-2839.D2079.1.patch, HIVE-2839.D2079.2.patch
>
>
> Testing HIVE-2820, I've found some queries with mapjoin hint makes exceptions.
> {code}
> SELECT /*+ MAPJOIN(a) */ * FROM src a RIGHT OUTER JOIN src b on a.key=b.key
> AND true limit 10;
> FAILED: Hive Internal Error:
> java.lang.ClassCastException(org.apache.hadoop.hive.ql.plan.ExprNodeConstantDesc
> cannot be cast to org.apache.hadoop.hive.ql.plan.ExprNodeGenericFuncDesc)
> java.lang.ClassCastException:
> org.apache.hadoop.hive.ql.plan.ExprNodeConstantDesc cannot be cast to
> org.apache.hadoop.hive.ql.plan.ExprNodeGenericFuncDesc
> at
> org.apache.hadoop.hive.ql.optimizer.MapJoinProcessor.convertMapJoin(MapJoinProcessor.java:363)
> at
> org.apache.hadoop.hive.ql.optimizer.MapJoinProcessor.generateMapJoinOperator(MapJoinProcessor.java:483)
> at
> org.apache.hadoop.hive.ql.optimizer.MapJoinProcessor.transform(MapJoinProcessor.java:689)
> at
> org.apache.hadoop.hive.ql.optimizer.Optimizer.optimize(Optimizer.java:87)
> at
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:7519)
> at
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:250)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:431)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:336)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:891)
> 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:186)
> {code}
> and
> {code}
> SELECT /*+ MAPJOIN(a) */ * FROM src a RIGHT OUTER JOIN src b on a.key=b.key
> AND b.key * 10 < '1000' limit 10;
> java.lang.RuntimeException: org.apache.hadoop.hive.ql.metadata.HiveException
> at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:161)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:50)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:391)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:325)
> at org.apache.hadoop.mapred.Child$4.run(Child.java:270)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:416)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
> at org.apache.hadoop.mapred.Child.main(Child.java:264)
> Caused by: org.apache.hadoop.hive.ql.metadata.HiveException
> at
> org.apache.hadoop.hive.ql.exec.MapJoinOperator.loadHashTable(MapJoinOperator.java:198)
> at
> org.apache.hadoop.hive.ql.exec.MapJoinOperator.cleanUpInputFileChangedOp(MapJoinOperator.java:212)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1321)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1325)
> at
> org.apache.hadoop.hive.ql.exec.Operator.cleanUpInputFileChanged(Operator.java:1325)
> at
> org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:495)
> at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:143)
> ... 8 more
> {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] [Updated] (HIVE-2820) Invalid tag is used for MapJoinProcessor
[
https://issues.apache.org/jira/browse/HIVE-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2820:
---
Fix Version/s: (was: 0.9.0)
Unlinking from 0.9
> Invalid tag is used for MapJoinProcessor
>
>
> Key: HIVE-2820
> URL: https://issues.apache.org/jira/browse/HIVE-2820
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Affects Versions: 0.9.0
> Environment: ubuntu
>Reporter: Navis
>Assignee: Navis
> Attachments: HIVE-2820.D1935.1.patch, HIVE-2820.D1935.2.patch,
> HIVE-2820.D1935.3.patch
>
>
> Testing HIVE-2810, I've found tag and alias are used in very confusing
> manner. For example, query below fails..
> {code}
> hive> set hive.auto.convert.join=true;
>
> hive> select /*+ STREAMTABLE(a) */ * from myinput1 a join myinput1 b on
> a.key=b.key join myinput1 c on a.key=c.key;
> Total MapReduce jobs = 4
> Ended Job = 1667415037, job is filtered out (removed at runtime).
> Ended Job = 1739566906, job is filtered out (removed at runtime).
> Ended Job = 1113337780, job is filtered out (removed at runtime).
> 12/02/24 10:27:14 WARN conf.HiveConf: DEPRECATED: Ignoring hive-default.xml
> found on the CLASSPATH at /home/navis/hive/conf/hive-default.xml
> Execution log at:
> /tmp/navis/navis_20120224102727_cafe0d8d-9b21-441d-bd4e-b83303b31cdc.log
> 2012-02-24 10:27:14 Starting to launch local task to process map join;
> maximum memory = 932118528
> java.lang.NullPointerException
> at
> org.apache.hadoop.hive.ql.exec.HashTableSinkOperator.processOp(HashTableSinkOperator.java:312)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:762)
> at
> org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:83)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at
> org.apache.hadoop.hive.ql.exec.MapredLocalTask.startForward(MapredLocalTask.java:325)
> at
> org.apache.hadoop.hive.ql.exec.MapredLocalTask.executeFromChildJVM(MapredLocalTask.java:272)
> at org.apache.hadoop.hive.ql.exec.ExecDriver.main(ExecDriver.java:685)
> 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:186)
> Execution failed with exit status: 2
> Obtaining error information
> {code}
> Failed task has a plan which doesn't make sense.
> {noformat}
> Stage: Stage-8
> Map Reduce Local Work
> Alias -> Map Local Tables:
> b
> Fetch Operator
> limit: -1
> c
> Fetch Operator
> limit: -1
> Alias -> Map Local Operator Tree:
> b
> TableScan
> alias: b
> HashTable Sink Operator
> condition expressions:
> 0 {key} {value}
> 1 {key} {value}
> 2 {key} {value}
> handleSkewJoin: false
> keys:
> 0 [Column[key]]
> 1 [Column[key]]
> 2 [Column[key]]
> Position of Big Table: 0
> c
> TableScan
> alias: c
> Map Join Operator
> condition map:
>Inner Join 0 to 1
>Inner Join 0 to 2
> condition expressions:
> 0 {key} {value}
> 1 {key} {value}
> 2 {key} {value}
> handleSkewJoin: false
> keys:
> 0 [Column[key]]
> 1 [Column[key]]
> 2 [Column[key]]
> outputColumnNames: _col0, _col1, _col4, _col5, _col8, _col9
> Position of Big Table: 0
> Select Operator
> expressions:
> expr: _col0
> type: int
> expr: _col1
> type: int
> expr: _col4
> type: int
> expr: _col5
> type: int
> expr: _col8
> type: int
> expr: _col9
> type: int
> outputColumnNames: _col0, _col1, _col2, _col3, _col4, _col5
> File Output Operator
> compressed: false
>
[jira] [Updated] (HIVE-2736) Hive UDFs cannot emit binary constants
[ https://issues.apache.org/jira/browse/HIVE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2736: --- Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > Hive UDFs cannot emit binary constants > -- > > Key: HIVE-2736 > URL: https://issues.apache.org/jira/browse/HIVE-2736 > Project: Hive > Issue Type: Bug > Components: Query Processor, Serializers/Deserializers, UDF >Affects Versions: 0.9.0 >Reporter: Philip Tromans >Assignee: Philip Tromans >Priority: Minor > Labels: newbie > Attachments: HIVE-2736.1.patch.txt, HIVE-2736.2.patch.txt > > Original Estimate: 4h > Remaining Estimate: 4h > > I recently wrote a UDF which emits BINARY values (as implemented in > [HIVE-2380|https://issues.apache.org/jira/browse/HIVE-2380]). When testing > this, I encountered the following exception (because I was evaluating > f(g(constant string))) and g() was emitting a BytesWritable type. > FAILED: Hive Internal Error: java.lang.RuntimeException(Internal error: > Cannot find ConstantObjectInspector for BINARY) > java.lang.RuntimeException: Internal error: Cannot find > ConstantObjectInspector for BINARY > at > org.apache.hadoop.hive.serde2.objectinspector.primitive.PrimitiveObjectInspectorFactory.getPrimitiveWritableConstantObjectInspector(PrimitiveObjectInspectorFactory.java:196) > at > org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorUtils.getConstantObjectInspector(ObjectInspectorUtils.java:899) > at > org.apache.hadoop.hive.ql.udf.generic.GenericUDF.initializeAndFoldConstants(GenericUDF.java:128) > at > org.apache.hadoop.hive.ql.plan.ExprNodeGenericFuncDesc.newInstance(ExprNodeGenericFuncDesc.java:214) > at > org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.getXpathOrFuncExprNodeDesc(TypeCheckProcFactory.java:684) > at > org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:805) > 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:125) > at > org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.startWalking(DefaultGraphWalker.java:102) > at > org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory.genExprNode(TypeCheckProcFactory.java:161) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:7708) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genSelectPlan(SemanticAnalyzer.java:2301) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genSelectPlan(SemanticAnalyzer.java:2103) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPostGroupByBodyPlan(SemanticAnalyzer.java:6126) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genBodyPlan(SemanticAnalyzer.java:6097) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:6723) > at > org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:7484) > at > org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:243) > at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:430) > at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:337) > at org.apache.hadoop.hive.ql.Driver.run(Driver.java:889) > at > org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:255) > at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:212) > at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:403) > at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:671) > at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:554) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.hadoop.util.RunJar.main(RunJar.java:156) > It looks like a pretty simple fix - add a case for BINARY in > PrimitiveObjectInspectorFactory.getPrimitiveWritableConstantObjectInspector() > and implement a WritableConstantByteArrayObjectInspector class (almost > identical to the others). I'm happy to do this, although this is my first > foray into the world of contributing to FOSS so I might end up asking a few > stupid questions. -- This message is automatically generated by J
[jira] [Updated] (HIVE-2723) should throw "Ambiguous column reference key" Exception in particular join condition
[ https://issues.apache.org/jira/browse/HIVE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2723: --- Affects Version/s: 0.9.0 Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > should throw "Ambiguous column reference key" Exception in particular join > condition > -- > > Key: HIVE-2723 > URL: https://issues.apache.org/jira/browse/HIVE-2723 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.9.0 > Environment: Linux zongren-VirtualBox 3.0.0-14-generic #23-Ubuntu SMP > Mon Nov 21 20:34:47 UTC 2011 i686 i686 i386 GNU/Linux > java version "1.6.0_25" > hadoop-0.20.2-cdh3u0 > hive-0.7.0-cdh3u0 >Reporter: caofangkun >Assignee: Navis >Priority: Minor > Labels: exception-handling, query, queryparser > Attachments: HIVE-2723.D1275.1.patch, HIVE-2723.D1275.2.patch > > > This Bug can be Repeated as following : > create table test(key string, value string); > create table test1(key string, value string); > 1: Correct! > select t.key > from > (select a.key, b.key from (select * from src ) a right outer join (select * > from src1) b on (a.key = b.key)) t; > FAILED: Error in semantic analysis: Ambiguous column reference key > 2: Uncorrect!! Should throw Exception as above too! > select t.key --Is this a.key or b.key ? It's ambiduous! > from > (select a.\*, b.\* from (select * from src ) a right outer join (select * > from src1) b on (a.value = b.value)) t; > Total MapReduce jobs = 1 > Launching Job 1 out of 1 > Number of reduce tasks not specified. Defaulting to jobconf value of: 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_201201170959_0004, Tracking URL = > http://zongren-VirtualBox:50030/jobdetails.jsp?jobid=job_201201170959_0004 > Kill Command = /home/zongren/workspace/hadoop-adh/bin/hadoop job > -Dmapred.job.tracker=zongren-VirtualBox:9001 -kill job_201201170959_0004 > Hadoop job information for Stage-1: number of mappers: 2; number of reducers: > 1 > 2012-01-17 11:02:47,507 Stage-1 map = 0%, reduce = 0% > 2012-01-17 11:02:55,002 Stage-1 map = 100%, reduce = 0% > 2012-01-17 11:03:04,240 Stage-1 map = 100%, reduce = 33% > 2012-01-17 11:03:05,258 Stage-1 map = 100%, reduce = 100% > Ended Job = job_201201170959_0004 > MapReduce Jobs Launched: > Job 0: Map: 2 Reduce: 1 HDFS Read: 669 HDFS Write: 216 SUCESS > Total MapReduce CPU Time Spent: 0 msec > OK -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2715) Upgrade Thrift dependency to 0.9.0
[ https://issues.apache.org/jira/browse/HIVE-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2715: --- Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > Upgrade Thrift dependency to 0.9.0 > -- > > Key: HIVE-2715 > URL: https://issues.apache.org/jira/browse/HIVE-2715 > Project: Hive > Issue Type: Bug > Components: Metastore >Affects Versions: 0.8.0 >Reporter: Mithun Radhakrishnan > > I work on HCatalog (0.2). Recently, we ran into HCat_server running out of > memory every few days, and it boiled down to a bug in thrift, (THRIFT-1468, > recently fixed). > HCat-0.2-branch depends on Hive-0.8, which in turn depends on thrift-0.5.0. > (The bug also exists on 0.7.0.) > May I please enquire if Hive can't depend on a more current version of > thrift? (Does it break the metastore?) I'm afraid I'm not privy to the > reasoning behind Hive's dependency on a slightly dated thrift-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] [Updated] (HIVE-2679) ctas should check the table do not exists just right before move the data to the table's directory
[ https://issues.apache.org/jira/browse/HIVE-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2679: --- Component/s: Query Processor Metastore Affects Version/s: 0.9.0 Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > ctas should check the table do not exists just right before move the data to > the table's directory > --- > > Key: HIVE-2679 > URL: https://issues.apache.org/jira/browse/HIVE-2679 > Project: Hive > Issue Type: Bug > Components: Metastore, Query Processor >Affects Versions: 0.9.0 >Reporter: binlijin > Attachments: hive-2679.patch > > > Some one first runs a ctas sql and the MR job takes a long time, another one > runs another ctas sql and the MR job takes a short time and finishs before > the first one. when the two ctas sql's tablename are the same, the first one > will move data to the table's directory success but the create table task > will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2586) Float comparison doesn't work
[ https://issues.apache.org/jira/browse/HIVE-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2586: --- Affects Version/s: 0.9.0 Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > Float comparison doesn't work > - > > Key: HIVE-2586 > URL: https://issues.apache.org/jira/browse/HIVE-2586 > Project: Hive > Issue Type: Bug >Affects Versions: 0.9.0 >Reporter: Robert Surówka >Assignee: Navis >Priority: Minor > Attachments: HIVE-2586.1.patch.txt > > > Create table with float column, insert to it e.g. 1410.1, and then do select > * from where = 1410.1 . Nothing will be found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2544) Nullpointer on registering udfs.
[ https://issues.apache.org/jira/browse/HIVE-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2544: --- Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > Nullpointer on registering udfs. > > > Key: HIVE-2544 > URL: https://issues.apache.org/jira/browse/HIVE-2544 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.9.0 >Reporter: Bennie Schut >Assignee: Bennie Schut > Attachments: HIVE-2544.1.patch.txt > > > Currently the Function registry can throw NullPointers when multiple threads > are trying to register the same function. The normal put() will replace the > existing registered function object even if it's exactly the same function. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2498) Group by operator doesnt estimate size of Timestamp & Binary data correctly
[ https://issues.apache.org/jira/browse/HIVE-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2498: --- Affects Version/s: 0.9.0 Fix Version/s: (was: 0.9.0) Unlinking from 0.9 > Group by operator doesnt estimate size of Timestamp & Binary data correctly > --- > > Key: HIVE-2498 > URL: https://issues.apache.org/jira/browse/HIVE-2498 > Project: Hive > Issue Type: Bug >Affects Versions: 0.8.0, 0.8.1, 0.9.0 >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2498.D1185.1.patch, hive-2498.patch, > hive-2498_1.patch > > > It currently defaults to default case and returns constant value, whereas we > can do better by getting actual size at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2332) If all of the parameters of distinct functions are exists in group by columns, query fails in runtime
[
https://issues.apache.org/jira/browse/HIVE-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2332:
---
Affects Version/s: 0.9.0
Fix Version/s: (was: 0.9.0)
Unlinking from 0.9
> If all of the parameters of distinct functions are exists in group by
> columns, query fails in runtime
> -
>
> Key: HIVE-2332
> URL: https://issues.apache.org/jira/browse/HIVE-2332
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Affects Versions: 0.9.0
>Reporter: Navis
>Assignee: Navis
>Priority: Critical
> Attachments: HIVE-2332.1.patch.txt, HIVE-2332.2.patch.txt,
> HIVE-2332.D663.1.patch
>
>
> select sum(key_int1), sum(distinct key_int1) from t1 group by key_int1;
> fails with message..
> {code}
> FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.MapRedTask
> {code}
> hadoop says..
> {code}
> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at
> org.apache.hadoop.hive.serde2.objectinspector.StandardStructObjectInspector.init(StandardStructObjectInspector.java:95)
> at
> org.apache.hadoop.hive.serde2.objectinspector.StandardStructObjectInspector.(StandardStructObjectInspector.java:86)
> at
> org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorFactory.getStandardStructObjectInspector(ObjectInspectorFactory.java:252)
> at
> org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.initEvaluatorsAndReturnStruct(ReduceSinkOperator.java:188)
> at
> org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.processOp(ReduceSinkOperator.java:197)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:85)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:532)
> {code}
> I think the deficient number of key expression, compared to number of key
> column, is the problem, which should be equal or more.
> Would it be solved if add some key expression? I'll try.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2264) Hive server is SHUTTING DOWN when invalid queries beeing executed.
[
https://issues.apache.org/jira/browse/HIVE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2264:
---
Fix Version/s: (was: 0.9.0)
Unlinking from 0.9
> Hive server is SHUTTING DOWN when invalid queries beeing executed.
> --
>
> Key: HIVE-2264
> URL: https://issues.apache.org/jira/browse/HIVE-2264
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Affects Versions: 0.9.0
> Environment: SuSE-Linux-11
>Reporter: rohithsharma
>Assignee: Navis
>Priority: Critical
> Attachments: HIVE-2264.1.patch.txt
>
>
> When invalid query is beeing executed, Hive server is shutting down.
> {noformat}
> "CREATE TABLE SAMPLETABLE(IP STRING , showtime BIGINT ) partitioned by (ds
> string,ipz int) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\040'"
> "ALTER TABLE SAMPLETABLE add Partition(ds='sf') location
> '/user/hive/warehouse' Partition(ipz=100) location '/user/hive/warehouse'"
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2965) Revert HIVE-2612
[ https://issues.apache.org/jira/browse/HIVE-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2965: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 0.9 > Revert HIVE-2612 > > > Key: HIVE-2965 > URL: https://issues.apache.org/jira/browse/HIVE-2965 > Project: Hive > Issue Type: Task >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan >Priority: Blocker > Fix For: 0.9.0 > > Attachments: hive-2765.patch > > > In 4/19 contrib meeting it was decided to revert HIVE-2612. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2958) GROUP BY causing ClassCastException [LazyDioInteger cannot be cast LazyInteger]
[
https://issues.apache.org/jira/browse/HIVE-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2958:
---
Resolution: Fixed
Fix Version/s: 0.9.0
Status: Resolved (was: Patch Available)
Committed to trunk and 0.9. Thanks, Navis!
> GROUP BY causing ClassCastException [LazyDioInteger cannot be cast
> LazyInteger]
> ---
>
> Key: HIVE-2958
> URL: https://issues.apache.org/jira/browse/HIVE-2958
> Project: Hive
> Issue Type: Bug
> Components: HBase Handler
>Affects Versions: 0.9.0
> Environment: HBase 0.90.4, Hive 0.90 snapshot (trunk) built today
>Reporter: Tim Robertson
>Assignee: Navis
>Priority: Blocker
> Fix For: 0.9.0
>
> Attachments: HIVE-2958.D2871.1.patch
>
>
> This relates to https://issues.apache.org/jira/browse/HIVE-1634.
> The following work fine:
> {code}
> CREATE EXTERNAL TABLE tim_hbase_occurrence (
> id int,
> scientific_name string,
> data_resource_id int
> ) STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' WITH
> SERDEPROPERTIES (
> "hbase.columns.mapping" = ":key#b,v:scientific_name#s,v:data_resource_id#b"
> ) TBLPROPERTIES(
> "hbase.table.name" = "mini_occurrences",
> "hbase.table.default.storage.type" = "binary"
> );
> SELECT * FROM tim_hbase_occurrence LIMIT 3;
> SELECT * FROM tim_hbase_occurrence WHERE data_resource_id=1081 LIMIT 3;
> {code}
> However, the following fails:
> {code}
> SELECT data_resource_id, count(*) FROM tim_hbase_occurrence GROUP BY
> data_resource_id;
> {code}
> The error given:
> {code}
> 0 TS
> 2012-04-17 16:58:45,693 INFO org.apache.hadoop.hive.ql.exec.MapOperator:
> Initialization Done 7 MAP
> 2012-04-17 16:58:45,714 INFO org.apache.hadoop.hive.ql.exec.MapOperator:
> Processing alias tim_hbase_occurrence for file
> hdfs://c1n2.gbif.org/user/hive/warehouse/tim_hbase_occurrence
> 2012-04-17 16:58:45,714 INFO org.apache.hadoop.hive.ql.exec.MapOperator: 7
> forwarding 1 rows
> 2012-04-17 16:58:45,714 INFO
> org.apache.hadoop.hive.ql.exec.TableScanOperator: 0 forwarding 1 rows
> 2012-04-17 16:58:45,716 INFO org.apache.hadoop.hive.ql.exec.SelectOperator: 1
> forwarding 1 rows
> 2012-04-17 16:58:45,723 FATAL ExecMapper:
> org.apache.hadoop.hive.ql.metadata.HiveException: Hive Runtime Error while
> processing row {"id":1444,"scientific_name":null,"data_resource_id":1081}
> at
> org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:548)
> at org.apache.hadoop.hive.ql.exec.ExecMapper.map(ExecMapper.java:143)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:50)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:391)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:325)
> at org.apache.hadoop.mapred.Child$4.run(Child.java:270)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:396)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1157)
> at org.apache.hadoop.mapred.Child.main(Child.java:264)
> Caused by: org.apache.hadoop.hive.ql.metadata.HiveException:
> java.lang.ClassCastException:
> org.apache.hadoop.hive.serde2.lazydio.LazyDioInteger cannot be cast to
> org.apache.hadoop.hive.serde2.lazy.LazyInteger
> at
> org.apache.hadoop.hive.ql.exec.GroupByOperator.processOp(GroupByOperator.java:737)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:762)
> at
> org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:84)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:762)
> at
> org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:83)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:762)
> at
> org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:529)
> ... 9 more
> Caused by: java.lang.ClassCastException:
> org.apache.hadoop.hive.serde2.lazydio.LazyDioInteger cannot be cast to
> org.apache.hadoop.hive.serde2.lazy.LazyInteger
> at
> org.apache.hadoop.hive.serde2.lazy.objectinspector.primitive.LazyIntObjectInspector.copyObject(LazyIntObjectInspector.java:43)
> at
> org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorUtils.copyToStandardObject(ObjectInspectorUtils.java:239)
> at
> org.apache.hadoop.hive.ql.exec.KeyWrapperFactory$ListKeyWrapper.deepCopyElements(KeyWrapperFactory.java:1
[jira] [Updated] (HIVE-2965) Revert HIVE-2612
[ https://issues.apache.org/jira/browse/HIVE-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2965: --- Status: Patch Available (was: Open) Ready for review. > Revert HIVE-2612 > > > Key: HIVE-2965 > URL: https://issues.apache.org/jira/browse/HIVE-2965 > Project: Hive > Issue Type: Task >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan >Priority: Blocker > Fix For: 0.9.0 > > Attachments: hive-2765.patch > > > In 4/19 contrib meeting it was decided to revert HIVE-2612. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2965) Revert HIVE-2612
[ https://issues.apache.org/jira/browse/HIVE-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2965: --- Attachment: hive-2765.patch Arc is unwieldy again. Can't convince it to submit the patch. So, uploading directly, patch reverting HIVE-2612 generated using svn merge command. > Revert HIVE-2612 > > > Key: HIVE-2965 > URL: https://issues.apache.org/jira/browse/HIVE-2965 > Project: Hive > Issue Type: Task >Reporter: Ashutosh Chauhan >Priority: Blocker > Fix For: 0.9.0 > > Attachments: hive-2765.patch > > > In 4/19 contrib meeting it was decided to revert HIVE-2612. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2961) Remove need for storage descriptors for view partitions
[ https://issues.apache.org/jira/browse/HIVE-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2961: --- Status: Open (was: Patch Available) Canceling patch since current patch may not be valid after HIVE-2795 is reverted. > Remove need for storage descriptors for view partitions > --- > > Key: HIVE-2961 > URL: https://issues.apache.org/jira/browse/HIVE-2961 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.9.0 >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2961.D2877.1.patch > > > Storage descriptors were introduced for view partitions as part of HIVE-2795. > This was to allow view partitions to have the concept of a region as well as > to fix a NPE that resulted from calling describe formatted on them. > Since regions are no longer necessary for view partitions and the NPE can be > fixed by not displaying storage information for view partitions (or > displaying the view's storage information if this is preferred, although, > since a view partition is purely metadata, this does not seem necessary), > these are no longer needed. > This also means the Python script added which retroactively adds storage > descriptors to existing view partitions can be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2902) undefined property exists in eclipse-templates/.classpath
[
https://issues.apache.org/jira/browse/HIVE-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2902:
---
Assignee: tamtam180
Status: Open (was: Patch Available)
You also need to add jackson-core and jackson-mapper jars in the classpath
> undefined property exists in eclipse-templates/.classpath
> -
>
> Key: HIVE-2902
> URL: https://issues.apache.org/jira/browse/HIVE-2902
> Project: Hive
> Issue Type: Bug
> Components: Build Infrastructure
>Reporter: tamtam180
>Assignee: tamtam180
>Priority: Minor
> Attachments: HIVE-2902.1.patch.txt
>
>
> @hbase-test.version@ was removed from ivy/libraries.properties in HIVE-2748,
> but the property still exists in eclipse-templates/.classpath.
> {code}
>
> path="build/ivy/lib/default/hbase-@hbase-test.vers...@-tests.jar"/>
> {code}
> It should be changed to @hbase.version@
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2959) TestRemoteHiveMetaStoreIpAddress always uses the same port
[ https://issues.apache.org/jira/browse/HIVE-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2959: --- Resolution: Fixed Fix Version/s: 0.10 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Kevin! > TestRemoteHiveMetaStoreIpAddress always uses the same port > -- > > Key: HIVE-2959 > URL: https://issues.apache.org/jira/browse/HIVE-2959 > Project: Hive > Issue Type: Test >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.10 > > Attachments: HIVE-2959.D2841.1.patch > > > TestRemoteHiveMetaStoreIpAddress always uses the same port, meaning that if > another process happens to be using that port, the tests cannot succeed. > There seems to be a standard way of finding a free port using Java's > ServerSocket class, this should be used instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2957) Hive JDBC doesn't support TIMESTAMP column
[ https://issues.apache.org/jira/browse/HIVE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2957: --- Status: Open (was: Patch Available) Patch needs a test case. > Hive JDBC doesn't support TIMESTAMP column > -- > > Key: HIVE-2957 > URL: https://issues.apache.org/jira/browse/HIVE-2957 > Project: Hive > Issue Type: Bug > Components: JDBC >Affects Versions: 0.8.1, 0.9.0 >Reporter: Bharath Ganesh >Assignee: Bharath Ganesh >Priority: Minor > Fix For: 0.9.0 > > Attachments: HIVE-2957.patch > > > Steps to replicate: > 1. Create a table with at least one column of type TIMESTAMP > 2. Do a DatabaseMetaData.getColumns () such that this TIMESTAMP column is > part of the resultset. > 3. When you iterate over the TIMESTAMP column it would fail, throwing the > below exception: > Exception in thread "main" java.sql.SQLException: Unrecognized column type: > timestamp > at org.apache.hadoop.hive.jdbc.Utils.hiveTypeToSqlType(Utils.java:56) > at org.apache.hadoop.hive.jdbc.JdbcColumn.getSqlType(JdbcColumn.java:62) > at > org.apache.hadoop.hive.jdbc.HiveDatabaseMetaData$2.next(HiveDatabaseMetaData.java:244) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2930) Add license to the Hive files
[ https://issues.apache.org/jira/browse/HIVE-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2930: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Thanks Owen for fixing this. Committed to 0.9 and trunk. > Add license to the Hive files > - > > Key: HIVE-2930 > URL: https://issues.apache.org/jira/browse/HIVE-2930 > Project: Hive > Issue Type: Improvement >Reporter: Owen O'Malley >Assignee: Owen O'Malley >Priority: Blocker > Fix For: 0.9.0 > > Attachments: HIVE-2930.D2835.1.patch > > > We need to clean up the RAT report to 0. Apache projects aren't supposed to > release until they have shown that all of their files have proper headers. > Note that although most of the files are just missing headers, some of them > explicitly say copyright by facebook and released under the Thrift (not > Apache) license. I'll generate a list of them, but I'd really appreciate it > if someone from facebook could in verify that they intend to license them to > Apache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2948) HiveFileFormatUtils should use Path.SEPARATOR instead of File.Separator
[ https://issues.apache.org/jira/browse/HIVE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2948: --- Fix Version/s: 0.9.0 > HiveFileFormatUtils should use Path.SEPARATOR instead of File.Separator > --- > > Key: HIVE-2948 > URL: https://issues.apache.org/jira/browse/HIVE-2948 > Project: Hive > Issue Type: Bug >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2948.D2763.1.patch > > > Because its munging hdfs paths and not OS paths. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2940) RCFileMergeMapper Prints To Standard Output Even In Silent Mode
[ https://issues.apache.org/jira/browse/HIVE-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2940: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Thiruvel! > RCFileMergeMapper Prints To Standard Output Even In Silent Mode > --- > > Key: HIVE-2940 > URL: https://issues.apache.org/jira/browse/HIVE-2940 > Project: Hive > Issue Type: Task >Affects Versions: 0.8.1, 0.9.0 >Reporter: Thiruvel Thirumoolan >Assignee: Thiruvel Thirumoolan >Priority: Trivial > Fix For: 0.10 > > Attachments: HIVE-2940.patch > > > A very minor issue. One of our users was running partition concatenate in > local mode as part of their application and this was a little noisy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2871) Add a new hook to run at the beginning and end of the Driver.run method
[ https://issues.apache.org/jira/browse/HIVE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2871: --- Fix Version/s: 0.9.0 > Add a new hook to run at the beginning and end of the Driver.run method > --- > > Key: HIVE-2871 > URL: https://issues.apache.org/jira/browse/HIVE-2871 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2871.D2331.1.patch, HIVE-2871.D2331.2.patch, > HIVE-2871.D2331.3.patch > > > Driver.run is the highest level method which all queries go through, whether > they come from Hive Server, the CLI, or any other entry. We also do not have > any hooks before the compilation method is called, and having hooks in > Driver.run would provide this. Having hooks in Driver.run will allow, for > example, being able to overwrite config values used throughout query > processing, including compilation, and at the other end, cleaning up any > resources/logging any final values just before returning to the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2823) Add logging of total run time of Driver
[ https://issues.apache.org/jira/browse/HIVE-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2823: --- Fix Version/s: 0.9.0 > Add logging of total run time of Driver > --- > > Key: HIVE-2823 > URL: https://issues.apache.org/jira/browse/HIVE-2823 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2823.D1977.1.patch, HIVE-2823.D1977.2.patch > > > We are currently logging the run time of several components of the Driver, > e.g. compilation and map reduce execution time. It would be helpful to log > the total run time of the Driver's run method as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2825) Concatenating a partition does not inherit location from table
[ https://issues.apache.org/jira/browse/HIVE-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2825: --- Fix Version/s: 0.9.0 > Concatenating a partition does not inherit location from table > -- > > Key: HIVE-2825 > URL: https://issues.apache.org/jira/browse/HIVE-2825 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2825.D1995.1.patch, HIVE-2825.D1995.2.patch > > > When a table is created in one dfs, a partition is added to that table, the > table's dfs is changed, and the partitioned is concatenated, the partitions > location remains exactly the same. Instead, it should inherit its location > from the table, and be updated accordingly. > See https://issues.apache.org/jira/browse/HIVE-1707 for an analogous change > to insert overwrite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2833) Fix test failures caused by HIVE-2716
[ https://issues.apache.org/jira/browse/HIVE-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2833: --- Fix Version/s: 0.9.0 > Fix test failures caused by HIVE-2716 > - > > Key: HIVE-2833 > URL: https://issues.apache.org/jira/browse/HIVE-2833 > Project: Hive > Issue Type: Bug > Components: Metastore >Reporter: Carl Steinbach >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2716.D2055.1.patch, HIVE-2833.D2055.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] [Updated] (HIVE-2837) insert into external tables should not be allowed
[ https://issues.apache.org/jira/browse/HIVE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2837: --- Fix Version/s: 0.9.0 > insert into external tables should not be allowed > - > > Key: HIVE-2837 > URL: https://issues.apache.org/jira/browse/HIVE-2837 > Project: Hive > Issue Type: Bug >Reporter: Namit Jain >Assignee: Namit Jain > Fix For: 0.9.0 > > Attachments: HIVE-2837.D2211.1.patch, HIVE-2837.D2211.2.patch > > > This is a very risky thing to allow. > Since, the external tables can point to any user location, which can > potentially corrupt some other tables. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2832) Cache error messages for additional logging
[ https://issues.apache.org/jira/browse/HIVE-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2832: --- Fix Version/s: 0.9.0 > Cache error messages for additional logging > --- > > Key: HIVE-2832 > URL: https://issues.apache.org/jira/browse/HIVE-2832 > Project: Hive > Issue Type: Improvement > Components: Logging >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2832.D2025.1.patch, HIVE-2832.D2025.2.patch > > > It would be good if we could cache logs written to SessionState.err so that > they could be exposed to hooks for additional logging. This would allow > logging of error messages with the queries that failed in a central location. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2714) Lots of special characters are not handled in LIKE
[ https://issues.apache.org/jira/browse/HIVE-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2714: --- Fix Version/s: 0.9.0 > Lots of special characters are not handled in LIKE > -- > > Key: HIVE-2714 > URL: https://issues.apache.org/jira/browse/HIVE-2714 > Project: Hive > Issue Type: Bug >Reporter: Jonathan Chang >Assignee: Jonathan Chang > Fix For: 0.9.0 > > Attachments: HIVE-2714.D1239.1.patch, HIVE-2714.D1239.1.patch > > > Currently LIKE converts the string to a regular expression. It tries to > handle special characters but many are not correctly handled, e.g. +, ?, |, > etc. That code should just use Pattern.quote. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2872) Store which configs the user has explicitly changed
[ https://issues.apache.org/jira/browse/HIVE-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2872: --- Fix Version/s: 0.9.0 > Store which configs the user has explicitly changed > --- > > Key: HIVE-2872 > URL: https://issues.apache.org/jira/browse/HIVE-2872 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2872.D2337.1.patch, HIVE-2872.D2337.2.patch > > > It would be useful to keep track of which config variables the user has > explicitly changed from the values which are either default or loaded from > hive-site.xml. These include config variables set using the hiveconf > argument to the CLI, and via the SET command. This could be used to prevent > Hive from changing a config variable which has been explicitly set by the > user, and also potentially for logging to help with later debugging of failed > queries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2471) Add timestamp column to the partition stats table.
[ https://issues.apache.org/jira/browse/HIVE-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2471: --- Fix Version/s: 0.9.0 > Add timestamp column to the partition stats table. > -- > > Key: HIVE-2471 > URL: https://issues.apache.org/jira/browse/HIVE-2471 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2471.1.patch.txt, HIVE-2471.D2367.1.patch, > HIVE-2471.D2367.2.patch, HIVE-2471.D2367.3.patch > > > Occasionally, when entries are added to the partition stats table the program > is halted before it can delete those entries, by an exception, keyboard > interrupt, etc. These build up to the point where the table gets very large, > and it hurts the performance of the update statement which is often called. > In order to fix this, I am adding a column to the table which is > auto-populated with the current timestamp. This will allow us to create > scripts that go through periodically and clean out old entries from the 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] [Updated] (HIVE-2863) Ambiguous table name or column reference message displays when table and column names are the same
[ https://issues.apache.org/jira/browse/HIVE-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2863: --- Fix Version/s: 0.9.0 > Ambiguous table name or column reference message displays when table and > column names are the same > -- > > Key: HIVE-2863 > URL: https://issues.apache.org/jira/browse/HIVE-2863 > Project: Hive > Issue Type: Bug >Reporter: Mauro Cazzari >Assignee: Navis > Fix For: 0.9.0 > > Attachments: HIVE-2863.D2361.1.patch > > > Given the following table: > CREATE TABLE `Y` (`y` DOUBLE) ROW FORMAT DELIMITED FIELDS TERMINATED BY > '\001' STORED AS TEXTFILE; > The following query fails: > SELECT `Y`.`y` FROM `Y` WHERE ( `y` = 1 ) > ERROR: java.sql.SQLException: Query returned non-zero code: 10, cause: > FAILED: Error in >semantic analysis: Line 1:36 Ambiguous table alias or column reference > '`y`' > ERROR: Unable to execute Hadoop query. > ERROR: Prepare error. SQL statement: SELECT `Y`.`y` FROM `Y` WHERE ( `y` > = 1 ). > The problem goes away if the table and column names do not match. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2901) Hive union with NULL constant and string in same column returns all null
[ https://issues.apache.org/jira/browse/HIVE-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2901: --- Fix Version/s: 0.9.0 > Hive union with NULL constant and string in same column returns all null > > > Key: HIVE-2901 > URL: https://issues.apache.org/jira/browse/HIVE-2901 > Project: Hive > Issue Type: Bug >Reporter: Kevin Wilfong >Assignee: Navis >Priority: Critical > Fix For: 0.9.0 > > Attachments: HIVE-2901.D2541.1.patch, HIVE-2901.D2541.2.patch, > HIVE-2901.D2541.3.patch > > > select x from (select value as x from src union all select NULL as x from > src)a; > This query produces all nulls, where value is a string column. > Notably, > select x from (select key as x from src union all select NULL as x from src)a; > where key is a string, but can be cast to a double, the query returns correct > results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2948) HiveFileFormatUtils should use Path.SEPARATOR instead of File.Separator
[ https://issues.apache.org/jira/browse/HIVE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2948: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks, Kevin for the review.. Committed to trunk. > HiveFileFormatUtils should use Path.SEPARATOR instead of File.Separator > --- > > Key: HIVE-2948 > URL: https://issues.apache.org/jira/browse/HIVE-2948 > Project: Hive > Issue Type: Bug >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2948.D2763.1.patch > > > Because its munging hdfs paths and not OS paths. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-538) make hive_jdbc.jar self-containing
[ https://issues.apache.org/jira/browse/HIVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-538: -- Status: Patch Available (was: Open) Ready for review. > make hive_jdbc.jar self-containing > -- > > Key: HIVE-538 > URL: https://issues.apache.org/jira/browse/HIVE-538 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.6.0, 0.4.0, 0.3.0 >Reporter: Raghotham Murthy >Assignee: Ashutosh Chauhan > Attachments: HIVE-538.D2553.1.patch > > > Currently, most jars in hive/build/dist/lib and the hadoop-*-core.jar are > required in the classpath to run jdbc applications on hive. We need to do > atleast the following to get rid of most unnecessary dependencies: > 1. get rid of dynamic serde and use a standard serialization format, maybe > tab separated, json or avro > 2. dont use hadoop configuration parameters > 3. repackage thrift and fb303 classes into hive_jdbc.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2948) HiveFileFormatUtils should use Path.SEPARATOR instead of File.Separator
[ https://issues.apache.org/jira/browse/HIVE-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2948: --- Status: Patch Available (was: Open) Ready for review. > HiveFileFormatUtils should use Path.SEPARATOR instead of File.Separator > --- > > Key: HIVE-2948 > URL: https://issues.apache.org/jira/browse/HIVE-2948 > Project: Hive > Issue Type: Bug >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2948.D2763.1.patch > > > Because its munging hdfs paths and not OS paths. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2910) Improve the HWI interface
[ https://issues.apache.org/jira/browse/HIVE-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2910: --- Resolution: Fixed Fix Version/s: 0.10 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Hugo! > Improve the HWI interface > - > > Key: HIVE-2910 > URL: https://issues.apache.org/jira/browse/HIVE-2910 > Project: Hive > Issue Type: Improvement > Components: Web UI >Reporter: Hugo Trippaers >Assignee: Hugo Trippaers >Priority: Minor > Labels: newbie, patch > Fix For: 0.10 > > Attachments: glyphicons-halflings-white.png, > glyphicons-halflings.png, hive-2910.3.patch.log, hive-2910.3.patch.txt, > hive-2910.4.patch.txt, hive-hwi-2.patch, hive-hwi.patch, screenie001.PNG, > screenie002.PNG > > > I've made some improvements to the HWI interface with the Twitter bootstrap > system. I'm looking for feedback on the new 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] [Updated] (HIVE-2711) Make the header of RCFile unique
[ https://issues.apache.org/jira/browse/HIVE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2711: --- Resolution: Fixed Fix Version/s: 0.10 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Owen! > Make the header of RCFile unique > > > Key: HIVE-2711 > URL: https://issues.apache.org/jira/browse/HIVE-2711 > Project: Hive > Issue Type: Bug > Components: Serializers/Deserializers >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.10 > > Attachments: HIVE-2711.D2115.1.patch, HIVE-2711.D2115.2.patch, > HIVE-2711.D2115.3.patch, HIVE-2711.D2571.1.patch, rc-file-v0.rc > > > The RCFile implementation was copied from Hadoop's SequenceFile and copied > the 'magic' string in the header. This means that you can't use the header to > distinguish between RCFiles and SequenceFiles. > I'd propose that we create a new header for RCFiles (RCF?) to replace the > current SEQ. To maintain compatibility, we'll need to continue to accept the > current 'SEQ\06' and just make new files contain the new header. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2929) race condition in DAG execute tasks for hive
[ https://issues.apache.org/jira/browse/HIVE-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2929: --- Fix Version/s: 0.10 > race condition in DAG execute tasks for hive > > > Key: HIVE-2929 > URL: https://issues.apache.org/jira/browse/HIVE-2929 > Project: Hive > Issue Type: Bug >Reporter: Namit Jain >Assignee: Namit Jain > Fix For: 0.10 > > Attachments: hive.2929.1.patch > > > select ... > ( > SubQuery involving MapReduce > union all > SubQuery involving MapReduce > ); > or > select ... > (SubQuery involving MapReduce) > join > (SubQuery involving MapReduce) > ; > If both the subQueries finish at nearly the same time, there is a race > condition in which the results of the subQuery finishing last will be > completely missed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2858) Cache remote map reduce job stack traces for additional logging
[ https://issues.apache.org/jira/browse/HIVE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2858: --- Fix Version/s: 0.9.0 > Cache remote map reduce job stack traces for additional logging > --- > > Key: HIVE-2858 > URL: https://issues.apache.org/jira/browse/HIVE-2858 > Project: Hive > Issue Type: Improvement > Components: Logging >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2858.D2223.1.patch, HIVE-2858.D2223.2.patch > > > Currently we are parsing the task logs for failed jobs for information to > display to the user in the CLI. In addition, we could parse those logs for > stack traces and store e them in the SessionState. This way, when we log > failed queries, these will give us a decent idea of why those queries 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] [Updated] (HIVE-2585) Collapse hive.metastore.uris and hive.metastore.local
[ https://issues.apache.org/jira/browse/HIVE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2585: --- Status: Patch Available (was: Open) > Collapse hive.metastore.uris and hive.metastore.local > - > > Key: HIVE-2585 > URL: https://issues.apache.org/jira/browse/HIVE-2585 > Project: Hive > Issue Type: Improvement > Components: Metastore >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2585.D2559.1.patch, HIVE-2585.D2559.2.patch > > > We should just have hive.metastore.uris. If it is empty, we shall assume > local mode, if non-empty we shall use that string to connect to remote > metastore. Having two different keys for same information is confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2923) testAclPositive in TestZooKeeperTokenStore failing in clean checkout when run on Mac
[ https://issues.apache.org/jira/browse/HIVE-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2923: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Thomas! > testAclPositive in TestZooKeeperTokenStore failing in clean checkout when run > on Mac > > > Key: HIVE-2923 > URL: https://issues.apache.org/jira/browse/HIVE-2923 > Project: Hive > Issue Type: Bug >Affects Versions: 0.9.0 > Environment: Mac OSX Lion >Reporter: Kevin Wilfong >Assignee: Thomas Weise >Priority: Blocker > Fix For: 0.9.0 > > Attachments: HIVE-2923.patch > > > When running testAclPositive in TestZooKeeperTokenStore in a clean checkout, > it fails with the error: > Failed to validate token path. > org.apache.hadoop.hive.thrift.DelegationTokenStore$TokenStoreException: > Failed to validate token path. > at > org.apache.hadoop.hive.thrift.ZooKeeperTokenStore.init(ZooKeeperTokenStore.java:207) > at > org.apache.hadoop.hive.thrift.ZooKeeperTokenStore.setConf(ZooKeeperTokenStore.java:225) > at > org.apache.hadoop.hive.thrift.TestZooKeeperTokenStore.testAclPositive(TestZooKeeperTokenStore.java:170) > 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 junit.framework.TestCase.runTest(TestCase.java:168) > at junit.framework.TestCase.runBare(TestCase.java:134) > at junit.framework.TestResult$1.protect(TestResult.java:110) > at junit.framework.TestResult.runProtected(TestResult.java:128) > at junit.framework.TestResult.run(TestResult.java:113) > at junit.framework.TestCase.run(TestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:232) > at junit.framework.TestSuite.run(TestSuite.java:227) > at > org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518) > at > org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052) > at > org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906) > Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: > KeeperErrorCode = ConnectionLoss for /zktokenstore-testAcl > at org.apache.zookeeper.KeeperException.create(KeeperException.java:99) > at org.apache.zookeeper.KeeperException.create(KeeperException.java:51) > at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:778) > at > org.apache.hadoop.hive.thrift.ZooKeeperTokenStore.ensurePath(ZooKeeperTokenStore.java:119) > at > org.apache.hadoop.hive.thrift.ZooKeeperTokenStore.init(ZooKeeperTokenStore.java:204) > ... 17 more > This message is also printed to standard out: > Unable to load realm mapping info from SCDynamicStore > The test seems to run fine in Linux, but more than one developer has reported > this on a Mac. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2879) Add "rat" target to build to look for missing license headers
[ https://issues.apache.org/jira/browse/HIVE-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2879: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Owen! > Add "rat" target to build to look for missing license headers > - > > Key: HIVE-2879 > URL: https://issues.apache.org/jira/browse/HIVE-2879 > Project: Hive > Issue Type: Improvement > Components: Build Infrastructure >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.9.0 > > Attachments: HIVE-2879.D2373.1.patch, HIVE-2879.D2373.2.patch, > HIVE-2879.D2373.3.patch > > > We should have a "rat" target that can generate an Apache RAT report. RAT is > used for finding missing license headers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2559) Add target to install Hive JARs/POMs in the local Maven cache
[ https://issues.apache.org/jira/browse/HIVE-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2559: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Alan! > Add target to install Hive JARs/POMs in the local Maven cache > - > > Key: HIVE-2559 > URL: https://issues.apache.org/jira/browse/HIVE-2559 > Project: Hive > Issue Type: Improvement > Components: Build Infrastructure >Affects Versions: 0.9.0 >Reporter: Alejandro Abdelnur >Assignee: Alan Gates >Priority: Critical > Fix For: 0.9.0 > > Attachments: HIVE-2559.patch > > > HIVE-2391 is producing usable Maven artifacts. > However, it only as a target to deploy/publish those artifacts to Apache > Maven repos. > There should be a new target to locally install Hive Maven artifacts, thus > enabling their use from other projects before they are committed/publish to > Apache Maven (this is critical to test patches that may address issues in > downstream components). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2883) Metastore client doesnt close connection properly
[
https://issues.apache.org/jira/browse/HIVE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2883:
---
Status: Patch Available (was: Open)
> Metastore client doesnt close connection properly
> -
>
> Key: HIVE-2883
> URL: https://issues.apache.org/jira/browse/HIVE-2883
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 0.9.0
>Reporter: Ashutosh Chauhan
> Fix For: 0.9.0
>
> Attachments: HIVE-2883.D2613.1.patch
>
>
> While closing connection, it always fail with following trace. Seemingly, it
> doesnt have any harmful effects.
> {code}
> 12/03/20 10:55:02 ERROR hive.metastore: Unable to shutdown local metastore
> client
> org.apache.thrift.transport.TTransportException: Cannot write to null
> outputStream
> at
> org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport.java:142)
> at
> org.apache.thrift.protocol.TBinaryProtocol.writeI32(TBinaryProtocol.java:163)
> at
> org.apache.thrift.protocol.TBinaryProtocol.writeMessageBegin(TBinaryProtocol.java:91)
> at org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:62)
> at
> com.facebook.fb303.FacebookService$Client.send_shutdown(FacebookService.java:421)
> at
> com.facebook.fb303.FacebookService$Client.shutdown(FacebookService.java:415)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.close(HiveMetaStoreClient.java:310)
> {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] [Updated] (HIVE-2738) NPE in ExprNodeGenericFuncEvaluator
[
https://issues.apache.org/jira/browse/HIVE-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2738:
---
Status: Open (was: Patch Available)
Patch fails ant test -Dtestcase=TestNegativeCliDriver -Dqfile=udfnull.q
> NPE in ExprNodeGenericFuncEvaluator
> ---
>
> Key: HIVE-2738
> URL: https://issues.apache.org/jira/browse/HIVE-2738
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.8.0
>Reporter: Nicolas Lalevée
>Assignee: Nicolas Lalevée
> Attachments: 750c8966-6402-465a-b011-903469fe56da.xml,
> HIVE-2738-r1237763.patch, MapMaxUDF.java, MapToJsonUDF.java, hive_job_logs.txt
>
>
> Here is the query:
> bq. {{SELECT t.lid, '2011-12-12',
> s_map2json(s_maxmap(UNION_MAP(t.categoryCount), 100)) FROM ( SELECT theme_lid
> AS theme_lid, MAP(s_host(referer), COUNT( * )) AS categoryCount FROM
> PageViewEvent WHERE day >= '20130104' AND day <= '20130112' AND date_ >=
> '2012-01-04' AND date_ < '2012-01-13' AND lid IS NOT NULL GROUP BY lid,
> s_host(referer) ) t GROUP BY t.lid}}
> Removing the call s_map2json make it work but not by removing s_maxmap, but I
> don't understand what could be wrong with the implementation of my udf. And I
> don't know how to debug remote hadoop jobs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2861) Support eventual constant expression for filter pushdown for key ranges in hbase
[
https://issues.apache.org/jira/browse/HIVE-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2861:
---
Resolution: Fixed
Fix Version/s: 0.9.0
Status: Resolved (was: Patch Available)
Committed to trunk. Thanks, Navis!
> Support eventual constant expression for filter pushdown for key ranges in
> hbase
>
>
> Key: HIVE-2861
> URL: https://issues.apache.org/jira/browse/HIVE-2861
> Project: Hive
> Issue Type: Improvement
> Components: HBase Handler
>Reporter: Navis
>Assignee: Navis
>Priority: Trivial
> Fix For: 0.9.0
>
> Attachments: HIVE-2861.D2259.1.patch
>
>
> Minor upgrade from HIVE-2771, which supports simple eventual constant
> expression as a filter (especially 'cast').
> For example,
> {noformat}
> select * from hbase_pushdown where key > cast(20 + 30 as 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] [Updated] (HIVE-2920) TestStatsPublisherEnhanced throws NPE on JDBC connection failure
[ https://issues.apache.org/jira/browse/HIVE-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2920: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Carl! > TestStatsPublisherEnhanced throws NPE on JDBC connection failure > > > Key: HIVE-2920 > URL: https://issues.apache.org/jira/browse/HIVE-2920 > Project: Hive > Issue Type: Bug > Components: Statistics, Testing Infrastructure >Reporter: Carl Steinbach >Assignee: Carl Steinbach > Fix For: 0.9.0 > > Attachments: HIVE-2920.D2577.1.patch, HIVE-2920.D2577.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] [Updated] (HIVE-2576) HiveDataSource doesn't get a proper connection
[ https://issues.apache.org/jira/browse/HIVE-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2576: --- Status: Open (was: Patch Available) > HiveDataSource doesn't get a proper connection > -- > > Key: HIVE-2576 > URL: https://issues.apache.org/jira/browse/HIVE-2576 > Project: Hive > Issue Type: Bug > Components: JDBC >Affects Versions: 0.8.0 >Reporter: Nicolas Lalevée >Assignee: Nicolas Lalevée > Attachments: HIVE-2576-r1201637.patch > > > The HiveDataSource is creating a HiveConnection with as an URL "", but the > connection expects to start with "jdbc:hive://" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2332) If all of the parameters of distinct functions are exists in group by columns, query fails in runtime
[
https://issues.apache.org/jira/browse/HIVE-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2332:
---
Status: Patch Available (was: Open)
Oh, I missed it. Marking Patch Available then.
> If all of the parameters of distinct functions are exists in group by
> columns, query fails in runtime
> -
>
> Key: HIVE-2332
> URL: https://issues.apache.org/jira/browse/HIVE-2332
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: Navis
>Assignee: Navis
>Priority: Critical
> Fix For: 0.9.0
>
> Attachments: HIVE-2332.1.patch.txt, HIVE-2332.2.patch.txt,
> HIVE-2332.D663.1.patch
>
>
> select sum(key_int1), sum(distinct key_int1) from t1 group by key_int1;
> fails with message..
> {code}
> FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.MapRedTask
> {code}
> hadoop says..
> {code}
> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at
> org.apache.hadoop.hive.serde2.objectinspector.StandardStructObjectInspector.init(StandardStructObjectInspector.java:95)
> at
> org.apache.hadoop.hive.serde2.objectinspector.StandardStructObjectInspector.(StandardStructObjectInspector.java:86)
> at
> org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorFactory.getStandardStructObjectInspector(ObjectInspectorFactory.java:252)
> at
> org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.initEvaluatorsAndReturnStruct(ReduceSinkOperator.java:188)
> at
> org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.processOp(ReduceSinkOperator.java:197)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:85)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:532)
> {code}
> I think the deficient number of key expression, compared to number of key
> column, is the problem, which should be equal or more.
> Would it be solved if add some key expression? I'll try.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2332) If all of the parameters of distinct functions are exists in group by columns, query fails in runtime
[
https://issues.apache.org/jira/browse/HIVE-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2332:
---
Status: Open (was: Patch Available)
Canceling patch as it first needs to address Namit's comments.
> If all of the parameters of distinct functions are exists in group by
> columns, query fails in runtime
> -
>
> Key: HIVE-2332
> URL: https://issues.apache.org/jira/browse/HIVE-2332
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
>Reporter: Navis
>Assignee: Navis
>Priority: Critical
> Fix For: 0.9.0
>
> Attachments: HIVE-2332.1.patch.txt, HIVE-2332.2.patch.txt,
> HIVE-2332.D663.1.patch
>
>
> select sum(key_int1), sum(distinct key_int1) from t1 group by key_int1;
> fails with message..
> {code}
> FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.MapRedTask
> {code}
> hadoop says..
> {code}
> Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at
> org.apache.hadoop.hive.serde2.objectinspector.StandardStructObjectInspector.init(StandardStructObjectInspector.java:95)
> at
> org.apache.hadoop.hive.serde2.objectinspector.StandardStructObjectInspector.(StandardStructObjectInspector.java:86)
> at
> org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorFactory.getStandardStructObjectInspector(ObjectInspectorFactory.java:252)
> at
> org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.initEvaluatorsAndReturnStruct(ReduceSinkOperator.java:188)
> at
> org.apache.hadoop.hive.ql.exec.ReduceSinkOperator.processOp(ReduceSinkOperator.java:197)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:85)
> at org.apache.hadoop.hive.ql.exec.Operator.process(Operator.java:471)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:744)
> at
> org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:532)
> {code}
> I think the deficient number of key expression, compared to number of key
> column, is the problem, which should be equal or more.
> Would it be solved if add some key expression? I'll try.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-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 updated HIVE-2767:
---
Status: Open (was: Patch Available)
Patch needs to be rebased.
> 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: Julien Le Dem
> Attachments: 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] [Updated] (HIVE-2875) Renaming partition changes partition location prefix
[ https://issues.apache.org/jira/browse/HIVE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2875: --- Fix Version/s: 0.9.0 > Renaming partition changes partition location prefix > > > Key: HIVE-2875 > URL: https://issues.apache.org/jira/browse/HIVE-2875 > Project: Hive > Issue Type: Bug >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2875.D2349.1.patch, HIVE-2875.D2349.2.patch > > > Renaming a partition changes the location of the partition to the default > location of the table, followed by the partition specification. It should > just change the partition specification of the path. > If the path does not end with the old partition specification, we should > probably throw an exception because renaming a partition should not change > the path so dramatically, and not changing the path to reflect the new > partition name could leave the partition in a very confusing state. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2866) Cache local map reduce job errors for additional logging
[ https://issues.apache.org/jira/browse/HIVE-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2866: --- Fix Version/s: 0.9.0 > Cache local map reduce job errors for additional logging > > > Key: HIVE-2866 > URL: https://issues.apache.org/jira/browse/HIVE-2866 > Project: Hive > Issue Type: Improvement > Components: Logging >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2866.D2277.1.patch > > > Using the CachingPrintStream we are storing errors that occur locally in > Hive, but because local map reduce jobs are run in a separate JVM we are not > storing that occur for these. We can use this same construct to store errors > written to the subprocesses error stream. This way, when we log failed > queries, these will give us a decent idea of why those queries failed. > See related issues: > https://issues.apache.org/jira/browse/HIVE-2832 > https://issues.apache.org/jira/browse/HIVE-2858 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2676) The row count that loaded to a table may not right
[ https://issues.apache.org/jira/browse/HIVE-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2676: --- Fix Version/s: 0.9.0 > The row count that loaded to a table may not right > - > > Key: HIVE-2676 > URL: https://issues.apache.org/jira/browse/HIVE-2676 > Project: Hive > Issue Type: Improvement >Reporter: binlijin >Priority: Minor > Labels: patch > Fix For: 0.9.0 > > Attachments: HIVE-2676.patch > > > create table tablename as SELECT *** > At the end hive will print a number that show how many Rows loaded to the > tablename, but sometimes the number is not right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2881) Remove redundant key comparing in SMBMapJoinOperator
[ https://issues.apache.org/jira/browse/HIVE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2881: --- Fix Version/s: 0.9.0 > Remove redundant key comparing in SMBMapJoinOperator > > > Key: HIVE-2881 > URL: https://issues.apache.org/jira/browse/HIVE-2881 > Project: Hive > Issue Type: Improvement > Components: Query Processor >Reporter: Navis >Assignee: Navis >Priority: Minor > Fix For: 0.9.0 > > Attachments: HIVE-2881.D2379.1.patch > > > Currently, SMBJoin compares keys twice in #findSmallestKey and #joinObject. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2908) Hive: Extend ALTER TABLE DROP PARTITION syntax to use all comparators
[ https://issues.apache.org/jira/browse/HIVE-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2908: --- Fix Version/s: 0.9.0 > Hive: Extend ALTER TABLE DROP PARTITION syntax to use all comparators > - > > Key: HIVE-2908 > URL: https://issues.apache.org/jira/browse/HIVE-2908 > Project: Hive > Issue Type: Improvement > Components: Query Processor >Affects Versions: 0.9.0 >Reporter: Sambavi Muthukrishnan >Assignee: Sambavi Muthukrishnan >Priority: Minor > Fix For: 0.9.0 > > Attachments: HIVE-2908.D2523.1.patch, HIVE-2908.D2523.2.patch, > HIVE-2908.final.patch.txt > > Original Estimate: 96h > Remaining Estimate: 96h > > To drop a partition from a Hive table, this works: > ALTER TABLE foo DROP PARTITION(ds = 'date') > ...but it should also work to drop all partitions prior to date. > ALTER TABLE foo DROP PARTITION(ds < 'date') > This task is to implement ALTER TABLE DROP PARTITION for all of the > comparators, < > <= >= <> = != instead of just for =. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2853) Add pre event listeners to metastore
[ https://issues.apache.org/jira/browse/HIVE-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2853: --- Fix Version/s: 0.9.0 > Add pre event listeners to metastore > > > Key: HIVE-2853 > URL: https://issues.apache.org/jira/browse/HIVE-2853 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2853.D2175.1.patch, HIVE-2853.D2175.2.patch > > > Currently there are event listeners in the metastore which run after the > completion of a method. It would be useful to have similar hooks which run > before the metastore method is executed. These can be used to make > validating names, locations, etc. customizable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2585) Collapse hive.metastore.uris and hive.metastore.local
[ https://issues.apache.org/jira/browse/HIVE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2585: --- Status: Patch Available (was: Open) > Collapse hive.metastore.uris and hive.metastore.local > - > > Key: HIVE-2585 > URL: https://issues.apache.org/jira/browse/HIVE-2585 > Project: Hive > Issue Type: Improvement > Components: Metastore >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2585.D2559.1.patch > > > We should just have hive.metastore.uris. If it is empty, we shall assume > local mode, if non-empty we shall use that string to connect to remote > metastore. Having two different keys for same information is confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2711) Make the header of RCFile unique
[ https://issues.apache.org/jira/browse/HIVE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2711: --- Status: Open (was: Patch Available) > Make the header of RCFile unique > > > Key: HIVE-2711 > URL: https://issues.apache.org/jira/browse/HIVE-2711 > Project: Hive > Issue Type: Bug > Components: Serializers/Deserializers >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Attachments: HIVE-2711.D2115.1.patch > > > The RCFile implementation was copied from Hadoop's SequenceFile and copied > the 'magic' string in the header. This means that you can't use the header to > distinguish between RCFiles and SequenceFiles. > I'd propose that we create a new header for RCFiles (RCF?) to replace the > current SEQ. To maintain compatibility, we'll need to continue to accept the > current 'SEQ\06' and just make new files contain the new header. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2900) Add target for fatjar
[ https://issues.apache.org/jira/browse/HIVE-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2900: --- Resolution: Duplicate Fix Version/s: (was: 0.9.0) Status: Resolved (was: Patch Available) Closed in favor of HIVE-538 > Add target for fatjar > - > > Key: HIVE-2900 > URL: https://issues.apache.org/jira/browse/HIVE-2900 > Project: Hive > Issue Type: New Feature > Components: Build Infrastructure >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2900.D2469.1.patch > > > Currently, hive generates many different jars and also has slew of deps. It > would be useful to bundle all these jars together for easier downstream > consumption. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2912) HiveServer shouldn't initialize HiveMetaStore if Metastore is remote.
[ https://issues.apache.org/jira/browse/HIVE-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2912: --- Description: Currently it always initializes MetaStore in-process. (was: In HiveServer.java HiveServerHandler constructor line 131, call to super() should be made only if hive.local.metastore = true in conf. ) > HiveServer shouldn't initialize HiveMetaStore if Metastore is remote. > - > > Key: HIVE-2912 > URL: https://issues.apache.org/jira/browse/HIVE-2912 > Project: Hive > Issue Type: Bug >Reporter: Ashutosh Chauhan > > Currently it always initializes MetaStore in-process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2518) pull junit jar from maven repos via ivy
[ https://issues.apache.org/jira/browse/HIVE-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2518: --- Fix Version/s: 0.9.0 > pull junit jar from maven repos via ivy > --- > > Key: HIVE-2518 > URL: https://issues.apache.org/jira/browse/HIVE-2518 > Project: Hive > Issue Type: Improvement >Reporter: He Yongqiang >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2518.D2493.1.patch > > > see https://issues.apache.org/jira/browse/HIVE-2505 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2898) Add nicer helper functions for adding and reading metadata from RCFiles
[ https://issues.apache.org/jira/browse/HIVE-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2898: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Owen! > Add nicer helper functions for adding and reading metadata from RCFiles > --- > > Key: HIVE-2898 > URL: https://issues.apache.org/jira/browse/HIVE-2898 > Project: Hive > Issue Type: New Feature > Components: Serializers/Deserializers >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.9.0 > > Attachments: HIVE-2898.D2433.1.patch, HIVE-2898.D2433.2.patch, > HIVE-2898.D2433.3.patch, HIVE-2898.D2433.4.patch, HIVE-2898.D2433.5.patch > > > Currently, to use the metadata in RCFile, you need to manipulate it using > SequenceFile.Metadata. I'd like to add two helper functions that make it more > convenient. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2883) Metastore client doesnt close connection properly
[
https://issues.apache.org/jira/browse/HIVE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2883:
---
Component/s: Metastore
Affects Version/s: 0.9.0
Fix Version/s: 0.9.0
Looks like client.shutdown() is unnecessarily called after client.close() I
guess only one of those calls will suffice.
> Metastore client doesnt close connection properly
> -
>
> Key: HIVE-2883
> URL: https://issues.apache.org/jira/browse/HIVE-2883
> Project: Hive
> Issue Type: Bug
> Components: Metastore
>Affects Versions: 0.9.0
>Reporter: Ashutosh Chauhan
> Fix For: 0.9.0
>
>
> While closing connection, it always fail with following trace. Seemingly, it
> doesnt have any harmful effects.
> {code}
> 12/03/20 10:55:02 ERROR hive.metastore: Unable to shutdown local metastore
> client
> org.apache.thrift.transport.TTransportException: Cannot write to null
> outputStream
> at
> org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport.java:142)
> at
> org.apache.thrift.protocol.TBinaryProtocol.writeI32(TBinaryProtocol.java:163)
> at
> org.apache.thrift.protocol.TBinaryProtocol.writeMessageBegin(TBinaryProtocol.java:91)
> at org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:62)
> at
> com.facebook.fb303.FacebookService$Client.send_shutdown(FacebookService.java:421)
> at
> com.facebook.fb303.FacebookService$Client.shutdown(FacebookService.java:415)
> at
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.close(HiveMetaStoreClient.java:310)
> {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] [Updated] (HIVE-2797) Make the IP address of a Thrift client available to HMSHandler.
[ https://issues.apache.org/jira/browse/HIVE-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2797: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Thanks, Kevin for updating the patch. Committed to trunk. > Make the IP address of a Thrift client available to HMSHandler. > --- > > Key: HIVE-2797 > URL: https://issues.apache.org/jira/browse/HIVE-2797 > Project: Hive > Issue Type: Improvement > Components: Metastore >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2797.7.patch, HIVE-2797.D1701.1.patch, > HIVE-2797.D1701.2.patch, HIVE-2797.D1701.3.patch, HIVE-2797.D1701.4.patch, > HIVE-2797.D1701.5.patch, HIVE-2797.D1701.6.patch > > > Currently, in unsecured mode, metastore Thrift calls are, from the > HMSHandler's point of view, anonymous. If we expose the IP address of the > Thrift client to the HMSHandler from the Processor, this will help to give > some context, in particular for audit logging, of where the call is coming > from. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2894) RCFile Reader doesn't provide access to Metadata
[ https://issues.apache.org/jira/browse/HIVE-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2894: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Owen! > RCFile Reader doesn't provide access to Metadata > > > Key: HIVE-2894 > URL: https://issues.apache.org/jira/browse/HIVE-2894 > Project: Hive > Issue Type: New Feature >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.9.0 > > Attachments: HIVE-2894.D2421.1.patch > > > Currently the RCFile writer can add metadata to an RCFile, but the reader > doesn't provide an accessor. I'd like to add one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2879) Add "rat" target to build to look for missing license headers
[ https://issues.apache.org/jira/browse/HIVE-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2879: --- Status: Open (was: Patch Available) > Add "rat" target to build to look for missing license headers > - > > Key: HIVE-2879 > URL: https://issues.apache.org/jira/browse/HIVE-2879 > Project: Hive > Issue Type: Improvement > Components: Build Infrastructure >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Attachments: HIVE-2879.D2373.1.patch > > > We should have a "rat" target that can generate an Apache RAT report. RAT is > used for finding missing license headers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2900) Add target for fatjar
[ https://issues.apache.org/jira/browse/HIVE-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2900: --- Fix Version/s: 0.9.0 Status: Patch Available (was: Open) Marking Patch available. > Add target for fatjar > - > > Key: HIVE-2900 > URL: https://issues.apache.org/jira/browse/HIVE-2900 > Project: Hive > Issue Type: New Feature > Components: Build Infrastructure >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2900.D2469.1.patch > > > Currently, hive generates many different jars and also has slew of deps. It > would be useful to bundle all these jars together for easier downstream > consumption. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2773) HiveStorageHandler.configureTableJobProperites() should let the handler know wether it is configuration for input or output
[ https://issues.apache.org/jira/browse/HIVE-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2773: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Francis! > HiveStorageHandler.configureTableJobProperites() should let the handler know > wether it is configuration for input or output > --- > > Key: HIVE-2773 > URL: https://issues.apache.org/jira/browse/HIVE-2773 > Project: Hive > Issue Type: Improvement >Reporter: Francis Liu >Assignee: Francis Liu > Labels: hcatalog, storage_handler > Fix For: 0.9.0 > > Attachments: HIVE-2773.D1815.1.patch, HIVE-2773.D2007.1.patch, > HIVE-2773.D2415.1.patch, HIVE-2773.patch > > > HiveStorageHandler.configureTableJobProperties() is called to allow the > storage handler to setup any properties that the underlying > inputformat/outputformat/serde may need. But the handler implementation does > not know whether it is being called for configuring input or output. This > makes it a problem for handlers which sets an external state. In the case of > HCatalog's HBase storageHandler, whenever a write needs to be configured we > create a write transaction which needs to be committed or aborted later on. > In this case configuring for both input and output each time > configureTableJobProperties() is called would not be desirable. This has > become an issue since HCatalog is dropping storageDrivers for SerDe and > StorageHandler (see HCATALOG-237). > My proposal is to replace configureTableJobProperties() with two methods: > configureInputJobProperties() > configureOutputJobProperties() > Each method will have the same signature. I cursory look at the code and I > believe changes should be straighforward also given that we are not really > changing anything just splitting responsibility. If the community is fine > with this approach I will go ahead and create a aptch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2577) Expose the HiveConf in HiveConnection API
[ https://issues.apache.org/jira/browse/HIVE-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2577: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Nicolas! > Expose the HiveConf in HiveConnection API > - > > Key: HIVE-2577 > URL: https://issues.apache.org/jira/browse/HIVE-2577 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.8.0 >Reporter: Nicolas Lalevée >Assignee: Nicolas Lalevée > Fix For: 0.9.0 > > Attachments: HIVE-2577-r1201637.patch > > > When running the jdbc code in a local mode, there no way to programatically > manage the hive 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] [Updated] (HIVE-2819) Closed range scans on hbase keys
[ https://issues.apache.org/jira/browse/HIVE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2819: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) As I noted in my previous comments, all tests passed. Committed to trunk. Thanks, Carl for the review. > Closed range scans on hbase keys > - > > Key: HIVE-2819 > URL: https://issues.apache.org/jira/browse/HIVE-2819 > Project: Hive > Issue Type: Improvement > Components: HBase Handler >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2819.D1923.1.patch, HIVE-2819.D1923.2.patch, > HIVE-2819.D1923.3.patch > > > This patch pushes range scans on keys of closed form into hbase -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2797) Make the IP address of a Thrift client available to HMSHandler.
[ https://issues.apache.org/jira/browse/HIVE-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2797: --- Status: Open (was: Patch Available) Patch doesn't apply cleanly. Needs a rebase. > Make the IP address of a Thrift client available to HMSHandler. > --- > > Key: HIVE-2797 > URL: https://issues.apache.org/jira/browse/HIVE-2797 > Project: Hive > Issue Type: Improvement > Components: Metastore >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Attachments: HIVE-2797.D1701.1.patch, HIVE-2797.D1701.2.patch, > HIVE-2797.D1701.3.patch, HIVE-2797.D1701.4.patch, HIVE-2797.D1701.5.patch > > > Currently, in unsecured mode, metastore Thrift calls are, from the > HMSHandler's point of view, anonymous. If we expose the IP address of the > Thrift client to the HMSHandler from the Processor, this will help to give > some context, in particular for audit logging, of where the call is coming > from. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2805) Move metastore upgrade scripts labeled 0.10.0 into scripts labeled 0.9.0
[ https://issues.apache.org/jira/browse/HIVE-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2805: --- Component/s: Metastore Affects Version/s: 0.9.0 Fix Version/s: 0.9.0 > Move metastore upgrade scripts labeled 0.10.0 into scripts labeled 0.9.0 > > > Key: HIVE-2805 > URL: https://issues.apache.org/jira/browse/HIVE-2805 > Project: Hive > Issue Type: Task > Components: Metastore >Affects Versions: 0.9.0 >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2805.D1743.1.patch > > > Move contents of upgrade-0.9.0-to-0.10.0.mysql.sql, > upgrade-0.9.0-to-0.10.0.derby.sql into upgrade-0.8.0-to-0.9.0.mysql.sql, > upgrade-0.8.0-to-0.9.0.derby.sql > Rename hive-schema-0.10.0.derby.sql, hive-schema-0.10.0.mysql.sql to > hive-schema-0.9.0.derby.sql, hive-schema-0.9.0.mysql.sql -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2864) If hive history file's directory doesn't exist don't crash
[ https://issues.apache.org/jira/browse/HIVE-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2864: --- Fix Version/s: 0.9.0 > If hive history file's directory doesn't exist don't crash > -- > > Key: HIVE-2864 > URL: https://issues.apache.org/jira/browse/HIVE-2864 > Project: Hive > Issue Type: Improvement >Reporter: Kevin Wilfong >Assignee: Kevin Wilfong > Fix For: 0.9.0 > > Attachments: HIVE-2864.D2265.1.patch, HIVE-2864.D2265.2.patch > > > Currently, if the history file's directory does not exist the Hive client > crashes. Instead, since this is not a vital feature, it should just display > a warning to the user and continue without it. > This will become more important once the directory becomes configurable, see: > https://issues.apache.org/jira/browse/HIVE-1708 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2865) hive-config.sh should honor HIVE_HOME env
[ https://issues.apache.org/jira/browse/HIVE-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2865: --- Resolution: Fixed Status: Resolved (was: Patch Available) > hive-config.sh should honor HIVE_HOME env > -- > > Key: HIVE-2865 > URL: https://issues.apache.org/jira/browse/HIVE-2865 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.8.0 >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 0.9.0 > > Attachments: HIVE-2865.patch > > > hive-config.sh should honor HIVE_HOME env variable if set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2865) hive-config.sh should honor HIVE_HOME env
[ https://issues.apache.org/jira/browse/HIVE-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2865: --- Fix Version/s: 0.9.0 Status: Patch Available (was: Open) Committed to trunk. Thanks, Giri! > hive-config.sh should honor HIVE_HOME env > -- > > Key: HIVE-2865 > URL: https://issues.apache.org/jira/browse/HIVE-2865 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.8.0 >Reporter: Giridharan Kesavan >Assignee: Giridharan Kesavan > Fix For: 0.9.0 > > Attachments: HIVE-2865.patch > > > hive-config.sh should honor HIVE_HOME env variable if set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2831) TestContribCliDriver.dboutput and TestCliDriver.input45 fail on 0.23
[ https://issues.apache.org/jira/browse/HIVE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2831: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed. Thanks, Carl! > TestContribCliDriver.dboutput and TestCliDriver.input45 fail on 0.23 > > > Key: HIVE-2831 > URL: https://issues.apache.org/jira/browse/HIVE-2831 > Project: Hive > Issue Type: Bug > Components: Tests >Reporter: Carl Steinbach >Assignee: Carl Steinbach > Fix For: 0.9.0 > > Attachments: HIVE-2831.1.patch.txt, HIVE-2831.D2049.1.patch, > HIVE-2831.D2049.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] [Updated] (HIVE-2850) Remove zero length files
[ https://issues.apache.org/jira/browse/HIVE-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2850: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed. Thanks, Owen! > Remove zero length files > > > Key: HIVE-2850 > URL: https://issues.apache.org/jira/browse/HIVE-2850 > Project: Hive > Issue Type: Improvement >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.9.0 > > Attachments: HIVE-2850.D2163.1.patch > > > There are also zero-length non-source files that need to be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2503) HiveServer should provide per session configuration
[ https://issues.apache.org/jira/browse/HIVE-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2503: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Navis! > HiveServer should provide per session configuration > --- > > Key: HIVE-2503 > URL: https://issues.apache.org/jira/browse/HIVE-2503 > Project: Hive > Issue Type: Bug > Components: CLI, Server Infrastructure >Affects Versions: 0.9.0 >Reporter: Navis >Assignee: Navis > Fix For: 0.9.0 > > Attachments: HIVE-2503.1.patch.txt > > > Currently ThriftHiveProcessorFactory returns same HiveConf instance to > HiveServerHandler, making impossible to use per sesssion configuration. Just > wrapping 'conf' -> 'new HiveConf(conf)' seemed to solve this problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2702) listPartitionsByFilter only supports non-string partitions
[
https://issues.apache.org/jira/browse/HIVE-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-2702:
---
Status: Open (was: Patch Available)
> listPartitionsByFilter only supports non-string partitions
> --
>
> Key: HIVE-2702
> URL: https://issues.apache.org/jira/browse/HIVE-2702
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: Aniket Mokashi
>Assignee: Aniket Mokashi
> Attachments: HIVE-2702.1.patch, HIVE-2702.D2043.1.patch
>
>
> listPartitionsByFilter supports only non-string partitions. This is because
> its explicitly specified in generateJDOFilterOverPartitions in
> ExpressionTree.java.
> //Can only support partitions whose types are string
> if( ! table.getPartitionKeys().get(partitionColumnIndex).
>
> getType().equals(org.apache.hadoop.hive.serde.Constants.STRING_TYPE_NAME) ) {
> throw new MetaException
> ("Filtering is supported only on partition keys of type string");
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2819) Closed range scans on hbase keys
[ https://issues.apache.org/jira/browse/HIVE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2819: --- Status: Patch Available (was: Open) Ready for review. > Closed range scans on hbase keys > - > > Key: HIVE-2819 > URL: https://issues.apache.org/jira/browse/HIVE-2819 > Project: Hive > Issue Type: Improvement > Components: HBase Handler >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2819.D1923.1.patch, HIVE-2819.D1923.2.patch > > > This patch pushes range scans on keys of closed form into hbase -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2860) TestNegativeCliDriver autolocal1.q fails on 0.23
[ https://issues.apache.org/jira/browse/HIVE-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2860: --- Status: Open (was: Patch Available) > TestNegativeCliDriver autolocal1.q fails on 0.23 > > > Key: HIVE-2860 > URL: https://issues.apache.org/jira/browse/HIVE-2860 > 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-2860.D2253.1.patch, HIVE-2860.D2253.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] [Updated] (HIVE-2835) Change default configuration for hive.exec.dynamic.partition
[ https://issues.apache.org/jira/browse/HIVE-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2835: --- Resolution: Fixed Fix Version/s: 0.9.0 Release Note: Dynamic Partitioning is now on by default. Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Owen! > Change default configuration for hive.exec.dynamic.partition > > > Key: HIVE-2835 > URL: https://issues.apache.org/jira/browse/HIVE-2835 > Project: Hive > Issue Type: Improvement >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.9.0 > > Attachments: HIVE-2835.D2157.1.patch, HIVE-2835.D2157.2.patch > > > I think we should enable dynamic partitions by default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2748) Upgrade Hbase and ZK dependcies
[ https://issues.apache.org/jira/browse/HIVE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2748: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Patch committed to trunk. Thanks, Enis for your persistence on this one. > Upgrade Hbase and ZK dependcies > --- > > Key: HIVE-2748 > URL: https://issues.apache.org/jira/browse/HIVE-2748 > Project: Hive > Issue Type: Task >Affects Versions: 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.9.0 >Reporter: Ashutosh Chauhan >Assignee: Enis Soztutar > Fix For: 0.9.0 > > Attachments: HIVE-2748.3.patch, HIVE-2748.D1431.1.patch, > HIVE-2748.D1431.2.patch, HIVE-2748_v4.patch, HIVE-2748_v5.patch, > HIVE-2748_v6.patch, HIVE-2748_v7.patch, HIVE-2748_v8.patch > > > Both softwares have moved forward with significant improvements. Lets bump > compile time dependency to keep up -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1634) Allow access to Primitive types stored in binary format in HBase
[
https://issues.apache.org/jira/browse/HIVE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-1634:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow access to Primitive types stored in binary format in HBase
>
>
> Key: HIVE-1634
> URL: https://issues.apache.org/jira/browse/HIVE-1634
> Project: Hive
> Issue Type: Improvement
> Components: HBase Handler
>Affects Versions: 0.7.0, 0.8.0, 0.9.0
>Reporter: Basab Maulik
>Assignee: Ashutosh Chauhan
> Fix For: 0.9.0
>
> Attachments: HIVE-1634.0.patch, HIVE-1634.1.patch,
> HIVE-1634.D1581.1.patch, HIVE-1634.D1581.2.patch, HIVE-1634.D1581.3.patch,
> TestHiveHBaseExternalTable.java, hive-1634_3.patch
>
>
> This addresses HIVE-1245 in part, for atomic or primitive types.
> The serde property "hbase.columns.storage.types" = "-,b,b,b,b,b,b,b,b" is a
> specification of the storage option for the corresponding column in the serde
> property "hbase.columns.mapping". Allowed values are '-' for table default,
> 's' for standard string storage, and 'b' for binary storage as would be
> obtained from o.a.h.hbase.utils.Bytes. Map types for HBase column families
> use a colon separated pair such as 's:b' for the key and value part
> specifiers respectively. See the test cases and queries for HBase handler for
> additional examples.
> There is also a table property "hbase.table.default.storage.type" = "string"
> to specify a table level default storage type. The other valid specification
> is "binary". The table level default is overridden by a column level
> specification.
> This control is available for the boolean, tinyint, smallint, int, bigint,
> float, and double primitive types. The attached patch also relaxes the
> mapping of map types to HBase column families to allow any primitive type to
> be the map key.
> Attached is a program for creating a table and populating it in HBase. The
> external table in Hive can access the data as shown in the example below.
> hive> create external table TestHiveHBaseExternalTable
> > (key string, c_bool boolean, c_byte tinyint, c_short smallint,
> > c_int int, c_long bigint, c_string string, c_float float, c_double
> double)
> > stored by 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> > with serdeproperties ("hbase.columns.mapping" =
> ":key,cf:boolean,cf:byte,cf:short,cf:int,cf:long,cf:string,cf:float,cf:double")
> > tblproperties ("hbase.table.name" = "TestHiveHBaseExternalTable");
> OK
> Time taken: 0.691 seconds
> hive> select * from TestHiveHBaseExternalTable;
> OK
> key-1 NULLNULLNULLNULLNULLTest-String NULLNULL
> Time taken: 0.346 seconds
> hive> drop table TestHiveHBaseExternalTable;
> OK
> Time taken: 0.139 seconds
> hive> create external table TestHiveHBaseExternalTable
> > (key string, c_bool boolean, c_byte tinyint, c_short smallint,
> > c_int int, c_long bigint, c_string string, c_float float, c_double
> double)
> > stored by 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> > with serdeproperties (
> > "hbase.columns.mapping" =
> ":key,cf:boolean,cf:byte,cf:short,cf:int,cf:long,cf:string,cf:float,cf:double",
> > "hbase.columns.storage.types" = "-,b,b,b,b,b,b,b,b" )
> > tblproperties (
> > "hbase.table.name" = "TestHiveHBaseExternalTable",
> > "hbase.table.default.storage.type" = "string");
> OK
> Time taken: 0.139 seconds
> hive> select * from TestHiveHBaseExternalTable;
> OK
> key-1 true-128-32768 -2147483648 -9223372036854775808
> Test-String -2.1793132E-11 2.01345E291
> Time taken: 0.151 seconds
> hive> drop table TestHiveHBaseExternalTable;
> OK
> Time taken: 0.154 seconds
> hive> create external table TestHiveHBaseExternalTable
> > (key string, c_bool boolean, c_byte tinyint, c_short smallint,
> > c_int int, c_long bigint, c_string string, c_float float, c_double
> double)
> > stored by 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> > with serdeproperties (
> > "hbase.columns.mapping" =
> ":key,cf:boolean,cf:byte,cf:short,cf:int,cf:long,cf:string,cf:float,cf:double",
> > "hbase.columns.storage.types" = "-,b,b,b,b,b,-,b,b" )
> > tblproperties ("hbase.table.name" = "TestHiveHBaseExternalTable");
> OK
> Time taken: 0.347 seconds
> hive> select * from TestHiveHBaseExternalTable;
> OK
> key-1 true-128-32768 -2147483648 -9223372036854775808
> Test-String -2.1793132E-11 2.01345E291
> Time taken: 0.245 seconds
> hive>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.j
[jira] [Updated] (HIVE-2819) Closed range scans on hbase keys
[ https://issues.apache.org/jira/browse/HIVE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2819: --- Status: Patch Available (was: Open) Ready for review. > Closed range scans on hbase keys > - > > Key: HIVE-2819 > URL: https://issues.apache.org/jira/browse/HIVE-2819 > Project: Hive > Issue Type: Improvement >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Attachments: HIVE-2819.D1923.1.patch > > > This patch pushes range scans on keys of closed form into hbase -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2815) Filter pushdown in hbase for keys stored in binary format
[ https://issues.apache.org/jira/browse/HIVE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2815: --- Status: Patch Available (was: Open) > Filter pushdown in hbase for keys stored in binary format > - > > Key: HIVE-2815 > URL: https://issues.apache.org/jira/browse/HIVE-2815 > Project: Hive > Issue Type: Improvement > Components: HBase Handler >Affects Versions: 0.8.1, 0.8.0, 0.7.1, 0.7.0, 0.6.0 >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2815.D1875.1.patch > > > This patch enables filter pushdown for keys stored in binary format in hbase -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2517) Support group by on union and struct type
[ https://issues.apache.org/jira/browse/HIVE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2517: --- Status: Patch Available (was: Open) > Support group by on union and struct type > - > > Key: HIVE-2517 > URL: https://issues.apache.org/jira/browse/HIVE-2517 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Labels: structtype, uniontype > Fix For: 0.9.0 > > Attachments: HIVE-2517.D2151.1.patch, hive-2517.patch, > hive-2517_1.patch, hive-2517_2.patch > > > Currently group by on struct and union types are not supported. This issue > will enable support for those. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2840) INPUT__FILE__NAME virtual column returns unqualified paths on Hadoop 0.23
[ https://issues.apache.org/jira/browse/HIVE-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2840: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. > INPUT__FILE__NAME virtual column returns unqualified paths on Hadoop 0.23 > - > > Key: HIVE-2840 > URL: https://issues.apache.org/jira/browse/HIVE-2840 > Project: Hive > Issue Type: Bug > Components: Query Processor >Reporter: Carl Steinbach >Assignee: Carl Steinbach > Fix For: 0.9.0 > > Attachments: HIVE-2840.D2127.1.patch, HIVE-2840.D2127.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] [Updated] (HIVE-2841) Fix javadoc warnings
[ https://issues.apache.org/jira/browse/HIVE-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2841: --- Resolution: Fixed Fix Version/s: 0.9.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Owen for this useful work! > Fix javadoc warnings > > > Key: HIVE-2841 > URL: https://issues.apache.org/jira/browse/HIVE-2841 > Project: Hive > Issue Type: Improvement >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Fix For: 0.9.0 > > Attachments: HIVE-2841.D2139.1.patch > > > We currently have 219 warnings out of Javadoc and I'd like to fix them all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2789) When integrating into MapReduce2, 'select * from src distribute by src.key limit 1' returns non-deterministic result
[ https://issues.apache.org/jira/browse/HIVE-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2789: --- Status: Open (was: Patch Available) Patch needs to be rebased. > When integrating into MapReduce2, 'select * from src distribute by src.key > limit 1' returns non-deterministic result > > > Key: HIVE-2789 > URL: https://issues.apache.org/jira/browse/HIVE-2789 > Project: Hive > Issue Type: Bug > Components: Tests >Reporter: Zhenxiao Luo >Assignee: Carl Steinbach > Attachments: HIVE-2789.D1647.1.patch, HIVE-2789.D1647.1.patch, > HIVE-2789.D1647.2.patch, HIVE-2789.D1647.2.patch > > > query_properties.q test failure: > [junit] Begin query: query_properties.q > [junit] 12/01/23 16:59:13 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:13 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:18 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:18 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:22 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:22 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:27 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:27 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:32 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:32 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:36 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:36 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:41 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:41 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:46 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:46 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:50 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:50 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:55 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:55 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 16:59:59 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 16:59:59 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 17:00:04 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 17:00:04 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 17:00:08 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 17:00:08 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 17:00:13 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 17:00:13 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 17:00:18 WARN conf.Configuration: mapred.system.dir is > deprecated. Instead, use mapreduce.jobtracker.system.dir > [junit] 12/01/23 17:00:18 WARN conf.Configuration: mapred.local.dir is > deprecated. Instead, use mapreduce.cluster.local.dir > [junit] 12/01/23 17:00:22 WARN conf.Configuration: mapr
[jira] [Updated] (HIVE-2771) Add support for filter pushdown for key ranges in hbase for keys of type string
[ https://issues.apache.org/jira/browse/HIVE-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2771: --- Attachment: hive-2771.patch Patch with license. > Add support for filter pushdown for key ranges in hbase for keys of type > string > --- > > Key: HIVE-2771 > URL: https://issues.apache.org/jira/browse/HIVE-2771 > Project: Hive > Issue Type: Sub-task > Components: HBase Handler >Affects Versions: 0.7.0, 0.7.1, 0.8.0, 0.8.1 >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2771.D1551.1.patch, HIVE-2771.D1551.2.patch, > hive-2771.patch > > > This is a subtask of HIVE-1643 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2517) Support group by on union and struct type
[ https://issues.apache.org/jira/browse/HIVE-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2517: --- Attachment: hive-2517_2.patch Patch with license. > Support group by on union and struct type > - > > Key: HIVE-2517 > URL: https://issues.apache.org/jira/browse/HIVE-2517 > Project: Hive > Issue Type: New Feature > Components: Query Processor >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Labels: structtype, uniontype > Fix For: 0.9.0 > > Attachments: HIVE-2517.D2151.1.patch, hive-2517.patch, > hive-2517_1.patch, hive-2517_2.patch > > > Currently group by on struct and union types are not supported. This issue > will enable support for those. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2498) Group by operator doesnt estimate size of Timestamp & Binary data correctly
[ https://issues.apache.org/jira/browse/HIVE-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2498: --- Attachment: (was: HIVE-2498.D2145.1.patch) > Group by operator doesnt estimate size of Timestamp & Binary data correctly > --- > > Key: HIVE-2498 > URL: https://issues.apache.org/jira/browse/HIVE-2498 > Project: Hive > Issue Type: Bug >Affects Versions: 0.8.0, 0.8.1 >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2498.D1185.1.patch, hive-2498.patch, > hive-2498_1.patch > > > It currently defaults to default case and returns constant value, whereas we > can do better by getting actual size at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2498) Group by operator doesnt estimate size of Timestamp & Binary data correctly
[ https://issues.apache.org/jira/browse/HIVE-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2498: --- Attachment: hive-2498_1.patch Current patch cleanly applies on trunk. In any case, here is the rebased patch. > Group by operator doesnt estimate size of Timestamp & Binary data correctly > --- > > Key: HIVE-2498 > URL: https://issues.apache.org/jira/browse/HIVE-2498 > Project: Hive > Issue Type: Bug >Affects Versions: 0.8.0, 0.8.1 >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2498.D1185.1.patch, hive-2498.patch, > hive-2498_1.patch > > > It currently defaults to default case and returns constant value, whereas we > can do better by getting actual size at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2498) Group by operator doesnt estimate size of Timestamp & Binary data correctly
[ https://issues.apache.org/jira/browse/HIVE-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-2498: --- Affects Version/s: 0.8.0 0.8.1 Status: Patch Available (was: Open) Ready for review. > Group by operator doesnt estimate size of Timestamp & Binary data correctly > --- > > Key: HIVE-2498 > URL: https://issues.apache.org/jira/browse/HIVE-2498 > Project: Hive > Issue Type: Bug >Affects Versions: 0.8.1, 0.8.0 >Reporter: Ashutosh Chauhan >Assignee: Ashutosh Chauhan > Fix For: 0.9.0 > > Attachments: HIVE-2498.D1185.1.patch, hive-2498.patch, > hive-2498_1.patch > > > It currently defaults to default case and returns constant value, whereas we > can do better by getting actual size at runtime. -- 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
