[jira] [Updated] (HIVE-8382) ConstantPropagateProcFactory#isDeterministicUdf adds a lot of ERROR level logs

2014-10-08 Thread Navis (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Navis updated HIVE-8382:

Status: Patch Available  (was: Open)

 ConstantPropagateProcFactory#isDeterministicUdf adds a lot of ERROR level logs
 --

 Key: HIVE-8382
 URL: https://issues.apache.org/jira/browse/HIVE-8382
 Project: Hive
  Issue Type: Bug
  Components: Logical Optimizer
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
 Attachments: HIVE-8382.1.patch.txt


 Makes it hard to go over the hive log to figure out real errors:
 {code}
 try {
 UDF udfInternal =
 (UDF) Class.forName(bridge.getUdfClassName(), true, 
 Utilities.getSessionSpecifiedClassLoader())
 .newInstance();
 files = udfInternal.getRequiredFiles();
 jars = udf.getRequiredJars();
   } catch (Exception e) {
 LOG.error(The UDF implementation class ' + udfClassName
 + ' is not present in the class path);
 return false;
   }
 {code}
 I think we should either log this at INFO or DEBUG level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8382) ConstantPropagateProcFactory#isDeterministicUdf adds a lot of ERROR level logs

2014-10-08 Thread Navis (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Navis updated HIVE-8382:

Attachment: HIVE-8382.1.patch.txt

 ConstantPropagateProcFactory#isDeterministicUdf adds a lot of ERROR level logs
 --

 Key: HIVE-8382
 URL: https://issues.apache.org/jira/browse/HIVE-8382
 Project: Hive
  Issue Type: Bug
  Components: Logical Optimizer
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
 Attachments: HIVE-8382.1.patch.txt


 Makes it hard to go over the hive log to figure out real errors:
 {code}
 try {
 UDF udfInternal =
 (UDF) Class.forName(bridge.getUdfClassName(), true, 
 Utilities.getSessionSpecifiedClassLoader())
 .newInstance();
 files = udfInternal.getRequiredFiles();
 jars = udf.getRequiredJars();
   } catch (Exception e) {
 LOG.error(The UDF implementation class ' + udfClassName
 + ' is not present in the class path);
 return false;
   }
 {code}
 I think we should either log this at INFO or DEBUG level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8372) Potential NPE in Tez MergeFileRecordProcessor

2014-10-08 Thread Prasanth J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanth J updated HIVE-8372:
-
   Resolution: Fixed
Fix Version/s: 0.15.0
   0.14.0
   Status: Resolved  (was: Patch Available)

Patch committed to trunk and branch-0.14.

 Potential NPE in Tez MergeFileRecordProcessor
 -

 Key: HIVE-8372
 URL: https://issues.apache.org/jira/browse/HIVE-8372
 Project: Hive
  Issue Type: Bug
  Components: Tez
Affects Versions: 0.14.0
Reporter: Prasanth J
Assignee: Prasanth J
 Fix For: 0.14.0, 0.15.0

 Attachments: HIVE-8372.1.patch


 MergeFileRecordProcessor retrieves map work from cache. This map work can be 
 instance of merge file work. When the merge file work already exists in the 
 cache casting the map work to merge file work is missing which will result in 
 NullPointerException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8395) CBO: enable by default

2014-10-08 Thread Gunther Hagleitner (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163144#comment-14163144
 ] 

Gunther Hagleitner commented on HIVE-8395:
--

[~xuefuz] I've spent a lot of time analyzing results from these runs and I can 
tell you that it actually flushed out a lot of issues in the execution 
engine(s), because CBO expects any bushy join tree to properly work and that 
algebraic rewrites actually produce the same results. Also, it flags any 
optimization that has too narrow a set of matching rules. A side effect of this 
ticket will be tightening up all these things and feedback to folks adding new 
functionality. In general I think this is a huge benefit. 

In the case of CBO, the argument of which code path gets exercised is also not 
applicable. Unlike vectorization or execution engine, it's additive as I 
understand it - it still goes through all the same regular hive code paths 
before and after rewriting the AST. CBO is also conservative in when it kicks 
in. It makes sure that it has the stats and information it needs before 
rewriting the AST. If that's not met, it will just process as usual.

I'm also not sure whether you're saying leave off for 0.14 or trunk. Switching 
over for .14 is late in the game (as suggested by the fix version), but turning 
on in trunk will give us an entire release cycle to mature which I think is 
reasonable, especially given the benefits it can unlock for us.

 CBO: enable by default
 --

 Key: HIVE-8395
 URL: https://issues.apache.org/jira/browse/HIVE-8395
 Project: Hive
  Issue Type: Sub-task
  Components: CBO
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.14.0

 Attachments: HIVE-8395.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [VOTE] officially stop supporting hadoop 0.20.x in hive 0.14 ?

2014-10-08 Thread Gopal V

On 10/7/14, 3:53 PM, Thejas Nair wrote:

+1

Cheers,
Gopal


I think it is time to revisit the support for hive support for hadoop
0.20. Trying to maintain support for it puts additional burden on hive
contributors.

The last hadoop 0.20.x version was released on Feb 2010. Hadoop 1.0
was released in Dec 2011.
I believe most users have moved on to hadoop 2.x or at least hadoop
1.x . The users if any that are still on hadoop 0.20 probably don't
tend to upgrade their hive versions as well.

With the move to maven for builds in hive 0.13, we don't have the
ability to compile against hadoop 0.20. (Nobody has complains about
that AFAIK). I am not sure if hive 0.13 works well against hadoop
0.20, as it is not clear if that combination is in use. Also, most
commercial vendors seem to be focussing on testing it against hadoop
2.x.

I think it is time to do away with this added burden of attempting to
support hadoop 0.20.x versions.

Here is my +1 for officially stopping support for hadoop 0.20.x in hive 0.14 .

Thanks,
Thejas





[jira] [Updated] (HIVE-8389) Disable CBO when indexes are used

2014-10-08 Thread Gunther Hagleitner (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gunther Hagleitner updated HIVE-8389:
-
Assignee: Pengcheng Xiong

 Disable CBO when indexes are used
 -

 Key: HIVE-8389
 URL: https://issues.apache.org/jira/browse/HIVE-8389
 Project: Hive
  Issue Type: Bug
Reporter: Pengcheng Xiong
Assignee: Pengcheng Xiong
 Attachments: HIVE-8389.1.patch


 Disable CBO when indexes are used



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8389) Disable CBO when indexes are used

2014-10-08 Thread Gunther Hagleitner (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163203#comment-14163203
 ] 

Gunther Hagleitner commented on HIVE-8389:
--

[~pxiong] Sergey is right. This way you'll disable CBO whenever someone turns 
on the index optimization. That works, but is a blunt way of handling it. I've 
looked at the code a little bit. Since you can't tell from the semantic 
analyzer if any indices qualify, they only other way to handle this is to find 
out why CBO and index optimizer actually conflict and then address that.

Can you share the testcase/result on this ticket that shows the conflict?

 Disable CBO when indexes are used
 -

 Key: HIVE-8389
 URL: https://issues.apache.org/jira/browse/HIVE-8389
 Project: Hive
  Issue Type: Bug
Reporter: Pengcheng Xiong
Assignee: Pengcheng Xiong
 Attachments: HIVE-8389.1.patch


 Disable CBO when indexes are used



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8280) CBO : When filter is applied on dimension table PK/FK code path is not in effect.

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163222#comment-14163222
 ] 

Hive QA commented on HIVE-8280:
---



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673524/HIVE-8280.3.patch

{color:green}SUCCESS:{color} +1 6528 tests passed

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1149/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1149/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1149/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12673524

 CBO : When filter is applied on dimension table PK/FK code path is not in 
 effect.
 -

 Key: HIVE-8280
 URL: https://issues.apache.org/jira/browse/HIVE-8280
 Project: Hive
  Issue Type: Bug
  Components: CBO
Affects Versions: 0.14.0
Reporter: Mostafa Mokhtar
Assignee: Harish Butani
 Fix For: 0.14.0

 Attachments: HIVE-8280.1.patch, HIVE-8280.2.patch, HIVE-8280.3.patch


 When a filter is applied on PK side joins don't qualify as PK/FK join.
 In getUniqueKeys when a filter is applied on the table the child is no  
 longer a table scan.
 {code}
   public SetBitSet getUniqueKeys(ProjectRelBase rel, boolean ignoreNulls) {
 RelNode child = rel.getChild();
 if (!(child instanceof HiveTableScanRel)) {
   FunctionRelNode, Metadata fn = RelMdUniqueKeys.SOURCE.apply(
   rel.getClass(), BuiltInMetadata.UniqueKeys.class);
   return ((BuiltInMetadata.UniqueKeys) fn.apply(rel))
   .getUniqueKeys(ignoreNulls);
 } 
 {code}
 Repro 
 {code}
 with ss as 
 (select 
 ss_customer_sk, ss_item_sk, ss_ticket_number
 from
 store_sales,
 store
 where
 s_store_sk = ss_store_sk
 and s_market_id = 4), 
 sr as
 (select sr_customer_sk,sr_item_sk ,sr_ticket_number from store_returns, store 
 where s_store_sk = sr_store_sk and s_market_id=4) 
 select 
 count(*)
 from
 ss,
 sr
 where
 ss_customer_sk = sr_customer_sk
 and ss_item_sk = sr_item_sk
 and ss_ticket_number = sr_ticket_number;
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-6914) parquet-hive cannot write nested map (map value is map)

2014-10-08 Thread Mickael Lacour (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163244#comment-14163244
 ] 

Mickael Lacour commented on HIVE-6914:
--

[~langea], no the culprit is inside the method writeArray.
The wrong data was written.

Patch in progress

 parquet-hive cannot write nested map (map value is map)
 ---

 Key: HIVE-6914
 URL: https://issues.apache.org/jira/browse/HIVE-6914
 Project: Hive
  Issue Type: Bug
  Components: File Formats
Affects Versions: 0.12.0, 0.13.0
Reporter: Tongjie Chen

 // table schema (identical for both plain text version and parquet version)
 desc hive desc text_mmap;
 m map
 // sample nested map entry
 {level1:{level2_key1:value1,level2_key2:value2}}
 The following query will fail, 
 insert overwrite table parquet_mmap select * from text_mmap;
 Caused by: parquet.io.ParquetEncodingException: This should be an 
 ArrayWritable or MapWritable: 
 org.apache.hadoop.hive.ql.io.parquet.writable.BinaryWritable@f2f8106
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:85)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeArray(DataWritableWriter.java:118)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:80)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:82)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.write(DataWritableWriter.java:55)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriteSupport.write(DataWritableWriteSupport.java:59)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriteSupport.write(DataWritableWriteSupport.java:31)
 at 
 parquet.hadoop.InternalParquetRecordWriter.write(InternalParquetRecordWriter.java:115)
 at parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:81)
 at parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:37)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.ParquetRecordWriterWrapper.write(ParquetRecordWriterWrapper.java:77)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.ParquetRecordWriterWrapper.write(ParquetRecordWriterWrapper.java:90)
 at 
 org.apache.hadoop.hive.ql.exec.FileSinkOperator.processOp(FileSinkOperator.java:622)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at 
 org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:87)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at 
 org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:92)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:540)
 ... 9 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HIVE-8397) Approximated cardinality with HuperLogLog UDAF

2014-10-08 Thread Navis (JIRA)
Navis created HIVE-8397:
---

 Summary: Approximated cardinality with HuperLogLog UDAF
 Key: HIVE-8397
 URL: https://issues.apache.org/jira/browse/HIVE-8397
 Project: Hive
  Issue Type: Improvement
  Components: UDF
Reporter: Navis
Assignee: Navis
Priority: Trivial


Useful sometimes for quick estimation of bulk data. 
{noformat}
select hll(key), hll(value) from src;
{noformat}

Also can be used with hive.fetch.task.aggr=true;




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8397) Approximated cardinality with HyperLogLog UDAF

2014-10-08 Thread Navis (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Navis updated HIVE-8397:

Summary: Approximated cardinality with HyperLogLog UDAF  (was: Approximated 
cardinality with HuperLogLog UDAF)

 Approximated cardinality with HyperLogLog UDAF
 --

 Key: HIVE-8397
 URL: https://issues.apache.org/jira/browse/HIVE-8397
 Project: Hive
  Issue Type: Improvement
  Components: UDF
Reporter: Navis
Assignee: Navis
Priority: Trivial

 Useful sometimes for quick estimation of bulk data. 
 {noformat}
 select hll(key), hll(value) from src;
 {noformat}
 Also can be used with hive.fetch.task.aggr=true;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8397) Approximated cardinality with HyperLogLog UDAF

2014-10-08 Thread Navis (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Navis updated HIVE-8397:

Attachment: HIVE-8397.1.patch.txt

 Approximated cardinality with HyperLogLog UDAF
 --

 Key: HIVE-8397
 URL: https://issues.apache.org/jira/browse/HIVE-8397
 Project: Hive
  Issue Type: Improvement
  Components: UDF
Reporter: Navis
Assignee: Navis
Priority: Trivial
 Attachments: HIVE-8397.1.patch.txt


 Useful sometimes for quick estimation of bulk data. 
 {noformat}
 select hll(key), hll(value) from src;
 {noformat}
 Also can be used with hive.fetch.task.aggr=true;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8397) Approximated cardinality with HyperLogLog UDAF

2014-10-08 Thread Navis (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Navis updated HIVE-8397:

Status: Patch Available  (was: Open)

 Approximated cardinality with HyperLogLog UDAF
 --

 Key: HIVE-8397
 URL: https://issues.apache.org/jira/browse/HIVE-8397
 Project: Hive
  Issue Type: Improvement
  Components: UDF
Reporter: Navis
Assignee: Navis
Priority: Trivial
 Attachments: HIVE-8397.1.patch.txt


 Useful sometimes for quick estimation of bulk data. 
 {noformat}
 select hll(key), hll(value) from src;
 {noformat}
 Also can be used with hive.fetch.task.aggr=true;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (HIVE-8378) NPE in TezTask due to null counters

2014-10-08 Thread Navis (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Navis resolved HIVE-8378.
-
   Resolution: Duplicate
Fix Version/s: 0.14.0

 NPE in TezTask due to null counters
 ---

 Key: HIVE-8378
 URL: https://issues.apache.org/jira/browse/HIVE-8378
 Project: Hive
  Issue Type: Bug
  Components: Tez
Affects Versions: 0.13.1
 Environment: AWS EMR
Reporter: Kristof Vanbecelaere
 Fix For: 0.14.0


 The counters variable iterated over on line 177 can be null apparently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8315) CBO : Negate condition underestimates selectivity which results in an in-efficient plan

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1416#comment-1416
 ] 

Hive QA commented on HIVE-8315:
---



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673249/HIVE-8315.1.patch

{color:green}SUCCESS:{color} +1 6528 tests passed

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1150/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1150/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1150/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12673249

 CBO : Negate condition underestimates selectivity which results in an 
 in-efficient plan
 ---

 Key: HIVE-8315
 URL: https://issues.apache.org/jira/browse/HIVE-8315
 Project: Hive
  Issue Type: Bug
  Components: CBO
Affects Versions: 0.14.0
Reporter: Mostafa Mokhtar
Assignee: Harish Butani
 Fix For: 0.14.0

 Attachments: HIVE-8315.1.patch


 For TPC-DS Q64 the predicate cd1.cd_marital_status  cd2.cd_marital_status 
 under estimate the join selectivity by a huge margin and results in 
 in-efficient join order.
 This is a subset of the logical plan showing that item was joined very last
 {code}
 HiveJoinRel(condition=[=($0, $37)], 
 joinType=[inner]): rowcount = 1.0, cumulative cost = {6.386017602518958E8 
 rows, 0.0 cpu, 0.0 io}, id = 3790
   HiveJoinRel(condition=[=($0, $33)], 
 joinType=[inner]): rowcount = 1.0, cumulative cost = {6.386017582518958E8 
 rows, 0.0 cpu, 0.0 io}, id = 3067
 HiveFilterRel(condition=[($30, $32)]): 
 rowcount = 1.8252236387887635, cumulative cost = {6.386017554266721E8 rows, 
 0.0 cpu, 0.0 io}, id = 1153
   HiveProjectRel(ss_item_sk=[$2], 
 ss_customer_sk=[$3], ss_cdemo_sk=[$4], ss_hdemo_sk=[$5], ss_addr_sk=[$6], 
 ss_store_sk=[$7], ss_promo_sk=[$8], ss_ticket_number=[$9], 
 ss_wholesale_cost=[$10], ss_list_price=[$11], ss_coupon_amt=[$12], 
 ss_sold_date_sk=[$13], sr_item_sk=[$0], sr_ticket_number=[$1], 
 c_customer_sk=[$23], c_current_cdemo_sk=[$24], c_current_hdemo_sk=[$25], 
 c_current_addr_sk=[$26], c_first_shipto_date_sk=[$27], 
 c_first_sales_date_sk=[$28], d_date_sk=[$14], d_year=[$15], d_date_sk0=[$29], 
 d_year0=[$30], d_date_sk1=[$31], d_year1=[$32], s_store_sk=[$18], 
 s_store_name=[$19], s_zip=[$20], cd_demo_sk=[$16], cd_marital_status=[$17], 
 cd_demo_sk0=[$21], cd_marital_status0=[$22]): rowcount = 
 3.6246005783468924E7, cumulative cost = {6.386017554266721E8 rows, 0.0 cpu, 
 0.0 io}, id = 2312
 HiveJoinRel(condition=[AND(=($2, $0), 
 =($9, $1))], joinType=[inner]): rowcount = 3.6246005783468924E7, cumulative 
 cost = {6.386017554266721E8 rows, 0.0 cpu, 0.0 io}, id = 2310
   HiveProjectRel(sr_item_sk=[$1], 
 sr_ticket_number=[$8]): rowcount = 5.5578005E7, cumulative cost = {0.0 rows, 
 0.0 cpu, 0.0 io}, id = 912
 
 HiveTableScanRel(table=[[tpcds_bin_partitioned_orc_200_orig.store_returns]]): 
 rowcount = 5.5578005E7, cumulative cost = {0}, id = 62
   HiveJoinRel(condition=[=($1, $21)], 
 joinType=[inner]): rowcount = 1.2950939439433252E7, cumulative cost = 
 {5.700728109872389E8 rows, 0.0 cpu, 0.0 io}, id = 2308
 HiveJoinRel(condition=[=($5, 
 $16)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.629812800658973E8 rows, 0.0 cpu, 0.0 io}, id = 2301
   HiveJoinRel(condition=[=($2, 
 $14)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.574895371445558E8 rows, 0.0 cpu, 0.0 io}, id = 2299
 HiveJoinRel(condition=[=($11, 
 $12)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.500772062232143E8 rows, 0.0 cpu, 0.0 io}, id = 1898
   
 HiveProjectRel(ss_item_sk=[$1], ss_customer_sk=[$2], ss_cdemo_sk=[$3], 
 ss_hdemo_sk=[$4], ss_addr_sk=[$5], ss_store_sk=[$6], ss_promo_sk=[$7], 
 ss_ticket_number=[$8], ss_wholesale_cost=[$10], ss_list_price=[$11], 
 ss_coupon_amt=[$18], 

[jira] [Updated] (HIVE-6914) parquet-hive cannot write nested map (map value is map)

2014-10-08 Thread Mickael Lacour (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mickael Lacour updated HIVE-6914:
-
Attachment: HIVE-6914.1.patch

Patch to allow parquet-hive to write complex nested type as array of map, map 
of array as value, array of struct, ...

 parquet-hive cannot write nested map (map value is map)
 ---

 Key: HIVE-6914
 URL: https://issues.apache.org/jira/browse/HIVE-6914
 Project: Hive
  Issue Type: Bug
  Components: File Formats
Affects Versions: 0.12.0, 0.13.0
Reporter: Tongjie Chen
 Attachments: HIVE-6914.1.patch


 // table schema (identical for both plain text version and parquet version)
 desc hive desc text_mmap;
 m map
 // sample nested map entry
 {level1:{level2_key1:value1,level2_key2:value2}}
 The following query will fail, 
 insert overwrite table parquet_mmap select * from text_mmap;
 Caused by: parquet.io.ParquetEncodingException: This should be an 
 ArrayWritable or MapWritable: 
 org.apache.hadoop.hive.ql.io.parquet.writable.BinaryWritable@f2f8106
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:85)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeArray(DataWritableWriter.java:118)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:80)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:82)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.write(DataWritableWriter.java:55)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriteSupport.write(DataWritableWriteSupport.java:59)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriteSupport.write(DataWritableWriteSupport.java:31)
 at 
 parquet.hadoop.InternalParquetRecordWriter.write(InternalParquetRecordWriter.java:115)
 at parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:81)
 at parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:37)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.ParquetRecordWriterWrapper.write(ParquetRecordWriterWrapper.java:77)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.ParquetRecordWriterWrapper.write(ParquetRecordWriterWrapper.java:90)
 at 
 org.apache.hadoop.hive.ql.exec.FileSinkOperator.processOp(FileSinkOperator.java:622)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at 
 org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:87)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at 
 org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:92)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:540)
 ... 9 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-6914) parquet-hive cannot write nested map (map value is map)

2014-10-08 Thread Mickael Lacour (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mickael Lacour updated HIVE-6914:
-
Labels: parquet serialization  (was: )
Status: Patch Available  (was: Open)

[HIVE-6914] parquet-hive cannot write nested map (map value is map)

 * Change the way ArrayWritable was filled
 * Now parquet-hive can write complex nested type (array of map, map of 
array, struct ...)
 * Adding some qtests

 parquet-hive cannot write nested map (map value is map)
 ---

 Key: HIVE-6914
 URL: https://issues.apache.org/jira/browse/HIVE-6914
 Project: Hive
  Issue Type: Bug
  Components: File Formats
Affects Versions: 0.13.0, 0.12.0
Reporter: Tongjie Chen
  Labels: serialization, parquet
 Attachments: HIVE-6914.1.patch


 // table schema (identical for both plain text version and parquet version)
 desc hive desc text_mmap;
 m map
 // sample nested map entry
 {level1:{level2_key1:value1,level2_key2:value2}}
 The following query will fail, 
 insert overwrite table parquet_mmap select * from text_mmap;
 Caused by: parquet.io.ParquetEncodingException: This should be an 
 ArrayWritable or MapWritable: 
 org.apache.hadoop.hive.ql.io.parquet.writable.BinaryWritable@f2f8106
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:85)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeArray(DataWritableWriter.java:118)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:80)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.writeData(DataWritableWriter.java:82)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriter.write(DataWritableWriter.java:55)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriteSupport.write(DataWritableWriteSupport.java:59)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.DataWritableWriteSupport.write(DataWritableWriteSupport.java:31)
 at 
 parquet.hadoop.InternalParquetRecordWriter.write(InternalParquetRecordWriter.java:115)
 at parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:81)
 at parquet.hadoop.ParquetRecordWriter.write(ParquetRecordWriter.java:37)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.ParquetRecordWriterWrapper.write(ParquetRecordWriterWrapper.java:77)
 at 
 org.apache.hadoop.hive.ql.io.parquet.write.ParquetRecordWriterWrapper.write(ParquetRecordWriterWrapper.java:90)
 at 
 org.apache.hadoop.hive.ql.exec.FileSinkOperator.processOp(FileSinkOperator.java:622)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at 
 org.apache.hadoop.hive.ql.exec.SelectOperator.processOp(SelectOperator.java:87)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at 
 org.apache.hadoop.hive.ql.exec.TableScanOperator.processOp(TableScanOperator.java:92)
 at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:793)
 at org.apache.hadoop.hive.ql.exec.MapOperator.process(MapOperator.java:540)
 ... 9 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HIVE-8398) ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc

2014-10-08 Thread Zhichun Wu (JIRA)
Zhichun Wu created HIVE-8398:


 Summary: ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc
 Key: HIVE-8398
 URL: https://issues.apache.org/jira/browse/HIVE-8398
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.13.0, 0.14.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu


The following explain statement would fail  in hive 0.13 and trunk
with ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc exception:
{code}
create table test.t2( key string, value int);
explain select
   sum(u.value) value
from test.t2 u
group by u.key
having sum(u.value)  30;
{code}

The full stack trace:
{code}
java.lang.ClassCastException: org.apache.hadoop.hive.ql.plan.ExprNodeColumnDesc 
cannot be cast to org.apache.hadoop.hive.ql.plan.ExprNodeConstantDesc
at 
org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:1067)
at 
org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:90)
at 
org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatchAndReturn(DefaultGraphWalker.java:94)
at 
org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatch(DefaultGraphWalker.java:78)
at 
org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.walk(DefaultGraphWalker.java:132)
at 
org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.startWalking(DefaultGraphWalker.java:109)
at 
org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory.genExprNode(TypeCheckProcFactory.java:184)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genAllExprNodeDesc(SemanticAnalyzer.java:9561)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:9517)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:9488)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genFilterPlan(SemanticAnalyzer.java:2314)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genFilterPlan(SemanticAnalyzer.java:2295)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genHavingPlan(SemanticAnalyzer.java:2139)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPostGroupByBodyPlan(SemanticAnalyzer.java:8170)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genBodyPlan(SemanticAnalyzer.java:8133)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:8963)
at 
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9216)
at 
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:327)
at 
org.apache.hadoop.hive.ql.parse.ExplainSemanticAnalyzer.analyzeInternal(ExplainSemanticAnalyzer.java:64)
at 
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:327)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:422)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:322)
at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:975)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1040)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:911)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:901)
at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:268)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:220)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:423)
at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:792)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:686)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
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:212)
{code}

I think it's due to HIVE-3107.  HIVE-3107 introduces alternate mapping for a 
column in RowResolver.  While mapping the having clause in 
TypeCheckProcFactory, it first maps value to col_1(output of groupby clause) 
which has type of  ExprNodeColumnDesc (Before HIVE-3107, value is not 
recognized).  When it comes to u.value, it finds that u is a table alias 
but fails to cast nodeOutputs\[1\] to ExprNodeConstantDesc.  
Here I think we can use  the text attribute in the expr node as colAlias 
instead.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8398) ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc

2014-10-08 Thread Zhichun Wu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhichun Wu updated HIVE-8398:
-
Attachment: HIVE-8398.patch

 ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc
 -

 Key: HIVE-8398
 URL: https://issues.apache.org/jira/browse/HIVE-8398
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.13.0, 0.14.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
 Attachments: HIVE-8398.patch


 The following explain statement would fail  in hive 0.13 and trunk
 with ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc exception:
 {code}
 create table test.t2( key string, value int);
 explain select
sum(u.value) value
 from test.t2 u
 group by u.key
 having sum(u.value)  30;
 {code}
 The full stack trace:
 {code}
 java.lang.ClassCastException: 
 org.apache.hadoop.hive.ql.plan.ExprNodeColumnDesc cannot be cast to 
 org.apache.hadoop.hive.ql.plan.ExprNodeConstantDesc
 at 
 org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:1067)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:90)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatchAndReturn(DefaultGraphWalker.java:94)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatch(DefaultGraphWalker.java:78)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.walk(DefaultGraphWalker.java:132)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.startWalking(DefaultGraphWalker.java:109)
 at 
 org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory.genExprNode(TypeCheckProcFactory.java:184)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genAllExprNodeDesc(SemanticAnalyzer.java:9561)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:9517)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:9488)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genFilterPlan(SemanticAnalyzer.java:2314)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genFilterPlan(SemanticAnalyzer.java:2295)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genHavingPlan(SemanticAnalyzer.java:2139)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPostGroupByBodyPlan(SemanticAnalyzer.java:8170)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genBodyPlan(SemanticAnalyzer.java:8133)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:8963)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9216)
 at 
 org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:327)
 at 
 org.apache.hadoop.hive.ql.parse.ExplainSemanticAnalyzer.analyzeInternal(ExplainSemanticAnalyzer.java:64)
 at 
 org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:327)
 at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:422)
 at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:322)
 at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:975)
 at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1040)
 at org.apache.hadoop.hive.ql.Driver.run(Driver.java:911)
 at org.apache.hadoop.hive.ql.Driver.run(Driver.java:901)
 at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:268)
 at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:220)
 at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:423)
 at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:792)
 at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:686)
 at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
 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:212)
 {code}
 I think it's due to HIVE-3107.  HIVE-3107 introduces alternate mapping for a 
 column in RowResolver.  While mapping the having clause in 
 TypeCheckProcFactory, it first maps value to col_1(output of groupby 
 clause) which has type of  ExprNodeColumnDesc (Before HIVE-3107, value is 
 not recognized).  When it comes to u.value, it finds that u is a table 
 alias but fails to cast nodeOutputs\[1\] to ExprNodeConstantDesc.  
 Here I think we can use  the text attribute in the expr node as colAlias 
 instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8398) ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc

2014-10-08 Thread Zhichun Wu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhichun Wu updated HIVE-8398:
-
Status: Patch Available  (was: Open)

 ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc
 -

 Key: HIVE-8398
 URL: https://issues.apache.org/jira/browse/HIVE-8398
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.13.0, 0.14.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
 Attachments: HIVE-8398.patch


 The following explain statement would fail  in hive 0.13 and trunk
 with ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc exception:
 {code}
 create table test.t2( key string, value int);
 explain select
sum(u.value) value
 from test.t2 u
 group by u.key
 having sum(u.value)  30;
 {code}
 The full stack trace:
 {code}
 java.lang.ClassCastException: 
 org.apache.hadoop.hive.ql.plan.ExprNodeColumnDesc cannot be cast to 
 org.apache.hadoop.hive.ql.plan.ExprNodeConstantDesc
 at 
 org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:1067)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:90)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatchAndReturn(DefaultGraphWalker.java:94)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatch(DefaultGraphWalker.java:78)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.walk(DefaultGraphWalker.java:132)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.startWalking(DefaultGraphWalker.java:109)
 at 
 org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory.genExprNode(TypeCheckProcFactory.java:184)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genAllExprNodeDesc(SemanticAnalyzer.java:9561)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:9517)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genExprNodeDesc(SemanticAnalyzer.java:9488)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genFilterPlan(SemanticAnalyzer.java:2314)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genFilterPlan(SemanticAnalyzer.java:2295)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genHavingPlan(SemanticAnalyzer.java:2139)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPostGroupByBodyPlan(SemanticAnalyzer.java:8170)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genBodyPlan(SemanticAnalyzer.java:8133)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:8963)
 at 
 org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9216)
 at 
 org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:327)
 at 
 org.apache.hadoop.hive.ql.parse.ExplainSemanticAnalyzer.analyzeInternal(ExplainSemanticAnalyzer.java:64)
 at 
 org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:327)
 at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:422)
 at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:322)
 at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:975)
 at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1040)
 at org.apache.hadoop.hive.ql.Driver.run(Driver.java:911)
 at org.apache.hadoop.hive.ql.Driver.run(Driver.java:901)
 at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:268)
 at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:220)
 at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:423)
 at org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:792)
 at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:686)
 at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
 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:212)
 {code}
 I think it's due to HIVE-3107.  HIVE-3107 introduces alternate mapping for a 
 column in RowResolver.  While mapping the having clause in 
 TypeCheckProcFactory, it first maps value to col_1(output of groupby 
 clause) which has type of  ExprNodeColumnDesc (Before HIVE-3107, value is 
 not recognized).  When it comes to u.value, it finds that u is a table 
 alias but fails to cast nodeOutputs\[1\] to ExprNodeConstantDesc.  
 Here I think we can use  the text attribute in the expr node as colAlias 
 instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8395) CBO: enable by default

2014-10-08 Thread Xuefu Zhang (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163482#comment-14163482
 ] 

Xuefu Zhang commented on HIVE-8395:
---

{quote}
Switching over for .14 is late in the game 
{quote}

Agreed, especially considering the number issues that we are still having. It 
sounds reasonable to keep if off in 0.14 and on for trunk.

 CBO: enable by default
 --

 Key: HIVE-8395
 URL: https://issues.apache.org/jira/browse/HIVE-8395
 Project: Hive
  Issue Type: Sub-task
  Components: CBO
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.14.0

 Attachments: HIVE-8395.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8361) NPE in PTFOperator when there are empty partitions

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163519#comment-14163519
 ] 

Hive QA commented on HIVE-8361:
---



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673265/HIVE-8361.2.patch

{color:green}SUCCESS:{color} +1 6527 tests passed

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1151/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1151/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1151/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12673265

 NPE in PTFOperator when there are empty partitions
 --

 Key: HIVE-8361
 URL: https://issues.apache.org/jira/browse/HIVE-8361
 Project: Hive
  Issue Type: Bug
Reporter: Harish Butani
Assignee: Harish Butani
 Attachments: HIVE-8361.1.patch, HIVE-8361.2.patch


 Here is a simple query to reproduce this:
 {code}
 select sum(p_size) over (partition by p_mfgr )
 from part where p_mfgr = 'some non existent mfgr';
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [VOTE] officially stop supporting hadoop 0.20.x in hive 0.14 ?

2014-10-08 Thread Alan Gates

+1.

Alan.


Thejas Nair mailto:the...@hortonworks.com
October 7, 2014 at 15:53
I think it is time to revisit the support for hive support for hadoop
0.20. Trying to maintain support for it puts additional burden on hive
contributors.

The last hadoop 0.20.x version was released on Feb 2010. Hadoop 1.0
was released in Dec 2011.
I believe most users have moved on to hadoop 2.x or at least hadoop
1.x . The users if any that are still on hadoop 0.20 probably don't
tend to upgrade their hive versions as well.

With the move to maven for builds in hive 0.13, we don't have the
ability to compile against hadoop 0.20. (Nobody has complains about
that AFAIK). I am not sure if hive 0.13 works well against hadoop
0.20, as it is not clear if that combination is in use. Also, most
commercial vendors seem to be focussing on testing it against hadoop
2.x.

I think it is time to do away with this added burden of attempting to
support hadoop 0.20.x versions.

Here is my +1 for officially stopping support for hadoop 0.20.x in 
hive 0.14 .


Thanks,
Thejas



--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.


[jira] [Updated] (HIVE-8391) Comparion between TIMESTAMP and Integer types goes to STRING as common comparison denominator instead of a numeric type

2014-10-08 Thread Matt McCline (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-8391:
---
Attachment: vectorization_7.q

 Comparion between TIMESTAMP and Integer types goes to STRING as common 
 comparison denominator instead of a numeric type
 -

 Key: HIVE-8391
 URL: https://issues.apache.org/jira/browse/HIVE-8391
 Project: Hive
  Issue Type: Bug
  Components: CBO, Logical Optimizer
Affects Versions: 0.14.0
Reporter: Matt McCline
Assignee: Jason Dere
Priority: Critical
 Fix For: 0.14.0

 Attachments: HIVE-8391.1.patch, vectorization_7.q


 Discovered while investigating why vectorization_7.q has different results 
 for non-vectorized [+CBO] and vectorized [+CBO].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8270) JDBC uber jar is missing some classes required in secure setup.

2014-10-08 Thread Damien Carol (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163546#comment-14163546
 ] 

Damien Carol commented on HIVE-8270:


There still have a bug in Tomcat.
{noformat}
INFO: 
validateJarFile(/usr/share/apache-tomcat-7.0.50/webapps/SmartDataDev/WEB-INF/lib/hive-jdbc-0.14.0-SNAPSHOT-standalone.jar)
 - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: 
javax/servlet/Servlet.class
Oct 08, 2014 4:13:02 PM org.apache.catalina.startup.HostConfig deployWAR
{noformat}

After few tests, I see many javax.* and javax.jdo.* classes in the ubber jar. 
It's a real problem.
Avoiding the classes in javax.* namespace will reduce heavily the size of the 
jar.

I think the JDBC standalone jar is poor quality currently. It is unusable in 
J2EE environment.

Also why embedded JDO classes ? 

 JDBC uber jar is missing some classes required in secure setup.
 ---

 Key: HIVE-8270
 URL: https://issues.apache.org/jira/browse/HIVE-8270
 Project: Hive
  Issue Type: Bug
  Components: JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
  Labels: TODOC14
 Fix For: 0.14.0

 Attachments: HIVE-8270.1.patch


 JDBC uber jar is missing some required classes for a secure setup.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8391) Comparion between TIMESTAMP and Integer types goes to STRING as common comparison denominator instead of a numeric type

2014-10-08 Thread Matt McCline (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163548#comment-14163548
 ] 

Matt McCline commented on HIVE-8391:


I attached a modified version of 
../../ql/src/test/results/clientpositive/vectorization_7.q that first makes 
sure the query had a Map stage and vectorizes instead of the Fetch stage (SET 
hive.fetch.task.conversion=minimal).

I get differences when vectorization is turned off and on with this q file.  
Not sure what is going on.  Haven't tried CBO yet.

 Comparion between TIMESTAMP and Integer types goes to STRING as common 
 comparison denominator instead of a numeric type
 -

 Key: HIVE-8391
 URL: https://issues.apache.org/jira/browse/HIVE-8391
 Project: Hive
  Issue Type: Bug
  Components: CBO, Logical Optimizer
Affects Versions: 0.14.0
Reporter: Matt McCline
Assignee: Jason Dere
Priority: Critical
 Fix For: 0.14.0

 Attachments: HIVE-8391.1.patch, vectorization_7.q


 Discovered while investigating why vectorization_7.q has different results 
 for non-vectorized [+CBO] and vectorized [+CBO].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8391) Comparion between TIMESTAMP and Integer types goes to STRING as common comparison denominator instead of a numeric type

2014-10-08 Thread Matt McCline (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163556#comment-14163556
 ] 

Matt McCline commented on HIVE-8391:


(Note the query does compare a timestamp column against an integer not a 
double).

 Comparion between TIMESTAMP and Integer types goes to STRING as common 
 comparison denominator instead of a numeric type
 -

 Key: HIVE-8391
 URL: https://issues.apache.org/jira/browse/HIVE-8391
 Project: Hive
  Issue Type: Bug
  Components: CBO, Logical Optimizer
Affects Versions: 0.14.0
Reporter: Matt McCline
Assignee: Jason Dere
Priority: Critical
 Fix For: 0.14.0

 Attachments: HIVE-8391.1.patch, vectorization_7.q


 Discovered while investigating why vectorization_7.q has different results 
 for non-vectorized [+CBO] and vectorized [+CBO].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Issue Comment Deleted] (HIVE-8389) Disable CBO when indexes are used

2014-10-08 Thread Ashutosh Chauhan (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Chauhan updated HIVE-8389:
---
Comment: was deleted

(was: related to https://hortonworks.jira.com/browse/BUG-24307
)

 Disable CBO when indexes are used
 -

 Key: HIVE-8389
 URL: https://issues.apache.org/jira/browse/HIVE-8389
 Project: Hive
  Issue Type: Bug
Reporter: Pengcheng Xiong
Assignee: Pengcheng Xiong
 Attachments: HIVE-8389.1.patch


 Disable CBO when indexes are used



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-7925) extend current partition status extrapolation to support all DBs

2014-10-08 Thread Ashutosh Chauhan (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Chauhan updated HIVE-7925:
---
Description: extend current partition status extrapolation only supports 
Derby.  (was: extend current partition status extrapolation only supports Derby.
That is why we got errors such as 
https://hortonworks.jira.com/browse/BUG-21983)

 extend current partition status extrapolation to support all DBs
 

 Key: HIVE-7925
 URL: https://issues.apache.org/jira/browse/HIVE-7925
 Project: Hive
  Issue Type: Improvement
  Components: Metastore
Affects Versions: 0.14.0
Reporter: Pengcheng Xiong
Assignee: Pengcheng Xiong
Priority: Minor
 Fix For: 0.14.0

 Attachments: HIVE-7925.1.patch


 extend current partition status extrapolation only supports Derby.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8366) CBO fails if there is a table sample in subquery

2014-10-08 Thread Ashutosh Chauhan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163610#comment-14163610
 ] 

Ashutosh Chauhan commented on HIVE-8366:


Committed to 0.14

 CBO fails if there is a table sample in subquery
 

 Key: HIVE-8366
 URL: https://issues.apache.org/jira/browse/HIVE-8366
 Project: Hive
  Issue Type: Bug
  Components: CBO, Logical Optimizer
Affects Versions: 0.14.0
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan
 Fix For: 0.14.0

 Attachments: HIVE-8366.patch


 Bail out from cbo in such cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8366) CBO fails if there is a table sample in subquery

2014-10-08 Thread Ashutosh Chauhan (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Chauhan updated HIVE-8366:
---
Fix Version/s: (was: 0.15.0)
   0.14.0

 CBO fails if there is a table sample in subquery
 

 Key: HIVE-8366
 URL: https://issues.apache.org/jira/browse/HIVE-8366
 Project: Hive
  Issue Type: Bug
  Components: CBO, Logical Optimizer
Affects Versions: 0.14.0
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan
 Fix For: 0.14.0

 Attachments: HIVE-8366.patch


 Bail out from cbo in such cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8315) CBO : Negate condition underestimates selectivity which results in an in-efficient plan

2014-10-08 Thread Ashutosh Chauhan (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Chauhan updated HIVE-8315:
---
   Resolution: Fixed
Fix Version/s: (was: 0.14.0)
   0.15.0
   Status: Resolved  (was: Patch Available)

Committed to trunk. Thanks, Harish!
[~vikram.dixit] it will be good to have this in 0.14 as well.

 CBO : Negate condition underestimates selectivity which results in an 
 in-efficient plan
 ---

 Key: HIVE-8315
 URL: https://issues.apache.org/jira/browse/HIVE-8315
 Project: Hive
  Issue Type: Bug
  Components: CBO
Affects Versions: 0.14.0
Reporter: Mostafa Mokhtar
Assignee: Harish Butani
 Fix For: 0.15.0

 Attachments: HIVE-8315.1.patch


 For TPC-DS Q64 the predicate cd1.cd_marital_status  cd2.cd_marital_status 
 under estimate the join selectivity by a huge margin and results in 
 in-efficient join order.
 This is a subset of the logical plan showing that item was joined very last
 {code}
 HiveJoinRel(condition=[=($0, $37)], 
 joinType=[inner]): rowcount = 1.0, cumulative cost = {6.386017602518958E8 
 rows, 0.0 cpu, 0.0 io}, id = 3790
   HiveJoinRel(condition=[=($0, $33)], 
 joinType=[inner]): rowcount = 1.0, cumulative cost = {6.386017582518958E8 
 rows, 0.0 cpu, 0.0 io}, id = 3067
 HiveFilterRel(condition=[($30, $32)]): 
 rowcount = 1.8252236387887635, cumulative cost = {6.386017554266721E8 rows, 
 0.0 cpu, 0.0 io}, id = 1153
   HiveProjectRel(ss_item_sk=[$2], 
 ss_customer_sk=[$3], ss_cdemo_sk=[$4], ss_hdemo_sk=[$5], ss_addr_sk=[$6], 
 ss_store_sk=[$7], ss_promo_sk=[$8], ss_ticket_number=[$9], 
 ss_wholesale_cost=[$10], ss_list_price=[$11], ss_coupon_amt=[$12], 
 ss_sold_date_sk=[$13], sr_item_sk=[$0], sr_ticket_number=[$1], 
 c_customer_sk=[$23], c_current_cdemo_sk=[$24], c_current_hdemo_sk=[$25], 
 c_current_addr_sk=[$26], c_first_shipto_date_sk=[$27], 
 c_first_sales_date_sk=[$28], d_date_sk=[$14], d_year=[$15], d_date_sk0=[$29], 
 d_year0=[$30], d_date_sk1=[$31], d_year1=[$32], s_store_sk=[$18], 
 s_store_name=[$19], s_zip=[$20], cd_demo_sk=[$16], cd_marital_status=[$17], 
 cd_demo_sk0=[$21], cd_marital_status0=[$22]): rowcount = 
 3.6246005783468924E7, cumulative cost = {6.386017554266721E8 rows, 0.0 cpu, 
 0.0 io}, id = 2312
 HiveJoinRel(condition=[AND(=($2, $0), 
 =($9, $1))], joinType=[inner]): rowcount = 3.6246005783468924E7, cumulative 
 cost = {6.386017554266721E8 rows, 0.0 cpu, 0.0 io}, id = 2310
   HiveProjectRel(sr_item_sk=[$1], 
 sr_ticket_number=[$8]): rowcount = 5.5578005E7, cumulative cost = {0.0 rows, 
 0.0 cpu, 0.0 io}, id = 912
 
 HiveTableScanRel(table=[[tpcds_bin_partitioned_orc_200_orig.store_returns]]): 
 rowcount = 5.5578005E7, cumulative cost = {0}, id = 62
   HiveJoinRel(condition=[=($1, $21)], 
 joinType=[inner]): rowcount = 1.2950939439433252E7, cumulative cost = 
 {5.700728109872389E8 rows, 0.0 cpu, 0.0 io}, id = 2308
 HiveJoinRel(condition=[=($5, 
 $16)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.629812800658973E8 rows, 0.0 cpu, 0.0 io}, id = 2301
   HiveJoinRel(condition=[=($2, 
 $14)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.574895371445558E8 rows, 0.0 cpu, 0.0 io}, id = 2299
 HiveJoinRel(condition=[=($11, 
 $12)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.500772062232143E8 rows, 0.0 cpu, 0.0 io}, id = 1898
   
 HiveProjectRel(ss_item_sk=[$1], ss_customer_sk=[$2], ss_cdemo_sk=[$3], 
 ss_hdemo_sk=[$4], ss_addr_sk=[$5], ss_store_sk=[$6], ss_promo_sk=[$7], 
 ss_ticket_number=[$8], ss_wholesale_cost=[$10], ss_list_price=[$11], 
 ss_coupon_amt=[$18], ss_sold_date_sk=[$22]): rowcount = 5.50076554E8, 
 cumulative cost = {0.0 rows, 0.0 cpu, 0.0 io}, id = 909
 
 HiveTableScanRel(table=[[tpcds_bin_partitioned_orc_200_orig.store_sales]]): 
 rowcount = 5.50076554E8, cumulative cost = {0}, id = 55{code}
 Query 
 {code}
 select cs1.product_name ,cs1.store_name ,cs1.store_zip ,cs1.b_street_number 
 ,cs1.b_streen_name ,cs1.b_city
  ,cs1.b_zip ,cs1.c_street_number ,cs1.c_street_name ,cs1.c_city 
 ,cs1.c_zip ,cs1.syear ,cs1.cnt
  ,cs1.s1 ,cs1.s2 ,cs1.s3
  ,cs2.s1 ,cs2.s2 ,cs2.s3 ,cs2.syear ,cs2.cnt
 from
 (select i_product_name as 

[jira] [Commented] (HIVE-8315) CBO : Negate condition underestimates selectivity which results in an in-efficient plan

2014-10-08 Thread Vikram Dixit K (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163650#comment-14163650
 ] 

Vikram Dixit K commented on HIVE-8315:
--

+1 for 0.14

 CBO : Negate condition underestimates selectivity which results in an 
 in-efficient plan
 ---

 Key: HIVE-8315
 URL: https://issues.apache.org/jira/browse/HIVE-8315
 Project: Hive
  Issue Type: Bug
  Components: CBO
Affects Versions: 0.14.0
Reporter: Mostafa Mokhtar
Assignee: Harish Butani
 Fix For: 0.15.0

 Attachments: HIVE-8315.1.patch


 For TPC-DS Q64 the predicate cd1.cd_marital_status  cd2.cd_marital_status 
 under estimate the join selectivity by a huge margin and results in 
 in-efficient join order.
 This is a subset of the logical plan showing that item was joined very last
 {code}
 HiveJoinRel(condition=[=($0, $37)], 
 joinType=[inner]): rowcount = 1.0, cumulative cost = {6.386017602518958E8 
 rows, 0.0 cpu, 0.0 io}, id = 3790
   HiveJoinRel(condition=[=($0, $33)], 
 joinType=[inner]): rowcount = 1.0, cumulative cost = {6.386017582518958E8 
 rows, 0.0 cpu, 0.0 io}, id = 3067
 HiveFilterRel(condition=[($30, $32)]): 
 rowcount = 1.8252236387887635, cumulative cost = {6.386017554266721E8 rows, 
 0.0 cpu, 0.0 io}, id = 1153
   HiveProjectRel(ss_item_sk=[$2], 
 ss_customer_sk=[$3], ss_cdemo_sk=[$4], ss_hdemo_sk=[$5], ss_addr_sk=[$6], 
 ss_store_sk=[$7], ss_promo_sk=[$8], ss_ticket_number=[$9], 
 ss_wholesale_cost=[$10], ss_list_price=[$11], ss_coupon_amt=[$12], 
 ss_sold_date_sk=[$13], sr_item_sk=[$0], sr_ticket_number=[$1], 
 c_customer_sk=[$23], c_current_cdemo_sk=[$24], c_current_hdemo_sk=[$25], 
 c_current_addr_sk=[$26], c_first_shipto_date_sk=[$27], 
 c_first_sales_date_sk=[$28], d_date_sk=[$14], d_year=[$15], d_date_sk0=[$29], 
 d_year0=[$30], d_date_sk1=[$31], d_year1=[$32], s_store_sk=[$18], 
 s_store_name=[$19], s_zip=[$20], cd_demo_sk=[$16], cd_marital_status=[$17], 
 cd_demo_sk0=[$21], cd_marital_status0=[$22]): rowcount = 
 3.6246005783468924E7, cumulative cost = {6.386017554266721E8 rows, 0.0 cpu, 
 0.0 io}, id = 2312
 HiveJoinRel(condition=[AND(=($2, $0), 
 =($9, $1))], joinType=[inner]): rowcount = 3.6246005783468924E7, cumulative 
 cost = {6.386017554266721E8 rows, 0.0 cpu, 0.0 io}, id = 2310
   HiveProjectRel(sr_item_sk=[$1], 
 sr_ticket_number=[$8]): rowcount = 5.5578005E7, cumulative cost = {0.0 rows, 
 0.0 cpu, 0.0 io}, id = 912
 
 HiveTableScanRel(table=[[tpcds_bin_partitioned_orc_200_orig.store_returns]]): 
 rowcount = 5.5578005E7, cumulative cost = {0}, id = 62
   HiveJoinRel(condition=[=($1, $21)], 
 joinType=[inner]): rowcount = 1.2950939439433252E7, cumulative cost = 
 {5.700728109872389E8 rows, 0.0 cpu, 0.0 io}, id = 2308
 HiveJoinRel(condition=[=($5, 
 $16)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.629812800658973E8 rows, 0.0 cpu, 0.0 io}, id = 2301
   HiveJoinRel(condition=[=($2, 
 $14)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.574895371445558E8 rows, 0.0 cpu, 0.0 io}, id = 2299
 HiveJoinRel(condition=[=($11, 
 $12)], joinType=[inner]): rowcount = 5491530.921341597, cumulative cost = 
 {5.500772062232143E8 rows, 0.0 cpu, 0.0 io}, id = 1898
   
 HiveProjectRel(ss_item_sk=[$1], ss_customer_sk=[$2], ss_cdemo_sk=[$3], 
 ss_hdemo_sk=[$4], ss_addr_sk=[$5], ss_store_sk=[$6], ss_promo_sk=[$7], 
 ss_ticket_number=[$8], ss_wholesale_cost=[$10], ss_list_price=[$11], 
 ss_coupon_amt=[$18], ss_sold_date_sk=[$22]): rowcount = 5.50076554E8, 
 cumulative cost = {0.0 rows, 0.0 cpu, 0.0 io}, id = 909
 
 HiveTableScanRel(table=[[tpcds_bin_partitioned_orc_200_orig.store_sales]]): 
 rowcount = 5.50076554E8, cumulative cost = {0}, id = 55{code}
 Query 
 {code}
 select cs1.product_name ,cs1.store_name ,cs1.store_zip ,cs1.b_street_number 
 ,cs1.b_streen_name ,cs1.b_city
  ,cs1.b_zip ,cs1.c_street_number ,cs1.c_street_name ,cs1.c_city 
 ,cs1.c_zip ,cs1.syear ,cs1.cnt
  ,cs1.s1 ,cs1.s2 ,cs1.s3
  ,cs2.s1 ,cs2.s2 ,cs2.s3 ,cs2.syear ,cs2.cnt
 from
 (select i_product_name as product_name ,i_item_sk as item_sk ,s_store_name as 
 store_name
  ,s_zip as store_zip ,ad1.ca_street_number as b_street_number 
 ,ad1.ca_street_name as b_streen_name
  

[jira] [Commented] (HIVE-8270) JDBC uber jar is missing some classes required in secure setup.

2014-10-08 Thread Ashutosh Chauhan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163741#comment-14163741
 ] 

Ashutosh Chauhan commented on HIVE-8270:


[~damien.carol] Now that we have settled on the question that this jar is not 
meant to be used for HS2 embedded mode, (as discussed on this jira). I agree 
javax.* and jdo classes are baggage. We should explore possibility to excluding 
those. Feel free to open a new jira and attach a patch (if you have worked out 
something).

 JDBC uber jar is missing some classes required in secure setup.
 ---

 Key: HIVE-8270
 URL: https://issues.apache.org/jira/browse/HIVE-8270
 Project: Hive
  Issue Type: Bug
  Components: JDBC
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
  Labels: TODOC14
 Fix For: 0.14.0

 Attachments: HIVE-8270.1.patch


 JDBC uber jar is missing some required classes for a secure setup.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8363) AccumuloStorageHandler compile failure hadoop-1

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163748#comment-14163748
 ] 

Hive QA commented on HIVE-8363:
---



{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673269/HIVE-8363.1.patch

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 6528 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_parallel
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_schemeAuthority
{noformat}

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1152/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1152/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1152/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12673269

 AccumuloStorageHandler compile failure hadoop-1
 ---

 Key: HIVE-8363
 URL: https://issues.apache.org/jira/browse/HIVE-8363
 Project: Hive
  Issue Type: Bug
  Components: StorageHandler
Reporter: Szehon Ho
Assignee: Josh Elser
Priority: Blocker
 Fix For: 0.14.0

 Attachments: HIVE-8363.1.patch


 There's an error about AccumuloStorageHandler compiling on hadoop-1.  It 
 seems the signature of split() is not the same.  Looks like we can should use 
 another utils to fix this.
 {code}
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
 on project hive-accumulo-handler: Compilation failure
 [ERROR] 
 /data/hive-ptest/working/apache-svn-trunk-source/accumulo-handler/src/java/org/apache/hadoop/hive/accumulo/columns/ColumnMapper.java:[57,52]
  no suitable method found for split(java.lang.String,char)
 [ERROR] method 
 org.apache.hadoop.util.StringUtils.split(java.lang.String,char,char) is not 
 applicable
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-6915) Hive Hbase queries fail on secure Tez cluster

2014-10-08 Thread Naveen Gangam (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163767#comment-14163767
 ] 

Naveen Gangam commented on HIVE-6915:
-

I am using the fix from the patch with Hive 0.13 and I continue to see the 
issue with Tez while it works fine with MR.
I am running a simple SELECT count(*) from hbasetable;

{code}
2014-10-08 08:12:39,910 FATAL [InputInitializer [Map 1] #0] 
org.apache.hadoop.ipc.RpcClient: SASL authentication failed. The most likely 
cause is missing or invalid credentials. Consider 'kinit'.
javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: 
No valid credentials provided (Mechanism level: Failed to find any Kerberos 
tgt)]
at 
com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
at 
org.apache.hadoop.hbase.security.HBaseSaslRpcClient.saslConnect(HBaseSaslRpcClient.java:179)
at 
org.apache.hadoop.hbase.ipc.RpcClient$Connection.setupSaslConnection(RpcClient.java:770)
at 
org.apache.hadoop.hbase.ipc.RpcClient$Connection.access$600(RpcClient.java:357)
at 
org.apache.hadoop.hbase.ipc.RpcClient$Connection$2.run(RpcClient.java:891)
at 
org.apache.hadoop.hbase.ipc.RpcClient$Connection$2.run(RpcClient.java:888)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
at 
org.apache.hadoop.hbase.ipc.RpcClient$Connection.setupIOstreams(RpcClient.java:888)
at 
org.apache.hadoop.hbase.ipc.RpcClient.getConnection(RpcClient.java:1543)
at org.apache.hadoop.hbase.ipc.RpcClient.call(RpcClient.java:1442)
at 
org.apache.hadoop.hbase.ipc.RpcClient.callBlockingMethod(RpcClient.java:1661)
at 
org.apache.hadoop.hbase.ipc.RpcClient$BlockingRpcChannelImplementation.callBlockingMethod(RpcClient.java:1719)
at 
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$BlockingStub.scan(ClientProtos.java:29990)
at 
org.apache.hadoop.hbase.client.ScannerCallable.openScanner(ScannerCallable.java:308)
at 
org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:164)
at 
org.apache.hadoop.hbase.client.ScannerCallable.call(ScannerCallable.java:59)
at 
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:114)
at 
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:90)
at 
org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:283)
at 
org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:188)
at 
org.apache.hadoop.hbase.client.ClientScanner.init(ClientScanner.java:183)
at 
org.apache.hadoop.hbase.client.ClientScanner.init(ClientScanner.java:110)
at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:738)
at 
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:178)
at 
org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:82)
at 
org.apache.hadoop.hbase.client.MetaScanner.allTableRegions(MetaScanner.java:282)
at 
org.apache.hadoop.hbase.client.HTable.getRegionLocations(HTable.java:616)
at 
org.apache.hadoop.hbase.util.RegionSizeCalculator.init(RegionSizeCalculator.java:79)
at 
org.apache.hadoop.hbase.util.RegionSizeCalculator.init(RegionSizeCalculator.java:64)
at 
org.apache.hadoop.hbase.mapreduce.TableInputFormatBase.getSplits(TableInputFormatBase.java:160)
at 
org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat.getSplits(HiveHBaseTableInputFormat.java:482)
at 
org.apache.hadoop.hive.ql.io.HiveInputFormat.addSplitsForGroup(HiveInputFormat.java:291)
at 
org.apache.hadoop.hive.ql.io.HiveInputFormat.getSplits(HiveInputFormat.java:372)
at 
org.apache.hadoop.mapred.split.TezGroupedSplitsInputFormat.getSplits(TezGroupedSplitsInputFormat.java:68)
at 
org.apache.tez.mapreduce.hadoop.MRHelpers.generateOldSplits(MRHelpers.java:263)
at 
org.apache.tez.mapreduce.common.MRInputAMSplitGenerator.initialize(MRInputAMSplitGenerator.java:139)
at 
org.apache.tez.dag.app.dag.RootInputInitializerRunner$InputInitializerCallable$1.run(RootInputInitializerRunner.java:154)
at 
org.apache.tez.dag.app.dag.RootInputInitializerRunner$InputInitializerCallable$1.run(RootInputInitializerRunner.java:146)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
at 

[jira] [Commented] (HIVE-8354) HIVE-7156 introduced required dependency on tez

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163766#comment-14163766
 ] 

Hive QA commented on HIVE-8354:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673279/HIVE-8354.1.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1153/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1153/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1153/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8374) schematool fails on Postgres versions 9.2

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163770#comment-14163770
 ] 

Hive QA commented on HIVE-8374:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673282/HIVE-8374.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1154/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1154/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1154/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-7733) Ambiguous column reference error on query

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163776#comment-14163776
 ] 

Hive QA commented on HIVE-7733:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673292/HIVE-7733.6.patch.txt

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1156/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1156/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1156/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8357) Path type entities should use qualified path rather than string

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163782#comment-14163782
 ] 

Hive QA commented on HIVE-8357:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673295/HIVE-8357.2.patch.txt

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1157/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1157/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1157/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-6198) ORC file and struct column names are case sensitive

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163786#comment-14163786
 ] 

Hive QA commented on HIVE-6198:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673317/HIVE-6198.3.patch.txt

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1158/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1158/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1158/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8367) delete writes records in wrong order in some cases

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163793#comment-14163793
 ] 

Hive QA commented on HIVE-8367:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673376/HIVE-8367.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1159/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1159/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1159/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8381) Update hive version on trunk to 0.15

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163795#comment-14163795
 ] 

Hive QA commented on HIVE-8381:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673531/HIVE-8381.2.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1160/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1160/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1160/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hive-ptest/working/scratch/source-prep.sh' failed with exit 
status 1 and output '+ [[ -n /usr/java/jdk1.7.0_45-cloudera ]]
+ export JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ export 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-maven-3.0.5/bin:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-maven-3.0.5/bin:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ cd /data/hive-ptest/working/
+ tee /data/hive-ptest/logs/PreCommit-HIVE-TRUNK-Build-1160/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ svn = \s\v\n ]]
+ [[ -n '' ]]
+ [[ -d apache-svn-trunk-source ]]
+ [[ ! -d apache-svn-trunk-source/.svn ]]
+ [[ ! -d apache-svn-trunk-source ]]
+ cd apache-svn-trunk-source
+ svn revert -R .
Reverted 'ql/src/test/results/clientpositive/tez/delete_all_partitioned.q.out'
Reverted 'ql/src/test/results/clientpositive/tez/update_all_partitioned.q.out'
Reverted 'ql/src/test/results/clientpositive/delete_all_partitioned.q.out'
Reverted 'ql/src/test/results/clientpositive/update_all_partitioned.q.out'
Reverted 
'ql/src/java/org/apache/hadoop/hive/ql/parse/UpdateDeleteSemanticAnalyzer.java'
Reverted 'ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java'
++ egrep -v '^X|^Performing status on external'
++ awk '{print $2}'
++ svn status --no-ignore
+ rm -rf target datanucleus.log ant/target shims/0.20/target shims/0.20S/target 
shims/0.23/target shims/aggregator/target shims/common/target 
shims/common-secure/target metastore/target common/target common/src/gen 
serde/target ql/target
+ svn update

Fetching external item into 'hcatalog/src/test/e2e/harness'
External at revision 1630182.

At revision 1630182.
+ patchCommandPath=/data/hive-ptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hive-ptest/working/scratch/build.patch
+ [[ -f /data/hive-ptest/working/scratch/build.patch ]]
+ chmod +x /data/hive-ptest/working/scratch/smart-apply-patch.sh
+ /data/hive-ptest/working/scratch/smart-apply-patch.sh 
/data/hive-ptest/working/scratch/build.patch
Going to apply patch with: patch -p0
patching file hcatalog/core/pom.xml
patching file hcatalog/hcatalog-pig-adapter/pom.xml
patching file hcatalog/server-extensions/pom.xml
patching file hcatalog/streaming/pom.xml
patching file hcatalog/webhcat/java-client/pom.xml
patching file hcatalog/webhcat/svr/pom.xml
patching file pom.xml
+ [[ maven == \m\a\v\e\n ]]
+ rm -rf /data/hive-ptest/working/maven/org/apache/hive
+ mvn -B clean install -DskipTests 
-Dmaven.repo.local=/data/hive-ptest/working/maven -Phadoop-2
[INFO] Scanning for projects...
[ERROR] The build could not read 18 projects - [Help 1]
[ERROR]   
[ERROR]   The project org.apache.hive:hive-accumulo-handler:0.14.0-SNAPSHOT 
(/data/hive-ptest/working/apache-svn-trunk-source/accumulo-handler/pom.xml) has 
1 error
[ERROR] Non-resolvable parent POM: Could not find artifact 
org.apache.hive:hive:pom:0.14.0-SNAPSHOT and 'parent.relativePath' points at 
wrong local POM @ line 19, column 11 - [Help 2]
[ERROR]   
[ERROR]   The project org.apache.hive:hive-ant:0.14.0-SNAPSHOT 
(/data/hive-ptest/working/apache-svn-trunk-source/ant/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact 
org.apache.hive:hive:pom:0.14.0-SNAPSHOT and 'parent.relativePath' points at 
wrong local POM @ line 19, column 11 - [Help 2]
[ERROR]   
[ERROR]   The project org.apache.hive:hive-beeline:0.14.0-SNAPSHOT 

[jira] [Created] (HIVE-8399) Build failure on trunk

2014-10-08 Thread Vaibhav Gumashta (JIRA)
Vaibhav Gumashta created HIVE-8399:
--

 Summary: Build failure on trunk
 Key: HIVE-8399
 URL: https://issues.apache.org/jira/browse/HIVE-8399
 Project: Hive
  Issue Type: Bug
Reporter: Vaibhav Gumashta
Priority: Blocker






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8368) compactor is improperly writing delete records in base file

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163808#comment-14163808
 ] 

Hive QA commented on HIVE-8368:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673401/HIVE-8368.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1162/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1162/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1162/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Updated] (HIVE-8399) Build failure on trunk

2014-10-08 Thread Vaibhav Gumashta (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Gumashta updated HIVE-8399:
---
Affects Version/s: 0.14.0

 Build failure on trunk
 --

 Key: HIVE-8399
 URL: https://issues.apache.org/jira/browse/HIVE-8399
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Priority: Blocker

 {code}
 Downloading: 
 http://repo.maven.apache.org/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO] 
 [INFO] Hive .. SUCCESS [  2.591 s]
 [INFO] Hive Shims Common . SUCCESS [  1.774 s]
 [INFO] Hive Shims 0.20 ... SUCCESS [  0.656 s]
 [INFO] Hive Shims Secure Common .. SUCCESS [  0.954 s]
 [INFO] Hive Shims 0.20S .. SUCCESS [  0.516 s]
 [INFO] Hive Shims 0.23 ... SUCCESS [  1.769 s]
 [INFO] Hive Shims  SUCCESS [  0.192 s]
 [INFO] Hive Common ... SUCCESS [  3.753 s]
 [INFO] Hive Serde  SUCCESS [  3.005 s]
 [INFO] Hive Metastore  SUCCESS [ 10.376 s]
 [INFO] Hive Ant Utilities  SUCCESS [  0.266 s]
 [INFO] Hive Query Language ... FAILURE [ 10.606 s]
 [INFO] Hive Service .. SKIPPED
 [INFO] Hive Accumulo Handler . SKIPPED
 [INFO] Hive JDBC . SKIPPED
 [INFO] Hive Beeline .. SKIPPED
 [INFO] Hive CLI .. SKIPPED
 [INFO] Hive Contrib .. SKIPPED
 [INFO] Hive HBase Handler  SKIPPED
 [INFO] Hive HCatalog . SKIPPED
 [INFO] Hive HCatalog Core  SKIPPED
 [INFO] Hive HCatalog Pig Adapter . SKIPPED
 [INFO] Hive HCatalog Server Extensions ... SKIPPED
 [INFO] Hive HCatalog Webhcat Java Client . SKIPPED
 [INFO] Hive HCatalog Webhcat . SKIPPED
 [INFO] Hive HCatalog Streaming ... SKIPPED
 [INFO] Hive HWI .. SKIPPED
 [INFO] Hive ODBC . SKIPPED
 [INFO] Hive Shims Aggregator . SKIPPED
 [INFO] Hive TestUtils  SKIPPED
 [INFO] Hive Packaging  SKIPPED
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 37.318 s
 [INFO] Finished at: 2014-10-08T10:16:32-08:00
 [INFO] Final Memory: 54M/355M
 [INFO] 
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) 
 on project hive-exec: Error resolving project artifact: Could not transfer 
 artifact net.hydromatic:linq4j:pom:0.4 from/to datanucleus 
 (http://www.datanucleus.org/downloads/maven2): Access denied to: 
 http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,
  ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 - [Help 
 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR] 
 [ERROR] After correcting the problems, you can resume the build with the 
 command
 [ERROR]   mvn goals -rf :hive-exec
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8399) Build failure on trunk

2014-10-08 Thread Vaibhav Gumashta (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Gumashta updated HIVE-8399:
---
Fix Version/s: 0.14.0

 Build failure on trunk
 --

 Key: HIVE-8399
 URL: https://issues.apache.org/jira/browse/HIVE-8399
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Priority: Blocker
 Fix For: 0.14.0


 {code}
 Downloading: 
 http://repo.maven.apache.org/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO] 
 [INFO] Hive .. SUCCESS [  2.591 s]
 [INFO] Hive Shims Common . SUCCESS [  1.774 s]
 [INFO] Hive Shims 0.20 ... SUCCESS [  0.656 s]
 [INFO] Hive Shims Secure Common .. SUCCESS [  0.954 s]
 [INFO] Hive Shims 0.20S .. SUCCESS [  0.516 s]
 [INFO] Hive Shims 0.23 ... SUCCESS [  1.769 s]
 [INFO] Hive Shims  SUCCESS [  0.192 s]
 [INFO] Hive Common ... SUCCESS [  3.753 s]
 [INFO] Hive Serde  SUCCESS [  3.005 s]
 [INFO] Hive Metastore  SUCCESS [ 10.376 s]
 [INFO] Hive Ant Utilities  SUCCESS [  0.266 s]
 [INFO] Hive Query Language ... FAILURE [ 10.606 s]
 [INFO] Hive Service .. SKIPPED
 [INFO] Hive Accumulo Handler . SKIPPED
 [INFO] Hive JDBC . SKIPPED
 [INFO] Hive Beeline .. SKIPPED
 [INFO] Hive CLI .. SKIPPED
 [INFO] Hive Contrib .. SKIPPED
 [INFO] Hive HBase Handler  SKIPPED
 [INFO] Hive HCatalog . SKIPPED
 [INFO] Hive HCatalog Core  SKIPPED
 [INFO] Hive HCatalog Pig Adapter . SKIPPED
 [INFO] Hive HCatalog Server Extensions ... SKIPPED
 [INFO] Hive HCatalog Webhcat Java Client . SKIPPED
 [INFO] Hive HCatalog Webhcat . SKIPPED
 [INFO] Hive HCatalog Streaming ... SKIPPED
 [INFO] Hive HWI .. SKIPPED
 [INFO] Hive ODBC . SKIPPED
 [INFO] Hive Shims Aggregator . SKIPPED
 [INFO] Hive TestUtils  SKIPPED
 [INFO] Hive Packaging  SKIPPED
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 37.318 s
 [INFO] Finished at: 2014-10-08T10:16:32-08:00
 [INFO] Final Memory: 54M/355M
 [INFO] 
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) 
 on project hive-exec: Error resolving project artifact: Could not transfer 
 artifact net.hydromatic:linq4j:pom:0.4 from/to datanucleus 
 (http://www.datanucleus.org/downloads/maven2): Access denied to: 
 http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,
  ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 - [Help 
 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR] 
 [ERROR] After correcting the problems, you can resume the build with the 
 command
 [ERROR]   mvn goals -rf :hive-exec
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8380) NanoTime class serializes and deserializes Timestamp incorrectly

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163801#comment-14163801
 ] 

Hive QA commented on HIVE-8380:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673389/HIVE-8380.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1161/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1161/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1161/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Updated] (HIVE-8399) Build failure on trunk

2014-10-08 Thread Vaibhav Gumashta (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Gumashta updated HIVE-8399:
---
Description: 
{code}
Downloading: 
http://repo.maven.apache.org/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Hive .. SUCCESS [  2.591 s]
[INFO] Hive Shims Common . SUCCESS [  1.774 s]
[INFO] Hive Shims 0.20 ... SUCCESS [  0.656 s]
[INFO] Hive Shims Secure Common .. SUCCESS [  0.954 s]
[INFO] Hive Shims 0.20S .. SUCCESS [  0.516 s]
[INFO] Hive Shims 0.23 ... SUCCESS [  1.769 s]
[INFO] Hive Shims  SUCCESS [  0.192 s]
[INFO] Hive Common ... SUCCESS [  3.753 s]
[INFO] Hive Serde  SUCCESS [  3.005 s]
[INFO] Hive Metastore  SUCCESS [ 10.376 s]
[INFO] Hive Ant Utilities  SUCCESS [  0.266 s]
[INFO] Hive Query Language ... FAILURE [ 10.606 s]
[INFO] Hive Service .. SKIPPED
[INFO] Hive Accumulo Handler . SKIPPED
[INFO] Hive JDBC . SKIPPED
[INFO] Hive Beeline .. SKIPPED
[INFO] Hive CLI .. SKIPPED
[INFO] Hive Contrib .. SKIPPED
[INFO] Hive HBase Handler  SKIPPED
[INFO] Hive HCatalog . SKIPPED
[INFO] Hive HCatalog Core  SKIPPED
[INFO] Hive HCatalog Pig Adapter . SKIPPED
[INFO] Hive HCatalog Server Extensions ... SKIPPED
[INFO] Hive HCatalog Webhcat Java Client . SKIPPED
[INFO] Hive HCatalog Webhcat . SKIPPED
[INFO] Hive HCatalog Streaming ... SKIPPED
[INFO] Hive HWI .. SKIPPED
[INFO] Hive ODBC . SKIPPED
[INFO] Hive Shims Aggregator . SKIPPED
[INFO] Hive TestUtils  SKIPPED
[INFO] Hive Packaging  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 37.318 s
[INFO] Finished at: 2014-10-08T10:16:32-08:00
[INFO] Final Memory: 54M/355M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on 
project hive-exec: Error resolving project artifact: Could not transfer 
artifact net.hydromatic:linq4j:pom:0.4 from/to datanucleus 
(http://www.datanucleus.org/downloads/maven2): Access denied to: 
http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,
 ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 - [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn goals -rf :hive-exec
{code}

 Build failure on trunk
 --

 Key: HIVE-8399
 URL: https://issues.apache.org/jira/browse/HIVE-8399
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Priority: Blocker

 {code}
 Downloading: 
 http://repo.maven.apache.org/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO] 
 [INFO] Hive .. SUCCESS [  2.591 s]
 [INFO] Hive Shims Common . SUCCESS [  1.774 s]
 [INFO] Hive Shims 0.20 ... SUCCESS [  0.656 s]
 [INFO] Hive Shims Secure Common .. SUCCESS [  0.954 s]
 [INFO] Hive Shims 0.20S .. SUCCESS [  0.516 s]
 [INFO] Hive Shims 0.23 ... SUCCESS [  1.769 s]
 

[jira] [Updated] (HIVE-8399) Build failure on trunk 14 branch

2014-10-08 Thread Vaibhav Gumashta (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Gumashta updated HIVE-8399:
---
Summary: Build failure on trunk  14 branch  (was: Build failure on trunk)

 Build failure on trunk  14 branch
 --

 Key: HIVE-8399
 URL: https://issues.apache.org/jira/browse/HIVE-8399
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Priority: Blocker
 Fix For: 0.14.0


 {code}
 Downloading: 
 http://repo.maven.apache.org/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO] 
 [INFO] Hive .. SUCCESS [  2.591 s]
 [INFO] Hive Shims Common . SUCCESS [  1.774 s]
 [INFO] Hive Shims 0.20 ... SUCCESS [  0.656 s]
 [INFO] Hive Shims Secure Common .. SUCCESS [  0.954 s]
 [INFO] Hive Shims 0.20S .. SUCCESS [  0.516 s]
 [INFO] Hive Shims 0.23 ... SUCCESS [  1.769 s]
 [INFO] Hive Shims  SUCCESS [  0.192 s]
 [INFO] Hive Common ... SUCCESS [  3.753 s]
 [INFO] Hive Serde  SUCCESS [  3.005 s]
 [INFO] Hive Metastore  SUCCESS [ 10.376 s]
 [INFO] Hive Ant Utilities  SUCCESS [  0.266 s]
 [INFO] Hive Query Language ... FAILURE [ 10.606 s]
 [INFO] Hive Service .. SKIPPED
 [INFO] Hive Accumulo Handler . SKIPPED
 [INFO] Hive JDBC . SKIPPED
 [INFO] Hive Beeline .. SKIPPED
 [INFO] Hive CLI .. SKIPPED
 [INFO] Hive Contrib .. SKIPPED
 [INFO] Hive HBase Handler  SKIPPED
 [INFO] Hive HCatalog . SKIPPED
 [INFO] Hive HCatalog Core  SKIPPED
 [INFO] Hive HCatalog Pig Adapter . SKIPPED
 [INFO] Hive HCatalog Server Extensions ... SKIPPED
 [INFO] Hive HCatalog Webhcat Java Client . SKIPPED
 [INFO] Hive HCatalog Webhcat . SKIPPED
 [INFO] Hive HCatalog Streaming ... SKIPPED
 [INFO] Hive HWI .. SKIPPED
 [INFO] Hive ODBC . SKIPPED
 [INFO] Hive Shims Aggregator . SKIPPED
 [INFO] Hive TestUtils  SKIPPED
 [INFO] Hive Packaging  SKIPPED
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 37.318 s
 [INFO] Finished at: 2014-10-08T10:16:32-08:00
 [INFO] Final Memory: 54M/355M
 [INFO] 
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) 
 on project hive-exec: Error resolving project artifact: Could not transfer 
 artifact net.hydromatic:linq4j:pom:0.4 from/to datanucleus 
 (http://www.datanucleus.org/downloads/maven2): Access denied to: 
 http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,
  ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 - [Help 
 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR] 
 [ERROR] After correcting the problems, you can resume the build with the 
 command
 [ERROR]   mvn goals -rf :hive-exec
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8288) HiveServer2 dynamic discovery should create znodes organized by version number add support for removing server uri's of a particular version from the server script.

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163813#comment-14163813
 ] 

Hive QA commented on HIVE-8288:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673408/HIVE-8288.5.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1163/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1163/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1163/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8399) Build failure on trunk 14 branch

2014-10-08 Thread Vaibhav Gumashta (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163817#comment-14163817
 ] 

Vaibhav Gumashta commented on HIVE-8399:


This is weird: http://www.datanucleus.org/ throwing 403 access denied.

 Build failure on trunk  14 branch
 --

 Key: HIVE-8399
 URL: https://issues.apache.org/jira/browse/HIVE-8399
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Priority: Blocker
 Fix For: 0.14.0


 {code}
 Downloading: 
 http://repo.maven.apache.org/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO] 
 [INFO] Hive .. SUCCESS [  2.591 s]
 [INFO] Hive Shims Common . SUCCESS [  1.774 s]
 [INFO] Hive Shims 0.20 ... SUCCESS [  0.656 s]
 [INFO] Hive Shims Secure Common .. SUCCESS [  0.954 s]
 [INFO] Hive Shims 0.20S .. SUCCESS [  0.516 s]
 [INFO] Hive Shims 0.23 ... SUCCESS [  1.769 s]
 [INFO] Hive Shims  SUCCESS [  0.192 s]
 [INFO] Hive Common ... SUCCESS [  3.753 s]
 [INFO] Hive Serde  SUCCESS [  3.005 s]
 [INFO] Hive Metastore  SUCCESS [ 10.376 s]
 [INFO] Hive Ant Utilities  SUCCESS [  0.266 s]
 [INFO] Hive Query Language ... FAILURE [ 10.606 s]
 [INFO] Hive Service .. SKIPPED
 [INFO] Hive Accumulo Handler . SKIPPED
 [INFO] Hive JDBC . SKIPPED
 [INFO] Hive Beeline .. SKIPPED
 [INFO] Hive CLI .. SKIPPED
 [INFO] Hive Contrib .. SKIPPED
 [INFO] Hive HBase Handler  SKIPPED
 [INFO] Hive HCatalog . SKIPPED
 [INFO] Hive HCatalog Core  SKIPPED
 [INFO] Hive HCatalog Pig Adapter . SKIPPED
 [INFO] Hive HCatalog Server Extensions ... SKIPPED
 [INFO] Hive HCatalog Webhcat Java Client . SKIPPED
 [INFO] Hive HCatalog Webhcat . SKIPPED
 [INFO] Hive HCatalog Streaming ... SKIPPED
 [INFO] Hive HWI .. SKIPPED
 [INFO] Hive ODBC . SKIPPED
 [INFO] Hive Shims Aggregator . SKIPPED
 [INFO] Hive TestUtils  SKIPPED
 [INFO] Hive Packaging  SKIPPED
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 37.318 s
 [INFO] Finished at: 2014-10-08T10:16:32-08:00
 [INFO] Final Memory: 54M/355M
 [INFO] 
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) 
 on project hive-exec: Error resolving project artifact: Could not transfer 
 artifact net.hydromatic:linq4j:pom:0.4 from/to datanucleus 
 (http://www.datanucleus.org/downloads/maven2): Access denied to: 
 http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,
  ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 - [Help 
 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR] 
 [ERROR] After correcting the problems, you can resume the build with the 
 command
 [ERROR]   mvn goals -rf :hive-exec
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8258) Compactor cleaners can be starved on a busy table or partition.

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163819#comment-14163819
 ] 

Hive QA commented on HIVE-8258:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673441/HIVE-8258.4.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1164/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1164/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1164/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8021) CBO: support CTAS and insert ... select

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163821#comment-14163821
 ] 

Hive QA commented on HIVE-8021:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673452/HIVE-8021.03.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1165/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1165/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1165/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

Build appears to be broken by http://www.datanucleus.org/

2014-10-08 Thread Brock Noland
http://www.datanucleus.org/ is not accessiable

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project hive-exec: Error resolving project artifact:
Could not transfer artifact net.hydromatic:linq4j:pom:0.4 from/to
datanucleus (http://www.datanucleus.org/downloads/maven2): Access
denied to: 
http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,
ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 -
[Help 1]


[jira] [Commented] (HIVE-8386) HCAT api call is case sensitive on fields in struct column

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163824#comment-14163824
 ] 

Hive QA commented on HIVE-8386:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673459/HIVE-8386.1.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1166/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1166/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1166/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8389) Disable CBO when indexes are used

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163829#comment-14163829
 ] 

Hive QA commented on HIVE-8389:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673462/HIVE-8389.1.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1167/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1167/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1167/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-6972) jdbc HTTP configuration options should be part of sessionConf part of connection string

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163833#comment-14163833
 ] 

Hive QA commented on HIVE-6972:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673481/HIVE-6972.3.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1168/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1168/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1168/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8225) CBO trunk merge: union11 test fails due to incorrect plan

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163837#comment-14163837
 ] 

Hive QA commented on HIVE-8225:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673527/HIVE-8225.7.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1169/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1169/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1169/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8393) Handle SIGINT on Tez

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163841#comment-14163841
 ] 

Hive QA commented on HIVE-8393:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673497/HIVE-8393.1.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1170/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1170/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1170/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8395) CBO: enable by default

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163848#comment-14163848
 ] 

Hive QA commented on HIVE-8395:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673500/HIVE-8395.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1171/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1171/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1171/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8390) CBO produces annoying exception message when there are no stats

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163854#comment-14163854
 ] 

Hive QA commented on HIVE-8390:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673469/HIVE-8390.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1172/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1172/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1172/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Created] (HIVE-8400) hwi does not have war file

2014-10-08 Thread Pankit Thapar (JIRA)
Pankit Thapar created HIVE-8400:
---

 Summary: hwi does not have war file
 Key: HIVE-8400
 URL: https://issues.apache.org/jira/browse/HIVE-8400
 Project: Hive
  Issue Type: Bug
  Components: Web UI
Affects Versions: 0.13.1
Reporter: Pankit Thapar
 Fix For: 0.14.0


hive 0.11 used to have hwi-0.11.war file but it seems that hive 13 is not 
configured to build a war file, instead it builds a jar file for hwi.

A fix for this would be to change jar to war in hwi/pom.xml.
Diff is below : 
diff --git a/hwi/pom.xml b/hwi/pom.xml
index 35c124b..88d83fb 100644
--- a/hwi/pom.xml
+++ b/hwi/pom.xml
@@ -24,7 +24,7 @@
   /parent
 
   artifactIdhive-hwi/artifactId
-  packagingjar/packaging
+  packagingwar/packaging
   nameHive HWI/name

Please let me know if jar was intended or is it actually a bug so that I can 
submit a patch for the fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-6056) The AvroSerDe gives out BadSchemaException if a partition is added to the table

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163857#comment-14163857
 ] 

Hive QA commented on HIVE-6056:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673514/HIVE-6056.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1173/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1173/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1173/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-7858) Parquet compression should be configurable via table property

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163864#comment-14163864
 ] 

Hive QA commented on HIVE-7858:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673513/HIVE-7858.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1174/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1174/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1174/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Created] (HIVE-8401) Orc file merge operator didn't close files it opened, which resulted in redundant data in table directory

2014-10-08 Thread Xiaobing Zhou (JIRA)
Xiaobing Zhou created HIVE-8401:
---

 Summary: Orc file merge operator didn't close files it opened, 
which resulted in redundant data in table directory
 Key: HIVE-8401
 URL: https://issues.apache.org/jira/browse/HIVE-8401
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou
Priority: Critical






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8401) Orc file merge operator didn't close files it opened, which resulted in redundant data in table directory

2014-10-08 Thread Xiaobing Zhou (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaobing Zhou updated HIVE-8401:

Environment: Windows Server

 Orc file merge operator didn't close files it opened, which resulted in 
 redundant data in table directory
 -

 Key: HIVE-8401
 URL: https://issues.apache.org/jira/browse/HIVE-8401
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
 Environment: Windows Server
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou
Priority: Critical





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8382) ConstantPropagateProcFactory#isDeterministicUdf adds a lot of ERROR level logs

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163870#comment-14163870
 ] 

Hive QA commented on HIVE-8382:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673541/HIVE-8382.1.patch.txt

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1175/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1175/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1175/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Created] (HIVE-8402) Orc pushing SARGs into delta files causing ArrayOutOfBoundsExceptions

2014-10-08 Thread Alan Gates (JIRA)
Alan Gates created HIVE-8402:


 Summary: Orc pushing SARGs into delta files causing 
ArrayOutOfBoundsExceptions
 Key: HIVE-8402
 URL: https://issues.apache.org/jira/browse/HIVE-8402
 Project: Hive
  Issue Type: Bug
  Components: File Formats, Transactions
Affects Versions: 0.14.0
Reporter: Alan Gates
Assignee: Alan Gates
Priority: Blocker
 Fix For: 0.14.0


ORC is in some instances pushing SARGs into delta files.  This is wrong 
behavior in general as it may result in failing to pull the most recent version 
of a row.  When the SARG is applied to a row that is deleted it causes an 
ArrayOutOfBoundsException because there is no data in the row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8397) Approximated cardinality with HyperLogLog UDAF

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163874#comment-14163874
 ] 

Hive QA commented on HIVE-8397:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673563/HIVE-8397.1.patch.txt

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1176/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1176/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1176/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8395) CBO: enable by default

2014-10-08 Thread Sergey Shelukhin (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163875#comment-14163875
 ] 

Sergey Shelukhin commented on HIVE-8395:


Looks like some dependency broke Hive QA :( datanucleus.org appears to be down

 CBO: enable by default
 --

 Key: HIVE-8395
 URL: https://issues.apache.org/jira/browse/HIVE-8395
 Project: Hive
  Issue Type: Sub-task
  Components: CBO
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
 Fix For: 0.14.0

 Attachments: HIVE-8395.patch






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8402) Orc pushing SARGs into delta files causing ArrayOutOfBoundsExceptions

2014-10-08 Thread Alan Gates (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163876#comment-14163876
 ] 

Alan Gates commented on HIVE-8402:
--

In my tests at the moment I only see this after compaction.  I don't know if 
this is because ORC correctly doesn't push the SARGs when there are only delta 
files or if something else is causing this.

 Orc pushing SARGs into delta files causing ArrayOutOfBoundsExceptions
 -

 Key: HIVE-8402
 URL: https://issues.apache.org/jira/browse/HIVE-8402
 Project: Hive
  Issue Type: Bug
  Components: File Formats, Transactions
Affects Versions: 0.14.0
Reporter: Alan Gates
Assignee: Alan Gates
Priority: Blocker
 Fix For: 0.14.0


 ORC is in some instances pushing SARGs into delta files.  This is wrong 
 behavior in general as it may result in failing to pull the most recent 
 version of a row.  When the SARG is applied to a row that is deleted it 
 causes an ArrayOutOfBoundsException because there is no data in the row.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-6914) parquet-hive cannot write nested map (map value is map)

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163884#comment-14163884
 ] 

Hive QA commented on HIVE-6914:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673580/HIVE-6914.1.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1177/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1177/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1177/

Messages:
{noformat}
 This message was trimmed, see log for full details 
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_CASE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_FALSE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_DATE StringLiteral using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_TRUE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_MAP using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_UNIONTYPE using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_STRUCT using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_NOT KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN KW_CASE KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:68:4: 
Decision can match input such as LPAREN LPAREN KW_IF using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:115:5: 
Decision can match input such as KW_CLUSTER KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:127:5: 
Decision can match input such as KW_PARTITION KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:138:5: 
Decision can match input such as KW_DISTRIBUTE KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:149:5: 
Decision can match input such as KW_SORT KW_BY LPAREN using multiple 
alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:166:7: 
Decision can match input such as STAR using multiple alternatives: 1, 2

As a result, alternative(s) 2 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_STRUCT using multiple alternatives: 4, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_ARRAY using multiple alternatives: 2, 6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:179:5: 
Decision can match input such as KW_UNIONTYPE using multiple alternatives: 5, 
6

As a result, alternative(s) 6 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_TRUE using multiple alternatives: 3, 8

As a result, alternative(s) 8 were disabled for that input
warning(200): IdentifiersParser.g:261:5: 
Decision can match input such as KW_NULL using multiple alternatives: 1, 8

As a result, alternative(s) 8 were disabled for that input

[jira] [Commented] (HIVE-8398) ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc

2014-10-08 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163887#comment-14163887
 ] 

Hive QA commented on HIVE-8398:
---



{color:red}Overall{color}: -1 no tests executed

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673593/HIVE-8398.patch

Test results: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1178/testReport
Console output: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1178/console
Test logs: 
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1178/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hive-ptest/working/scratch/source-prep.sh' failed with exit 
status 1 and output '+ [[ -n /usr/java/jdk1.7.0_45-cloudera ]]
+ export JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ export 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-maven-3.0.5/bin:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ 
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-maven-3.0.5/bin:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.6.0_34/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ cd /data/hive-ptest/working/
+ tee /data/hive-ptest/logs/PreCommit-HIVE-TRUNK-Build-1178/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ svn = \s\v\n ]]
+ [[ -n '' ]]
+ [[ -d apache-svn-trunk-source ]]
+ [[ ! -d apache-svn-trunk-source/.svn ]]
+ [[ ! -d apache-svn-trunk-source ]]
+ cd apache-svn-trunk-source
+ svn revert -R .
Reverted 
'ql/src/java/org/apache/hadoop/hive/ql/io/parquet/serde/ParquetHiveSerDe.java'
Reverted 
'ql/src/java/org/apache/hadoop/hive/ql/io/parquet/write/DataWritableWriter.java'
++ awk '{print $2}'
++ egrep -v '^X|^Performing status on external'
++ svn status --no-ignore
+ rm -rf target datanucleus.log ant/target shims/0.20/target shims/0.20S/target 
shims/0.23/target shims/aggregator/target shims/common/target 
shims/common-secure/target metastore/target data/files/parquet_fake_table.txt 
common/target common/src/gen serde/target ql/target 
ql/src/test/results/clientpositive/parquet_complex_type_nested.q.out 
ql/src/test/queries/clientpositive/parquet_complex_type_nested.q 
ql/src/java/org/apache/hadoop/hive/ql/io/parquet/serde/ParquetHiveSerDe.java.orig
 
ql/src/java/org/apache/hadoop/hive/ql/io/parquet/write/DataWritableWriter.java.orig
+ svn update

Fetching external item into 'hcatalog/src/test/e2e/harness'
External at revision 1630190.

At revision 1630190.
+ patchCommandPath=/data/hive-ptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hive-ptest/working/scratch/build.patch
+ [[ -f /data/hive-ptest/working/scratch/build.patch ]]
+ chmod +x /data/hive-ptest/working/scratch/smart-apply-patch.sh
+ /data/hive-ptest/working/scratch/smart-apply-patch.sh 
/data/hive-ptest/working/scratch/build.patch
The patch does not appear to apply with p0, p1, or p2
+ exit 1
'
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12673593

 ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc
 -

 Key: HIVE-8398
 URL: https://issues.apache.org/jira/browse/HIVE-8398
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.13.0, 0.14.0
Reporter: Zhichun Wu
Assignee: Zhichun Wu
 Attachments: HIVE-8398.patch


 The following explain statement would fail  in hive 0.13 and trunk
 with ExprNodeColumnDesc cannot be cast to ExprNodeConstantDesc exception:
 {code}
 create table test.t2( key string, value int);
 explain select
sum(u.value) value
 from test.t2 u
 group by u.key
 having sum(u.value)  30;
 {code}
 The full stack trace:
 {code}
 java.lang.ClassCastException: 
 org.apache.hadoop.hive.ql.plan.ExprNodeColumnDesc cannot be cast to 
 org.apache.hadoop.hive.ql.plan.ExprNodeConstantDesc
 at 
 org.apache.hadoop.hive.ql.parse.TypeCheckProcFactory$DefaultExprProcessor.process(TypeCheckProcFactory.java:1067)
 at 
 org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:90)
 at 
 

[jira] [Updated] (HIVE-8401) OrcFileMergeOperator only close last orc file it opened, which resulted in redundant data in table directory

2014-10-08 Thread Xiaobing Zhou (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaobing Zhou updated HIVE-8401:

Summary: OrcFileMergeOperator only close last orc file it opened, which 
resulted in redundant data in table directory  (was: Orc file merge operator 
only close last orc file it opened, which resulted in redundant data in table 
directory)

 OrcFileMergeOperator only close last orc file it opened, which resulted in 
 redundant data in table directory
 

 Key: HIVE-8401
 URL: https://issues.apache.org/jira/browse/HIVE-8401
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
 Environment: Windows Server
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou
Priority: Critical

 run the test
 {noformat}
 mvn -Phadoop-2  test -Dtest=TestCliDriver -Dqfile=alter_merge_2_orc.q
 {noformat}
 to reproduce it. Simply, this query does three data loads which generates 
 three orc files, ALTER TABLE CONCATENATE tries to merge orc pieces into a 
 single one which is final file to queried.
 Output 
 \hive\itests\qtest\target\qfile-results\clientpositive\alter_merge_2_orc.q.out
  shows # records as 600 that is wrong as opposed to 610 expected.
 Because OrcFileMergeOperator only closes last orc file, the 1st and 2nd orc 
 files still remain in table directory due to failure of deleting unclosed 
 file for old data clean when MoveTask tries to copy merged orc file from 
 scratch dir to table dir. Eventually the query goes to old data(1st and 2nd 
 orc files).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8401) Orc file merge operator only close last orc file it opened, which resulted in redundant data in table directory

2014-10-08 Thread Xiaobing Zhou (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaobing Zhou updated HIVE-8401:

Description: 
run the test
{noformat}
mvn -Phadoop-2  test -Dtest=TestCliDriver -Dqfile=alter_merge_2_orc.q
{noformat}
to reproduce it. Simply, this query does three data loads which generates three 
orc files, ALTER TABLE CONCATENATE tries to merge orc pieces into a single one 
which is final file to queried.

Output 
\hive\itests\qtest\target\qfile-results\clientpositive\alter_merge_2_orc.q.out 
shows # records as 600 that is wrong as opposed to 610 expected.

Because OrcFileMergeOperator only closes last orc file, the 1st and 2nd orc 
files still remain in table directory due to failure of deleting unclosed file 
for old data clean when MoveTask tries to copy merged orc file from scratch dir 
to table dir. Eventually the query goes to old data(1st and 2nd orc files).


Summary: Orc file merge operator only close last orc file it opened, 
which resulted in redundant data in table directory  (was: Orc file merge 
operator didn't close files it opened, which resulted in redundant data in 
table directory)

 Orc file merge operator only close last orc file it opened, which resulted in 
 redundant data in table directory
 ---

 Key: HIVE-8401
 URL: https://issues.apache.org/jira/browse/HIVE-8401
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
 Environment: Windows Server
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou
Priority: Critical

 run the test
 {noformat}
 mvn -Phadoop-2  test -Dtest=TestCliDriver -Dqfile=alter_merge_2_orc.q
 {noformat}
 to reproduce it. Simply, this query does three data loads which generates 
 three orc files, ALTER TABLE CONCATENATE tries to merge orc pieces into a 
 single one which is final file to queried.
 Output 
 \hive\itests\qtest\target\qfile-results\clientpositive\alter_merge_2_orc.q.out
  shows # records as 600 that is wrong as opposed to 610 expected.
 Because OrcFileMergeOperator only closes last orc file, the 1st and 2nd orc 
 files still remain in table directory due to failure of deleting unclosed 
 file for old data clean when MoveTask tries to copy merged orc file from 
 scratch dir to table dir. Eventually the query goes to old data(1st and 2nd 
 orc files).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8401) OrcFileMergeOperator only close last orc file it opened, which resulted in stale data in table directory

2014-10-08 Thread Xiaobing Zhou (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaobing Zhou updated HIVE-8401:

Summary: OrcFileMergeOperator only close last orc file it opened, which 
resulted in stale data in table directory  (was: OrcFileMergeOperator only 
close last orc file it opened, which resulted in redundant data in table 
directory)

 OrcFileMergeOperator only close last orc file it opened, which resulted in 
 stale data in table directory
 

 Key: HIVE-8401
 URL: https://issues.apache.org/jira/browse/HIVE-8401
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
 Environment: Windows Server
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou
Priority: Critical

 run the test
 {noformat}
 mvn -Phadoop-2  test -Dtest=TestCliDriver -Dqfile=alter_merge_2_orc.q
 {noformat}
 to reproduce it. Simply, this query does three data loads which generates 
 three orc files, ALTER TABLE CONCATENATE tries to merge orc pieces into a 
 single one which is final file to queried.
 Output 
 \hive\itests\qtest\target\qfile-results\clientpositive\alter_merge_2_orc.q.out
  shows # records as 600 that is wrong as opposed to 610 expected.
 Because OrcFileMergeOperator only closes last orc file, the 1st and 2nd orc 
 files still remain in table directory due to failure of deleting unclosed 
 file for old data clean when MoveTask tries to copy merged orc file from 
 scratch dir to table dir. Eventually the query goes to old data(1st and 2nd 
 orc files).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: Build appears to be broken by http://www.datanucleus.org/

2014-10-08 Thread Alan Gates
It appears that the jars we need are in maven central.  I tried removing 
datanucleus completely from my maven cache then commenting out the 
datanucleus repository in pom.xml and the jars were properly fetched 
from maven central.  Should I just put up a patch for this so we can get 
building again?


Alan.


Brock Noland mailto:br...@cloudera.com
October 8, 2014 at 10:28
http://www.datanucleus.org/ is not accessiable

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project hive-exec: Error resolving project artifact:
Could not transfer artifact net.hydromatic:linq4j:pom:0.4 from/to
datanucleus (http://www.datanucleus.org/downloads/maven2): Access
denied to: 
http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,

ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 -
[Help 1]


--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.


[jira] [Commented] (HIVE-8363) AccumuloStorageHandler compile failure hadoop-1

2014-10-08 Thread Szehon Ho (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163913#comment-14163913
 ] 

Szehon Ho commented on HIVE-8363:
-

Committed to trunk, thanks Josh!

[~vikram.dixit] can I have approval to commit to 0.14?

 AccumuloStorageHandler compile failure hadoop-1
 ---

 Key: HIVE-8363
 URL: https://issues.apache.org/jira/browse/HIVE-8363
 Project: Hive
  Issue Type: Bug
  Components: StorageHandler
Reporter: Szehon Ho
Assignee: Josh Elser
Priority: Blocker
 Fix For: 0.14.0

 Attachments: HIVE-8363.1.patch


 There's an error about AccumuloStorageHandler compiling on hadoop-1.  It 
 seems the signature of split() is not the same.  Looks like we can should use 
 another utils to fix this.
 {code}
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
 on project hive-accumulo-handler: Compilation failure
 [ERROR] 
 /data/hive-ptest/working/apache-svn-trunk-source/accumulo-handler/src/java/org/apache/hadoop/hive/accumulo/columns/ColumnMapper.java:[57,52]
  no suitable method found for split(java.lang.String,char)
 [ERROR] method 
 org.apache.hadoop.util.StringUtils.split(java.lang.String,char,char) is not 
 applicable
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8401) OrcFileMergeOperator only close last orc file it opened, which resulted in stale data in table directory

2014-10-08 Thread Xiaobing Zhou (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaobing Zhou updated HIVE-8401:

Attachment: alter_merge_2_orc.q.out

 OrcFileMergeOperator only close last orc file it opened, which resulted in 
 stale data in table directory
 

 Key: HIVE-8401
 URL: https://issues.apache.org/jira/browse/HIVE-8401
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
 Environment: Windows Server
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou
Priority: Critical
 Attachments: alter_merge_2_orc.q.out


 run the test
 {noformat}
 mvn -Phadoop-2  test -Dtest=TestCliDriver -Dqfile=alter_merge_2_orc.q
 {noformat}
 to reproduce it. Simply, this query does three data loads which generates 
 three orc files, ALTER TABLE CONCATENATE tries to merge orc pieces into a 
 single one which is final file to queried.
 Output 
 \hive\itests\qtest\target\qfile-results\clientpositive\alter_merge_2_orc.q.out
  shows # records as 600 that is wrong as opposed to 610 expected.
 Because OrcFileMergeOperator only closes last orc file, the 1st and 2nd orc 
 files still remain in table directory due to failure of deleting unclosed 
 file for old data clean when MoveTask tries to copy merged orc file from 
 scratch dir to table dir. Eventually the query goes to old data(1st and 2nd 
 orc files).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: Build appears to be broken by http://www.datanucleus.org/

2014-10-08 Thread Brock Noland
That works for me. IIRC when I did the maven build I learned we used the DN
repo for something not DN related. Can you try the build
with -Dmaven.repo.local=/tmp/maven and ensure it builds without any cache?

If so, yes let's get rid of that repo.

Also I found it works now with the -o flag.

On Wed, Oct 8, 2014 at 11:18 AM, Alan Gates ga...@hortonworks.com wrote:

 It appears that the jars we need are in maven central.  I tried removing
 datanucleus completely from my maven cache then commenting out the
 datanucleus repository in pom.xml and the jars were properly fetched from
 maven central.  Should I just put up a patch for this so we can get
 building again?

 Alan.

   Brock Noland br...@cloudera.com
  October 8, 2014 at 10:28
 http://www.datanucleus.org/ is not accessiable

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
 (default) on project hive-exec: Error resolving project artifact:
 Could not transfer artifact net.hydromatic:linq4j:pom:0.4 from/to
 datanucleus (http://www.datanucleus.org/downloads/maven2): Access
 denied to:
 http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 ,
 ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 -
 [Help 1]


 --
 Sent with Postbox http://www.getpostbox.com

 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity
 to which it is addressed and may contain information that is confidential,
 privileged and exempt from disclosure under applicable law. If the reader
 of this message is not the intended recipient, you are hereby notified that
 any printing, copying, dissemination, distribution, disclosure or
 forwarding of this communication is strictly prohibited. If you have
 received this communication in error, please contact the sender immediately
 and delete it from your system. Thank You.


Re: Build appears to be broken by http://www.datanucleus.org/

2014-10-08 Thread Alan Gates
Yeah, I found what it was.  javax.jms.  I'm trying to see if there's 
another repo I can pick it up from.


Alan.


Brock Noland mailto:br...@cloudera.com
October 8, 2014 at 11:25
That works for me. IIRC when I did the maven build I learned we used 
the DN

repo for something not DN related. Can you try the build
with -Dmaven.repo.local=/tmp/maven and ensure it builds without any cache?

If so, yes let's get rid of that repo.

Also I found it works now with the -o flag.


Alan Gates mailto:ga...@hortonworks.com
October 8, 2014 at 11:18
It appears that the jars we need are in maven central.  I tried 
removing datanucleus completely from my maven cache then commenting 
out the datanucleus repository in pom.xml and the jars were properly 
fetched from maven central.  Should I just put up a patch for this so 
we can get building again?


Alan.


Brock Noland mailto:br...@cloudera.com
October 8, 2014 at 10:28
http://www.datanucleus.org/ is not accessiable

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project hive-exec: Error resolving project artifact:
Could not transfer artifact net.hydromatic:linq4j:pom:0.4 from/to
datanucleus (http://www.datanucleus.org/downloads/maven2): Access
denied to: 
http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,

ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 -
[Help 1]


--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.


[jira] [Commented] (HIVE-8344) Hive on Tez sets mapreduce.framework.name to yarn-tez

2014-10-08 Thread Vikram Dixit K (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163931#comment-14163931
 ] 

Vikram Dixit K commented on HIVE-8344:
--

+1 LGTM. +1 for 0.14 as well.

 Hive on Tez sets mapreduce.framework.name to yarn-tez
 -

 Key: HIVE-8344
 URL: https://issues.apache.org/jira/browse/HIVE-8344
 Project: Hive
  Issue Type: Bug
Reporter: Gunther Hagleitner
Assignee: Gunther Hagleitner
 Attachments: HIVE-8344.1.patch, HIVE-8344.2.patch, HIVE-8344.3.patch


 This was done to run MR jobs when in Tez mode (emulate MR on Tez). However, 
 we don't switch back when the user specifies MR as exec engine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (HIVE-7384) Research into reduce-side join [Spark Branch]

2014-10-08 Thread Xuefu Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xuefu Zhang resolved HIVE-7384.
---
   Resolution: Fixed
Fix Version/s: spark-branch

Hive on Spark now supports reduce side join. Thus, I close this task  as 
resolved. Thanks to Szehon for the research.

 Research into reduce-side join [Spark Branch]
 -

 Key: HIVE-7384
 URL: https://issues.apache.org/jira/browse/HIVE-7384
 Project: Hive
  Issue Type: Sub-task
  Components: Spark
Reporter: Xuefu Zhang
Assignee: Szehon Ho
 Fix For: spark-branch

 Attachments: Hive on Spark Reduce Side Join.docx, sales_items.txt, 
 sales_products.txt, sales_stores.txt


 Hive's join operator is very sophisticated, especially for reduce-side join. 
 While we expect that other types of join, such as map-side join and SMB 
 map-side join, will work out of the box with our design, there may be some 
 complication in reduce-side join, which extensively utilizes key tag and 
 shuffle behavior. Our design principle prefers to making Hive implementation 
 work out of box also, which might requires new functionality from Spark. The 
 tasks is to research into this area, identifying requirements for Spark 
 community and the work to be done on Hive to make reduce-side join work.
 A design doc might be needed for this. For more information, please refer to 
 the overall design doc on wiki.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: Review Request 26435: Self join may fail if one side has VCs and other doesn't

2014-10-08 Thread Sergey Shelukhin

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/26435/#review55851
---



data/conf/hive-log4j.properties
https://reviews.apache.org/r/26435/#comment96225

are ObjectStore and Operator lines intended? they'd affect logging that 
might be useful for other tests



ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java
https://reviews.apache.org/r/26435/#comment96232

is it possible to document those with a small comment; as well as MapOpMeta 
and MapOpCtx classes?



ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java
https://reviews.apache.org/r/26435/#comment96226

nit: hash codes could be combined similar to how Java does it ( * prime + 
next)



ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java
https://reviews.apache.org/r/26435/#comment96227

why are the calles to SerDeUtils gone? Just asking



ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java
https://reviews.apache.org/r/26435/#comment96228

this creates a context and checks for its presence, but then puts the 
result of some call taking the context to map. Would it make sense to put 
context into map first and then do processing on it (that I assume the call 
does)? That would be less confusing.



ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java
https://reviews.apache.org/r/26435/#comment96229

is children.size() check no longer necessary?



ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java
https://reviews.apache.org/r/26435/#comment96230

path is never used



ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java
https://reviews.apache.org/r/26435/#comment96233

one child operator can be present for several paths or in several MapOpCtx?


- Sergey Shelukhin


On Oct. 8, 2014, 4:06 a.m., Navis Ryu wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/26435/
 ---
 
 (Updated Oct. 8, 2014, 4:06 a.m.)
 
 
 Review request for hive.
 
 
 Bugs: HIVE-8186
 https://issues.apache.org/jira/browse/HIVE-8186
 
 
 Repository: hive-git
 
 
 Description
 ---
 
 {noformat}select t1.BLOCK__OFFSET__INSIDE__FILE,t2.BLOCK__OFFSET__INSIDE__FILE
 from src t1 join src t2 on t1.key = t2.key;{noformat}
 Passes
 {noformat}select t2.BLOCK__OFFSET__INSIDE__FILE
 from src t1 join src t2 on t1.key = t2.key;{noformat}
 Fails.
 
 The issue is that LazyBinarySerDe OI receives data intended for 
 UnionStructObjectInspector.
 Judging by the above it has something to do with scanning table once for two 
 aliases.
 
 I'll look tomorrow
 
 
 Diffs
 -
 
   data/conf/hive-log4j.properties 7f5dfc4 
   ql/src/java/org/apache/hadoop/hive/ql/exec/MapOperator.java f624bf4 
   ql/src/java/org/apache/hadoop/hive/ql/exec/Operator.java 3dc7c76 
   ql/src/java/org/apache/hadoop/hive/ql/exec/ReduceSinkOperator.java d8698da 
   ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java 155002a 
   ql/src/java/org/apache/hadoop/hive/ql/exec/vector/VectorMapOperator.java 
 311f6d6 
   ql/src/java/org/apache/hadoop/hive/ql/plan/TableDesc.java 78d4d1f 
   ql/src/test/org/apache/hadoop/hive/ql/exec/TestOperators.java 90e4cad 
   ql/src/test/queries/clientpositive/join_vc.q 63b3da7 
   ql/src/test/results/clientpositive/join_vc.q.out 12004ca 
 
 Diff: https://reviews.apache.org/r/26435/diff/
 
 
 Testing
 ---
 
 
 Thanks,
 
 Navis Ryu
 




[jira] [Created] (HIVE-8403) Build broken by datanucleus.org being offline

2014-10-08 Thread Alan Gates (JIRA)
Alan Gates created HIVE-8403:


 Summary: Build broken by datanucleus.org being offline
 Key: HIVE-8403
 URL: https://issues.apache.org/jira/browse/HIVE-8403
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 0.14.0
Reporter: Alan Gates
Priority: Blocker
 Fix For: 0.14.0


datanucleus.org is not available, making it impossible to download jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8403) Build broken by datanucleus.org being offline

2014-10-08 Thread Alan Gates (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-8403:
-
Attachment: HIVE-8403.patch

Removes datanucleus.org as a repository and adds JBoss in order to pick up JMS 
jars.

 Build broken by datanucleus.org being offline
 -

 Key: HIVE-8403
 URL: https://issues.apache.org/jira/browse/HIVE-8403
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 0.14.0
Reporter: Alan Gates
Priority: Blocker
 Fix For: 0.14.0

 Attachments: HIVE-8403.patch


 datanucleus.org is not available, making it impossible to download jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8403) Build broken by datanucleus.org being offline

2014-10-08 Thread Alan Gates (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-8403:
-
Assignee: Alan Gates
  Status: Patch Available  (was: Open)

 Build broken by datanucleus.org being offline
 -

 Key: HIVE-8403
 URL: https://issues.apache.org/jira/browse/HIVE-8403
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 0.14.0
Reporter: Alan Gates
Assignee: Alan Gates
Priority: Blocker
 Fix For: 0.14.0

 Attachments: HIVE-8403.patch


 datanucleus.org is not available, making it impossible to download jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: Build appears to be broken by http://www.datanucleus.org/

2014-10-08 Thread Alan Gates
I've created HIVE-8403 and attached a patch that works for  me when I do 
the maven.repo.local thing.  Someone else should try this on their 
machine.  If it works, please check it in.  I assume we don't have to 
wait for the 24 hour limit on patches like this.


Alan.


Brock Noland mailto:br...@cloudera.com
October 8, 2014 at 11:25
That works for me. IIRC when I did the maven build I learned we used 
the DN

repo for something not DN related. Can you try the build
with -Dmaven.repo.local=/tmp/maven and ensure it builds without any cache?

If so, yes let's get rid of that repo.

Also I found it works now with the -o flag.


Alan Gates mailto:ga...@hortonworks.com
October 8, 2014 at 11:18
It appears that the jars we need are in maven central.  I tried 
removing datanucleus completely from my maven cache then commenting 
out the datanucleus repository in pom.xml and the jars were properly 
fetched from maven central.  Should I just put up a patch for this so 
we can get building again?


Alan.


Brock Noland mailto:br...@cloudera.com
October 8, 2014 at 10:28
http://www.datanucleus.org/ is not accessiable

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project hive-exec: Error resolving project artifact:
Could not transfer artifact net.hydromatic:linq4j:pom:0.4 from/to
datanucleus (http://www.datanucleus.org/downloads/maven2): Access
denied to: 
http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,

ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 -
[Help 1]


--
Sent with Postbox http://www.getpostbox.com

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.


[jira] [Resolved] (HIVE-8399) Build failure on trunk 14 branch

2014-10-08 Thread Vaibhav Gumashta (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vaibhav Gumashta resolved HIVE-8399.

Resolution: Duplicate

 Build failure on trunk  14 branch
 --

 Key: HIVE-8399
 URL: https://issues.apache.org/jira/browse/HIVE-8399
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
Reporter: Vaibhav Gumashta
Priority: Blocker
 Fix For: 0.14.0


 {code}
 Downloading: 
 http://repo.maven.apache.org/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO] 
 [INFO] Hive .. SUCCESS [  2.591 s]
 [INFO] Hive Shims Common . SUCCESS [  1.774 s]
 [INFO] Hive Shims 0.20 ... SUCCESS [  0.656 s]
 [INFO] Hive Shims Secure Common .. SUCCESS [  0.954 s]
 [INFO] Hive Shims 0.20S .. SUCCESS [  0.516 s]
 [INFO] Hive Shims 0.23 ... SUCCESS [  1.769 s]
 [INFO] Hive Shims  SUCCESS [  0.192 s]
 [INFO] Hive Common ... SUCCESS [  3.753 s]
 [INFO] Hive Serde  SUCCESS [  3.005 s]
 [INFO] Hive Metastore  SUCCESS [ 10.376 s]
 [INFO] Hive Ant Utilities  SUCCESS [  0.266 s]
 [INFO] Hive Query Language ... FAILURE [ 10.606 s]
 [INFO] Hive Service .. SKIPPED
 [INFO] Hive Accumulo Handler . SKIPPED
 [INFO] Hive JDBC . SKIPPED
 [INFO] Hive Beeline .. SKIPPED
 [INFO] Hive CLI .. SKIPPED
 [INFO] Hive Contrib .. SKIPPED
 [INFO] Hive HBase Handler  SKIPPED
 [INFO] Hive HCatalog . SKIPPED
 [INFO] Hive HCatalog Core  SKIPPED
 [INFO] Hive HCatalog Pig Adapter . SKIPPED
 [INFO] Hive HCatalog Server Extensions ... SKIPPED
 [INFO] Hive HCatalog Webhcat Java Client . SKIPPED
 [INFO] Hive HCatalog Webhcat . SKIPPED
 [INFO] Hive HCatalog Streaming ... SKIPPED
 [INFO] Hive HWI .. SKIPPED
 [INFO] Hive ODBC . SKIPPED
 [INFO] Hive Shims Aggregator . SKIPPED
 [INFO] Hive TestUtils  SKIPPED
 [INFO] Hive Packaging  SKIPPED
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 37.318 s
 [INFO] Finished at: 2014-10-08T10:16:32-08:00
 [INFO] Final Memory: 54M/355M
 [INFO] 
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) 
 on project hive-exec: Error resolving project artifact: Could not transfer 
 artifact net.hydromatic:linq4j:pom:0.4 from/to datanucleus 
 (http://www.datanucleus.org/downloads/maven2): Access denied to: 
 http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom,
  ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 - [Help 
 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
 [ERROR] 
 [ERROR] After correcting the problems, you can resume the build with the 
 command
 [ERROR]   mvn goals -rf :hive-exec
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8403) Build broken by datanucleus.org being offline

2014-10-08 Thread Gunther Hagleitner (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163975#comment-14163975
 ] 

Gunther Hagleitner commented on HIVE-8403:
--

Trying it out right now.

 Build broken by datanucleus.org being offline
 -

 Key: HIVE-8403
 URL: https://issues.apache.org/jira/browse/HIVE-8403
 Project: Hive
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 0.14.0
Reporter: Alan Gates
Assignee: Alan Gates
Priority: Blocker
 Fix For: 0.14.0

 Attachments: HIVE-8403.patch


 datanucleus.org is not available, making it impossible to download jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8401) OrcFileMergeOperator only close last orc file it opened, which resulted in stale data in table directory

2014-10-08 Thread Xiaobing Zhou (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163980#comment-14163980
 ] 

Xiaobing Zhou commented on HIVE-8401:
-

There are about 58 q tests that are using ALTER TABLE...CONCATENATE, they might 
hit the same issue.

 OrcFileMergeOperator only close last orc file it opened, which resulted in 
 stale data in table directory
 

 Key: HIVE-8401
 URL: https://issues.apache.org/jira/browse/HIVE-8401
 Project: Hive
  Issue Type: Bug
Affects Versions: 0.14.0
 Environment: Windows Server
Reporter: Xiaobing Zhou
Assignee: Xiaobing Zhou
Priority: Critical
 Attachments: alter_merge_2_orc.q.out


 run the test
 {noformat}
 mvn -Phadoop-2  test -Dtest=TestCliDriver -Dqfile=alter_merge_2_orc.q
 {noformat}
 to reproduce it. Simply, this query does three data loads which generates 
 three orc files, ALTER TABLE CONCATENATE tries to merge orc pieces into a 
 single one which is final file to queried.
 Output 
 \hive\itests\qtest\target\qfile-results\clientpositive\alter_merge_2_orc.q.out
  shows # records as 600 that is wrong as opposed to 610 expected.
 Because OrcFileMergeOperator only closes last orc file, the 1st and 2nd orc 
 files still remain in table directory due to failure of deleting unclosed 
 file for old data clean when MoveTask tries to copy merged orc file from 
 scratch dir to table dir. Eventually the query goes to old data(1st and 2nd 
 orc files).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HIVE-8404) ColumnPruner doesnt prune columns from limit operator

2014-10-08 Thread Ashutosh Chauhan (JIRA)
Ashutosh Chauhan created HIVE-8404:
--

 Summary: ColumnPruner doesnt prune columns from limit operator
 Key: HIVE-8404
 URL: https://issues.apache.org/jira/browse/HIVE-8404
 Project: Hive
  Issue Type: Bug
  Components: Logical Optimizer
Affects Versions: 0.13.1, 0.13.0, 0.12.0
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan


Discovered while working on HIVE-8358 input26.q failure



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: Build appears to be broken by http://www.datanucleus.org/

2014-10-08 Thread Gunther Hagleitner
I'm trying it right now.

Thanks,
Gunther.

On Wed, Oct 8, 2014 at 11:49 AM, Alan Gates ga...@hortonworks.com wrote:

 I've created HIVE-8403 and attached a patch that works for  me when I do
 the maven.repo.local thing.  Someone else should try this on their
 machine.  If it works, please check it in.  I assume we don't have to wait
 for the 24 hour limit on patches like this.

 Alan.

   Brock Noland br...@cloudera.com
  October 8, 2014 at 11:25
 That works for me. IIRC when I did the maven build I learned we used the DN
 repo for something not DN related. Can you try the build
 with -Dmaven.repo.local=/tmp/maven and ensure it builds without any cache?

 If so, yes let's get rid of that repo.

 Also I found it works now with the -o flag.


   Alan Gates ga...@hortonworks.com
  October 8, 2014 at 11:18
  It appears that the jars we need are in maven central.  I tried removing
 datanucleus completely from my maven cache then commenting out the
 datanucleus repository in pom.xml and the jars were properly fetched from
 maven central.  Should I just put up a patch for this so we can get
 building again?

 Alan.


   Brock Noland br...@cloudera.com
  October 8, 2014 at 10:28
 http://www.datanucleus.org/ is not accessiable

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
 (default) on project hive-exec: Error resolving project artifact:
 Could not transfer artifact net.hydromatic:linq4j:pom:0.4 from/to
 datanucleus (http://www.datanucleus.org/downloads/maven2): Access
 denied to:
 http://www.datanucleus.org/downloads/maven2/net/hydromatic/linq4j/0.4/linq4j-0.4.pom
 ,
 ReasonPhrase: Forbidden. for project net.hydromatic:linq4j:jar:0.4 -
 [Help 1]


 --
 Sent with Postbox http://www.getpostbox.com

 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity
 to which it is addressed and may contain information that is confidential,
 privileged and exempt from disclosure under applicable law. If the reader
 of this message is not the intended recipient, you are hereby notified that
 any printing, copying, dissemination, distribution, disclosure or
 forwarding of this communication is strictly prohibited. If you have
 received this communication in error, please contact the sender immediately
 and delete it from your system. Thank You.


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.


[jira] [Updated] (HIVE-8358) Constant folding should happen before predicate pushdown

2014-10-08 Thread Ashutosh Chauhan (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Chauhan updated HIVE-8358:
---
Status: Open  (was: Patch Available)

 Constant folding should happen before predicate pushdown
 

 Key: HIVE-8358
 URL: https://issues.apache.org/jira/browse/HIVE-8358
 Project: Hive
  Issue Type: Improvement
  Components: Logical Optimizer
Affects Versions: 0.14.0
Reporter: Ashutosh Chauhan
Assignee: Ashutosh Chauhan
 Attachments: HIVE-8358.patch


 So, that partition pruning and transitive predicate propagation may take 
 advantage of constant folding.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (HIVE-8388) Support GROUP/ORDER BY column references by ordinal position

2014-10-08 Thread John Scheibmeir (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Scheibmeir resolved HIVE-8388.
---
Resolution: Duplicate

 Support GROUP/ORDER BY column references by ordinal position
 

 Key: HIVE-8388
 URL: https://issues.apache.org/jira/browse/HIVE-8388
 Project: Hive
  Issue Type: Improvement
  Components: SQL
Reporter: John Scheibmeir
Assignee: Gunther Hagleitner
Priority: Minor

 Allow user to reference the group by or order by column by the desired 
 column's ordinal position
 Support syntax such as:
 select t.col1, sum(t.col2) from my_table t group by 1 order by 1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HIVE-8388) Support GROUP/ORDER BY column references by ordinal position

2014-10-08 Thread John Scheibmeir (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163985#comment-14163985
 ] 

John Scheibmeir commented on HIVE-8388:
---

I see already available with option:
set hive.groupby.orderby.position.alias=true;

 Support GROUP/ORDER BY column references by ordinal position
 

 Key: HIVE-8388
 URL: https://issues.apache.org/jira/browse/HIVE-8388
 Project: Hive
  Issue Type: Improvement
  Components: SQL
Reporter: John Scheibmeir
Assignee: Gunther Hagleitner
Priority: Minor

 Allow user to reference the group by or order by column by the desired 
 column's ordinal position
 Support syntax such as:
 select t.col1, sum(t.col2) from my_table t group by 1 order by 1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8393) Handle SIGINT on Tez

2014-10-08 Thread Gunther Hagleitner (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gunther Hagleitner updated HIVE-8393:
-
Status: Open  (was: Patch Available)

 Handle SIGINT on Tez
 

 Key: HIVE-8393
 URL: https://issues.apache.org/jira/browse/HIVE-8393
 Project: Hive
  Issue Type: Bug
Reporter: Gunther Hagleitner
Assignee: Gunther Hagleitner
 Attachments: HIVE-8393.1.patch, HIVE-8393.2.patch


 The signal handler in hive currently only interrupts MR jobs. The same logic 
 can be used to interrupt Tez dags as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8393) Handle SIGINT on Tez

2014-10-08 Thread Gunther Hagleitner (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gunther Hagleitner updated HIVE-8393:
-
Attachment: HIVE-8393.2.patch

 Handle SIGINT on Tez
 

 Key: HIVE-8393
 URL: https://issues.apache.org/jira/browse/HIVE-8393
 Project: Hive
  Issue Type: Bug
Reporter: Gunther Hagleitner
Assignee: Gunther Hagleitner
 Attachments: HIVE-8393.1.patch, HIVE-8393.2.patch


 The signal handler in hive currently only interrupts MR jobs. The same logic 
 can be used to interrupt Tez dags as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-8393) Handle SIGINT on Tez

2014-10-08 Thread Gunther Hagleitner (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gunther Hagleitner updated HIVE-8393:
-
Status: Patch Available  (was: Open)

 Handle SIGINT on Tez
 

 Key: HIVE-8393
 URL: https://issues.apache.org/jira/browse/HIVE-8393
 Project: Hive
  Issue Type: Bug
Reporter: Gunther Hagleitner
Assignee: Gunther Hagleitner
 Attachments: HIVE-8393.1.patch, HIVE-8393.2.patch


 The signal handler in hive currently only interrupts MR jobs. The same logic 
 can be used to interrupt Tez dags as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


  1   2   3   >