[jira] [Created] (HIVE-16086) Fix HiveMetaStoreChecker.checkPartitionDirsSingleThreaded method

2017-03-01 Thread Kiran Kumar Kolli (JIRA) 
Kiran Kumar Kolli created HIVE-16086:


 Summary: Fix HiveMetaStoreChecker.checkPartitionDirsSingleThreaded 
method
 Key: HIVE-16086
 URL: https://issues.apache.org/jira/browse/HIVE-16086
 Project: Hive
  Issue Type: Bug
Reporter: Kiran Kumar Kolli
Assignee: Kiran Kumar Kolli
 Fix For: 2.2.0


checkPartitionDirsSingleThreaded BFS implementation has a bug and its 
traversing the paths repeatedly. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 56810: Compute table stats when user computes column stats

2017-03-01 Thread pengcheng xiong 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56810/
---

(Updated March 2, 2017, 6:26 a.m.)


Review request for hive and Ashutosh Chauhan.


Repository: hive-git


Description
---

HIVE-15903


Diffs (updated)
-

  itests/src/test/resources/testconfiguration.properties b01ebd8 
  ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMapRedUtils.java 0e67ea6 
  ql/src/java/org/apache/hadoop/hive/ql/parse/BaseSemanticAnalyzer.java 3e749eb 
  ql/src/java/org/apache/hadoop/hive/ql/parse/ColumnStatsSemanticAnalyzer.java 
93b8183 
  ql/src/java/org/apache/hadoop/hive/ql/parse/ProcessAnalyzeTable.java c13a404 
  ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 0872e53 
  ql/src/test/queries/clientpositive/column_table_stats.q PRE-CREATION 
  ql/src/test/queries/clientpositive/exec_parallel_column_stats.q ceacc24 
  ql/src/test/results/clientpositive/alter_table_update_status.q.out a3c4f1a 
  ql/src/test/results/clientpositive/analyze_tbl_date.q.out a0cdbca 
  ql/src/test/results/clientpositive/analyze_tbl_part.q.out ed90b6f 
  ql/src/test/results/clientpositive/annotate_stats_deep_filters.q.out 32644dc 
  ql/src/test/results/clientpositive/annotate_stats_filter.q.out e22c3ef 
  ql/src/test/results/clientpositive/annotate_stats_groupby.q.out a8e4854 
  ql/src/test/results/clientpositive/annotate_stats_groupby2.q.out 31c4ed1 
  ql/src/test/results/clientpositive/annotate_stats_join.q.out 5d4fe6c 
  ql/src/test/results/clientpositive/annotate_stats_join_pkfk.q.out b4d46d2 
  ql/src/test/results/clientpositive/annotate_stats_limit.q.out ea181cb 
  ql/src/test/results/clientpositive/annotate_stats_select.q.out 873f1ab 
  ql/src/test/results/clientpositive/annotate_stats_table.q.out efc3c1f 
  ql/src/test/results/clientpositive/annotate_stats_union.q.out 059f261 
  ql/src/test/results/clientpositive/autoColumnStats_3.q.out dca158b 
  ql/src/test/results/clientpositive/avro_decimal.q.out 64e65ca 
  ql/src/test/results/clientpositive/avro_decimal_native.q.out cebc342 
  ql/src/test/results/clientpositive/cbo_rp_annotate_stats_groupby.q.out 
f260f03 
  ql/src/test/results/clientpositive/cbo_rp_auto_join1.q.out fe4bc4f 
  ql/src/test/results/clientpositive/colstats_all_nulls.q.out f67f81b 
  ql/src/test/results/clientpositive/columnStatsUpdateForStatsOptimizer_2.q.out 
af21343 
  ql/src/test/results/clientpositive/columnstats_partlvl.q.out 5c9f901 
  ql/src/test/results/clientpositive/columnstats_partlvl_dp.q.out 08fb42e 
  ql/src/test/results/clientpositive/columnstats_quoting.q.out 52e3538 
  ql/src/test/results/clientpositive/columnstats_tbllvl.q.out 60652e0 
  ql/src/test/results/clientpositive/compustat_avro.q.out 50c03bd 
  ql/src/test/results/clientpositive/compute_stats_date.q.out 73f08ad 
  ql/src/test/results/clientpositive/constGby.q.out fd8ecc2 
  ql/src/test/results/clientpositive/constant_prop_3.q.out ecf6e57 
  ql/src/test/results/clientpositive/decimal_stats.q.out cb02f76 
  ql/src/test/results/clientpositive/deleteAnalyze.q.out 4382522 
  ql/src/test/results/clientpositive/display_colstats_tbllvl.q.out e10edb4 
  ql/src/test/results/clientpositive/distinct_stats.q.out 73b4add 
  ql/src/test/results/clientpositive/drop_table_with_stats.q.out 52aa10a 
  ql/src/test/results/clientpositive/exec_parallel_column_stats.q.out f256ec1 
  ql/src/test/results/clientpositive/extrapolate_part_stats_date.q.out b12d3a1 
  
ql/src/test/results/clientpositive/llap/alter_table_invalidate_column_stats.q.out
 85d7dc4 
  
ql/src/test/results/clientpositive/llap/columnStatsUpdateForStatsOptimizer_1.q.out
 80ccddd 
  ql/src/test/results/clientpositive/llap/column_table_stats.q.out PRE-CREATION 
  ql/src/test/results/clientpositive/llap/columnstats_part_coltype.q.out 
3e28e58 
  ql/src/test/results/clientpositive/llap/deleteAnalyze.q.out ba14835 
  ql/src/test/results/clientpositive/llap/drop_partition_with_stats.q.out 
c6ab40d 
  ql/src/test/results/clientpositive/llap/explainuser_2.q.out e898111 
  ql/src/test/results/clientpositive/llap/llap_stats.q.out f6921f1 
  ql/src/test/results/clientpositive/llap/llapdecider.q.out d514f42 
  ql/src/test/results/clientpositive/llap/metadata_only_queries.q.out c8190bd 
  ql/src/test/results/clientpositive/llap/schema_evol_stats.q.out be8ca4a 
  ql/src/test/results/clientpositive/llap/special_character_in_tabnames_1.q.out 
d01b373 
  ql/src/test/results/clientpositive/llap/stats_only_null.q.out c905ceb 
  ql/src/test/results/clientpositive/llap/union_remove_26.q.out 18b9aa5 
  ql/src/test/results/clientpositive/llap/vector_outer_join1.q.out 072399e 
  ql/src/test/results/clientpositive/llap/vector_outer_join2.q.out d79c71b 
  ql/src/test/results/clientpositive/llap/vector_outer_join3.q.out dbbfd34 
  ql/src/test/results/clientpositive/llap/vector_outer_join4.q.out ffce9e6

Re: Review Request 53845: 'like any' and 'like all' operators in hive

2017-03-01 Thread Carl Steinbach 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/53845/#review167648
---




ql/src/java/org/apache/hadoop/hive/ql/parse/HiveLexer.g
Line 2 (original), 2 (patched)


Please make whitespace fixes in a separate patch. Including them here 
pollutes the diff and draws the attention of reviewers away from the important 
parts. I saw the same problem in several other files as well.



ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFLikeAll.java
Lines 51 (patched)


Please change to "Returns NULL if the expression on the left hand side is 
NULL or if one of the patterns in the list is NULL."


- Carl Steinbach


On Feb. 15, 2017, 6:47 a.m., Simanchal Das wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/53845/
> ---
> 
> (Updated Feb. 15, 2017, 6:47 a.m.)
> 
> 
> Review request for hive, Carl Steinbach and Vineet Garg.
> 
> 
> Repository: hive-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/HIVE-15229
> 
> 
> In Teradata 'like any' and 'like all' operators are mostly used when we are 
> matching a text field with numbers of patterns.
> 'like any' and 'like all' operator are equivalents of multiple like operator 
> like example below.
> --like any
> select col1 from table1 where col2 like any ('%accountant%', '%accounting%', 
> '%retail%', '%bank%', '%insurance%');
> 
> --Can be written using multiple like condition 
> select col1 from table1 where col2 like '%accountant%' or col2 like 
> '%accounting%' or col2 like '%retail%' or col2 like '%bank%' or col2 like 
> '%insurance%' ;
> 
> --like all
> select col1 from table1 where col2 like all ('%accountant%', '%accounting%', 
> '%retail%', '%bank%', '%insurance%');
> 
> --Can be written using multiple like operator 
> select col1 from table1 where col2 like '%accountant%' and col2 like 
> '%accounting%' and col2 like '%retail%' and col2 like '%bank%' and col2 like 
> '%insurance%' ;
> 
> Problem statement:
> 
> Now a days so many data warehouse projects are being migrated from Teradata 
> to Hive.
> Always Data engineer and Business analyst are searching for these two 
> operator.
> If we introduce these two operator in hive then so many scripts will be 
> migrated smoothly instead of converting these operators to multiple like 
> operators.
> 
> 
> Diffs
> -
> 
>   ql/src/java/org/apache/hadoop/hive/ql/exec/FunctionRegistry.java 0f05160 
>   ql/src/java/org/apache/hadoop/hive/ql/parse/HiveLexer.g f80642b 
>   ql/src/java/org/apache/hadoop/hive/ql/parse/HiveParser.g eb81393 
>   ql/src/java/org/apache/hadoop/hive/ql/parse/IdentifiersParser.g 81efadc 
>   ql/src/java/org/apache/hadoop/hive/ql/parse/TypeCheckProcFactory.java 
> f979c14 
>   ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFLikeAll.java 
> PRE-CREATION 
>   ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFLikeAny.java 
> PRE-CREATION 
>   
> ql/src/test/org/apache/hadoop/hive/ql/udf/generic/TestGenericUDFLikeAll.java 
> PRE-CREATION 
>   
> ql/src/test/org/apache/hadoop/hive/ql/udf/generic/TestGenericUDFLikeAny.java 
> PRE-CREATION 
>   ql/src/test/queries/clientnegative/udf_likeall_wrong1.q PRE-CREATION 
>   ql/src/test/queries/clientnegative/udf_likeany_wrong1.q PRE-CREATION 
>   ql/src/test/queries/clientpositive/udf_likeall.q PRE-CREATION 
>   ql/src/test/queries/clientpositive/udf_likeany.q PRE-CREATION 
>   ql/src/test/results/clientnegative/udf_likeall_wrong1.q.out PRE-CREATION 
>   ql/src/test/results/clientnegative/udf_likeany_wrong1.q.out PRE-CREATION 
>   ql/src/test/results/clientpositive/show_functions.q.out 3c9bb4a 
>   ql/src/test/results/clientpositive/udf_likeall.q.out PRE-CREATION 
>   ql/src/test/results/clientpositive/udf_likeany.q.out PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/53845/diff/7/
> 
> 
> Testing
> ---
> 
> Junit test cases and query.q files are attached
> 
> 
> Thanks,
> 
> Simanchal Das
> 
>

[jira] [Created] (HIVE-16085) get path-to-alias, path-to-work etc recursively in Hive

2017-03-01 Thread Sergey Shelukhin (JIRA) 
Sergey Shelukhin created HIVE-16085:
---

 Summary: get path-to-alias, path-to-work etc recursively in Hive
 Key: HIVE-16085
 URL: https://issues.apache.org/jira/browse/HIVE-16085
 Project: Hive
  Issue Type: Task
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin


Sometimes, we don't get correct alias/part desc/etc. from paths - e.g. in 
HIVE-15870 (for MM tables).
We have methods in utils for partdescs to work around that, but they are not 
applied consistently. I suspect people add calls to this method after they 
discover some particular path is broken; perhaps we should find such places 
proactively for path-to-part, path-to-work, and path-to-alias maps.
This can happen much more with MM tables, but can also happen for any 
recursive-path cases (incl. just a regular recursive path read enabled via an 
MR config).




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16084) SHOW COMPACTIONS should display CompactionID

2017-03-01 Thread Eugene Koifman (JIRA) 
Eugene Koifman created HIVE-16084:
-

 Summary: SHOW COMPACTIONS should display CompactionID
 Key: HIVE-16084
 URL: https://issues.apache.org/jira/browse/HIVE-16084
 Project: Hive
  Issue Type: Test
  Components: Transactions
Reporter: Eugene Koifman
Assignee: Eugene Koifman


together with HIVE-13353 it will let users search for specific job



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16083) Hive should escape fields terminator when use textfile format

2017-03-01 Thread Winston Churchill (JIRA) 
Winston Churchill created HIVE-16083:


 Summary: Hive should escape fields terminator when use textfile 
format
 Key: HIVE-16083
 URL: https://issues.apache.org/jira/browse/HIVE-16083
 Project: Hive
  Issue Type: Bug
  Components: File Formats
Affects Versions: 2.1.1
Reporter: Winston Churchill
Priority: Trivial


Create table with comon as fields terminator and insert data contains comon:
{code}
create table test_1(id int,name string) row format delimited fields terminated 
by ',' stored as textfile;
insert into table test_1 values (1,'a,b,c')；
{code}

{code}
select * from test_1;
++--+--+
| test_1.id  | test_1.name  |
++--+--+
| 1  | a|
++--+--+
4 rows selected (0.363 seconds)
{code}

May need to escape the fields terminator ?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 57094: HIVE-15996

2017-03-01 Thread Ashutosh Chauhan 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/57094/#review167635
---




ql/src/test/results/clientpositive/groupby_grouping_sets_grouping.q.out
Line 436 (original), 436 (patched)


Not sure if standard says anything, but sql server has return type of 
tinyint for grouping: https://msdn.microsoft.com/en-us/library/ms178544.aspx



ql/src/test/results/clientpositive/groupby_grouping_sets_grouping.q.out
Lines 1070 (patched)


This looks incorrect. When both columns are NULL NULL meaning all rows are 
present in this group grouping(k) = 1 and grouping(value)=1 and 
grouping(key,value) = 3. Instead we are getting 0.
Verified on oracle as well.



ql/src/test/results/clientpositive/groupby_grouping_sets_grouping.q.out
Lines 1071 (patched)


select k, value, grouping(k), grouping(value), grouping_id(k,value)
from T1
group by cube(k, value);

Output:
K   VALUE   GROUPING(K) GROUPING(VALUE) GROUPING_ID(K,VALUE)
 -   -  1   0   2
 -   -  1   1   3
 -  1   1   0   2
 -  2   1   0   2
 -  3   1   0   2
 -  5   1   0   2
1-  0   0   0
1-  0   1   1
1   1   0   0   0
2-  0   1   1
2   2   0   0   0
3-  0   0   0
3-  0   1   1
3   3   0   0   0
4-  0   1   1
4   5   0   0   0


- Ashutosh Chauhan


On Feb. 27, 2017, 2:37 p.m., Jesús Camacho Rodríguez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57094/
> ---
> 
> (Updated Feb. 27, 2017, 2:37 p.m.)
> 
> 
> Review request for hive and Ashutosh Chauhan.
> 
> 
> Bugs: HIVE-15996
> https://issues.apache.org/jira/browse/HIVE-15996
> 
> 
> Repository: hive-git
> 
> 
> Description
> ---
> 
> HIVE-15996
> 
> 
> Diffs
> -
> 
>   ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 
> 0872e535a9b6a09569c02fc498dab16867ca8783 
>   ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFGrouping.java 
> cc015268de0ab1e32401c1cf7c21502fb2a45331 
>   ql/src/test/queries/clientpositive/groupby_grouping_sets_grouping.q 
> 78560978ccb84c0737decf45cb56810195be288d 
>   ql/src/test/results/clientpositive/groupby_grouping_sets_grouping.q.out 
> 6917dbabb96b5a582416ac7f07968b739823a13f 
> 
> 
> Diff: https://reviews.apache.org/r/57094/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Jesús Camacho Rodríguez
> 
>

[jira] [Created] (HIVE-16082) Allow user to change number of listener thread in LlapTaskCommunicator

2017-03-01 Thread Zhiyuan Yang (JIRA) 
Zhiyuan Yang created HIVE-16082:
---

 Summary: Allow user to change number of listener thread in 
LlapTaskCommunicator
 Key: HIVE-16082
 URL: https://issues.apache.org/jira/browse/HIVE-16082
 Project: Hive
  Issue Type: Bug
Reporter: Zhiyuan Yang
Assignee: Zhiyuan Yang


Now LlapTaskCommunicator always has same number of RPC listener thread with 
TezTaskCommunicatorImpl. There are scenarios when we want them different: for 
example, in Llap only mode, we want less TezTaskCommunicatorImpl's listener 
thread to reduce off-heap memory usage.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16081) update shim creation for Hadoop 3

2017-03-01 Thread Sergey Shelukhin (JIRA) 
Sergey Shelukhin created HIVE-16081:
---

 Summary: update shim creation for Hadoop 3
 Key: HIVE-16081
 URL: https://issues.apache.org/jira/browse/HIVE-16081
 Project: Hive
  Issue Type: Bug
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin


We only have one shim, so for now, we are going to use that. Hopefully we won't 
need shims and build profiles for Hadoop 3



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16080) Add parquet to possible values for hive.default.fileformat

2017-03-01 Thread Sahil Takiar (JIRA) 
Sahil Takiar created HIVE-16080:
---

 Summary: Add parquet to possible values for hive.default.fileformat
 Key: HIVE-16080
 URL: https://issues.apache.org/jira/browse/HIVE-16080
 Project: Hive
  Issue Type: Bug
Reporter: Sahil Takiar
Assignee: Sahil Takiar






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16079) HS2: high memory pressure due to duplicate Properties objects

2017-03-01 Thread Misha Dmitriev (JIRA) 
Misha Dmitriev created HIVE-16079:
-

 Summary: HS2: high memory pressure due to duplicate Properties 
objects
 Key: HIVE-16079
 URL: https://issues.apache.org/jira/browse/HIVE-16079
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Reporter: Misha Dmitriev
Assignee: Misha Dmitriev
 Attachments: hs2-crash-2000p-500m-50q.txt

I've created a Hive table with 2000 partitions, each backed by two files, with 
one row in each file. When I execute some number of concurrent queries against 
this table, e.g. as follows

{code}
for i in `seq 1 50`; do beeline -u jdbc:hive2://localhost:1 -n admin -p 
admin -e "select count(i_f_1) from misha_table;" & done
{code}

it results in a big memory spike. With 20 queries I caused an OOM in a HS2 
server with -Xmx200m and with 50 queries - in the one with -Xmx500m.

I am attaching the results of jxray (www.jxray.com) analysis of a heap dump 
that was generated in the 50queries/500m heap scenario. It suggests that there 
are several opportunities to reduce memory pressure with not very invasive 
changes to the code:

1. 24.5% of memory is wasted by duplicate strings (see section 6). With 
String.intern() calls added in the ~10 relevant places in the code, this 
overhead can be highly reduced.

2. Almost 20% of memory is wasted due to various suboptimally used collections 
(see section 8). There are many maps and lists that are either empty or have 
just 1 element. By modifying the code that creates and populates these 
collections, we may likely save 5-10% of memory.

3. Almost 20% of memory is used by instances of java.util.Properties. It looks 
like these objects are highly duplicate, since for each Partition each 
concurrently running query creates its own copy of Partion, PartitionDesc and 
Properties. Thus we have nearly 100,000 (50 queries * 2,000 partitions) 
Properties in memory. By interning/deduplicating these objects we may be able 
to save perhaps 15% of memory.

So overall, I think there is a good chance to reduce HS2 memory consumption in 
this scenario by ~40%.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16078) improve abort checking in Tez/LLAP

2017-03-01 Thread Sergey Shelukhin (JIRA) 
Sergey Shelukhin created HIVE-16078:
---

 Summary: improve abort checking in Tez/LLAP
 Key: HIVE-16078
 URL: https://issues.apache.org/jira/browse/HIVE-16078
 Project: Hive
  Issue Type: Bug
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin


Sometimes, a fragment can run for a long time after a query fails. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16077) A tests where number of buckets is > number of reducers for Acid

2017-03-01 Thread Eugene Koifman (JIRA) 
Eugene Koifman created HIVE-16077:
-

 Summary: A tests where number of buckets is > number of reducers 
for Acid
 Key: HIVE-16077
 URL: https://issues.apache.org/jira/browse/HIVE-16077
 Project: Hive
  Issue Type: Test
  Components: Transactions
Reporter: Eugene Koifman


don't think we have such tests for Acid path
check if they exist for non-acid path



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16076) LLAP packaging - include aux libs

2017-03-01 Thread Sergey Shelukhin (JIRA) 
Sergey Shelukhin created HIVE-16076:
---

 Summary: LLAP packaging - include aux libs 
 Key: HIVE-16076
 URL: https://issues.apache.org/jira/browse/HIVE-16076
 Project: Hive
  Issue Type: Bug
Reporter: Gunther Hagleitner


The old auxlibs (or whatever) should be packaged by default, if present.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16075) MetaStore needs to reinitialize log4j to allow log specific settings via hiveconf take effect

2017-03-01 Thread yunfei liu (JIRA) 
yunfei liu created HIVE-16075:
-

 Summary: MetaStore needs to reinitialize log4j to allow log 
specific settings via hiveconf take effect 
 Key: HIVE-16075
 URL: https://issues.apache.org/jira/browse/HIVE-16075
 Project: Hive
  Issue Type: Improvement
  Components: Metastore
Affects Versions: 2.2.0
Reporter: yunfei liu
Assignee: yunfei liu
Priority: Minor


when I start hive metastore with command :
{quote}
{{hive --service metastore -hiveconf hive.log.file=hivemetastore.log -hiveconf 
hive.log.dir=/home/yun/hive/log}}
{quote}
The two log parameters won't take effect。
The reason is that : After metastore copy hive conf parameters into java system 
properties, it doesn't reinitialize log4j



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16074) Parser can not deal with complex sql

2017-03-01 Thread JIRA 
靳峥 created HIVE-16074:
-

 Summary: Parser can not deal with complex sql
 Key: HIVE-16074
 URL: https://issues.apache.org/jira/browse/HIVE-16074
 Project: Hive
  Issue Type: Bug
  Components: Parser
Affects Versions: 2.1.1
Reporter: 靳峥
 Fix For: 2.2.0


Parser will stuck when parsing the sql into ast, eg:
select 
intType,floatType,stringType,varchar32Type,byteType,shortType,dateType,timestampType,longType
 , max(intType | 0) from orctest where 
((1=2)) and ((1=1))) or (((2=2)) and 
((1=2 and (((1=1)) or ((0=0 or (((1=0)) or ((1=2 or (((1=1)) or 
((0=0 or (((1=1)) and ((0=0 or (((2=2)) or ((2=2 and (((2=2)) or 
((2=2 and (((2=2)) or ((1=2 or (((0=0)) and ((1=0 or (((1=1)) and 
((1=2 or (((1=1)) and ((2=2 or (((1=2)) and ((1=1 or (((1=1)) and 
((2=2 or (((1=1)) or ((1=1 and (((0=0)) and ((0=0 or (((0=0)) or 
((1=2 and (((1=2)) and ((1=1 and (((0=0)) or ((2=2 or (((1=2)) or 
((2=2 and (((0=0)) and ((1=2 or (((1=2)) or ((1=0 or (((2=2)) or 
((1=0 or (((2=2)) or ((1=2 or (((1=2)) or ((1=1 and (((1=2)) or 
((1=2 and (((1=0)) or ((2=2 and (((2=2)) or ((1=0 and (((1=2)) or 
((1=1 and (((1=2)) or ((1=2 and (((2=2)) and ((1=0 and (((2=2)) or 
((1=1 or (((0=0)) and ((1=1 and (((2=2)) or ((1=2 and (((1=2)) or 
((0=0 or (((1=0)) and ((1=1 or (((1=1)) and ((1=2))) group by 
intType,floatType,stringType,varchar32Type,byteType,shortType,dateType,timestampType,longType;

The jvm of Server was working fine, with continues minor gc.
The cpu kept 100%.
It means the java logic generated by antlr is too complex.
The way to solve the problem may be optimize the syntax file or update the 
version of antlr.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HIVE-16073) Fix partition column check during runtime filtering

2017-03-01 Thread Jason Dere (JIRA) 
Jason Dere created HIVE-16073:
-

 Summary: Fix partition column check during runtime filtering
 Key: HIVE-16073
 URL: https://issues.apache.org/jira/browse/HIVE-16073
 Project: Hive
  Issue Type: Bug
  Components: Query Planning
Reporter: Jason Dere
Assignee: Jason Dere


Followup of incorrect partition column check from HIVE-16022.
Couple things to look at:
1. Does this check need to happen at all? Seems like this was a workaround.
2. If it is necessary, the logic looked incorrect.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)