[jira] [Commented] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958066#comment-15958066 ] Takuma Wakamori commented on HIVE-13958: [~pxiong] Hello. I fixed the patches to be applied to the current branch. A lot of time passed since the first patch is attached, so I removed old one and create `HIVE-13958.01.patch`. Then I noticed that `HIVE-13958.03.patch` is created by [~sershe] (thanks!). I can't resolve these conflicts, sorry. If the privileged user can resolve this, please arrange these files, or simply remove me from assignee.. I'm sorry for the inconvenience. Regards, > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.01.patch, HIVE-13958.03.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Comment: was deleted (was: Apply checkTypeSafety to IN and BETWEEN ops, add test cases.) > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.01.patch, HIVE-13958.03.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: HIVE-13958.01.patch Apply checkTypeSafe to IN and BETWEEN ops, and add test cases. > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.01.patch, HIVE-13958.03.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: (was: HIVE-13958.1.patch) > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.03.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: HIVE-13958.1.patch Apply checkTypeSafety to IN and BETWEEN ops, add test cases. > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.03.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: (was: HIVE-13958.04.patch) > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.03.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: (was: HIVE-13958.02.patch) > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.03.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: (was: HIVE-13958.01.patch) > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.02.patch, HIVE-13958.03.patch, > HIVE-13958.04.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363490#comment-15363490 ] Takuma Wakamori commented on HIVE-13958: @Sergey Shelukhin Thank you for reviewing. I apologize in adbance that it will take a long time to fix it. Because I have lost my laptop recently. I'm buying new one now. If it is unacceptable, please unassign me from this issue. Best, > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.01.patch, HIVE-13958.02.patch, > HIVE-13958.03.patch, HIVE-13958.04.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: HIVE-13958.04.patch updated the patch to response to the review comments. > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.01.patch, HIVE-13958.02.patch, > HIVE-13958.03.patch, HIVE-13958.04.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-13735) Query involving only partition columns need not launch mr/tez job
[
https://issues.apache.org/jira/browse/HIVE-13735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329101#comment-15329101
]
Takuma Wakamori commented on HIVE-13735:
Hi, [~rajesh.balamohan].
If there is no one working on this issue, I will try.
However, I imagine that my solution may be ad-hoc; the corresponding code will
be executed only under the condition like:
(the query is select) && (have distinct clause) && (select_expr is a
partitioning key) && (...).
If it is OK, could anyone assign me to this issue? Thanks.
> Query involving only partition columns need not launch mr/tez job
> -
>
> Key: HIVE-13735
> URL: https://issues.apache.org/jira/browse/HIVE-13735
> Project: Hive
> Issue Type: Bug
>Reporter: Rajesh Balamohan
>
> codebase: hive master
> dataset: tpc-ds 10 TB scale
> e.g queries:
> {noformat}
> hive> show partitions web_sales;
> ...
> ...
> Time taken: 0.13 seconds, Fetched: 1824 row(s)
> hive> select distinct ws_sold_date_sk from web_sales;
> --
> VERTICES MODESTATUS TOTAL COMPLETED RUNNING PENDING
> FAILED KILLED
> --
> Map 1 .. container SUCCEEDED 1 100
> 0 0
> Reducer 2 .. container SUCCEEDED 1 100
> 0 0
> --
> VERTICES: 02/02 [==>>] 100% ELAPSED TIME: 2.70 s
> --
> Status: DAG finished successfully in 2.70 seconds
> ..
> Time taken: 3.964 seconds, Fetched: 1824 row(s)
> hive> select distinct ws_sold_date_sk from web_sales order by ws_sold_date_sk;
> --
> VERTICES MODESTATUS TOTAL COMPLETED RUNNING PENDING
> FAILED KILLED
> --
> Map 1 .. container SUCCEEDED80180100
> 0 0
> Reducer 2 .. container SUCCEEDED 1 100
> 0 0
> Reducer 3 .. container SUCCEEDED 1 100
> 0 0
> --
> VERTICES: 03/03 [==>>] 100% ELAPSED TIME: 23.05 s
> --
> Status: DAG finished successfully in 23.05 seconds
> ...
> Time taken: 27.095 seconds, Fetched: 1824 row(s)
> {noformat}
> since the info is already available in metastore, it might not need to launch
> these jobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-13928) Hive2: float value need to be single quoted inside where clause to return rows when it doesn't have to be
[
https://issues.apache.org/jira/browse/HIVE-13928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328965#comment-15328965
]
Takuma Wakamori commented on HIVE-13928:
Hi.
Does anyone working on this issue?
If not, I would like to fix it. Thanks!
> Hive2: float value need to be single quoted inside where clause to return
> rows when it doesn't have to be
> -
>
> Key: HIVE-13928
> URL: https://issues.apache.org/jira/browse/HIVE-13928
> Project: Hive
> Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Takahiko Saito
>Priority: Critical
>
> The below select where with float value does not return any row:
> {noformat}
> 0: jdbc:hive2://os-r7-mvjkcu-hiveserver2-11-4> drop table test;
> No rows affected (0.212 seconds)
> 0: jdbc:hive2://os-r7-mvjkcu-hiveserver2-11-4> create table test (f float);
> No rows affected (1.131 seconds)
> 0: jdbc:hive2://os-r7-mvjkcu-hiveserver2-11-4> insert into table test values
> (-35664.76),(29497.34);
> No rows affected (2.482 seconds)
> 0: jdbc:hive2://os-r7-mvjkcu-hiveserver2-11-4> select * from test;
> ++--+
> | test.f |
> ++--+
> | -35664.76 |
> | 29497.34 |
> ++--+
> 2 rows selected (0.142 seconds)
> 0: jdbc:hive2://os-r7-mvjkcu-hiveserver2-11-4> select * from test where f =
> -35664.76;
> +-+--+
> | test.f |
> +-+--+
> +-+--+
> {noformat}
> The workaround is to single quote float value:
> {noformat}
> 0: jdbc:hive2://os-r7-mvjkcu-hiveserver2-11-4> select * from test where f =
> '-35664.76';
> ++--+
> | test.f |
> ++--+
> | -35664.76 |
> ++--+
> 1 row selected (0.163 seconds)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[
https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327800#comment-15327800
]
Takuma Wakamori edited comment on HIVE-13958 at 6/13/16 5:41 PM:
-
[~sershe] Thanks! I am sorry for my late reseponse.
I attached patches that checks the implicit type-cast is allowed to the
arguments passed to not only {{WHERE}} but also {{IN}} and {{BETWEEN}} operator.
It includes minor typo fixes.
I would appreciate it if you could review it. Thanks!
was (Author: takuma):
Check the implicit type-cast is allowed to the arguments passed to not only
{{WHERE}} but also {{IN}} and {{BETWEEN}} operator.
It includes minor typo fixes.
> hive.strict.checks.type.safety should apply to decimals, as well as IN... and
> BETWEEN... ops
>
>
> Key: HIVE-13958
> URL: https://issues.apache.org/jira/browse/HIVE-13958
> Project: Hive
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sergey Shelukhin
>Assignee: Takuma Wakamori
> Labels: patch
> Attachments: HIVE-13958.01.patch, HIVE-13958.02.patch
>
>
> String to decimal auto-casts should be prohibited for compares
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13958: --- Attachment: HIVE-13958.02.patch HIVE-13958.01.patch > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sergey Shelukhin >Assignee: Takuma Wakamori > Labels: patch > Attachments: HIVE-13958.01.patch, HIVE-13958.02.patch > > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[
https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takuma Wakamori updated HIVE-13958:
---
Labels: patch (was: )
Affects Version/s: 2.2.0
Target Version/s: 2.2.0
Status: Patch Available (was: Open)
Check the implicit type-cast is allowed to the arguments passed to not only
{{WHERE}} but also {{IN}} and {{BETWEEN}} operator.
It includes minor typo fixes.
> hive.strict.checks.type.safety should apply to decimals, as well as IN... and
> BETWEEN... ops
>
>
> Key: HIVE-13958
> URL: https://issues.apache.org/jira/browse/HIVE-13958
> Project: Hive
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Sergey Shelukhin
>Assignee: Takuma Wakamori
> Labels: patch
>
> String to decimal auto-casts should be prohibited for compares
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-10337) CBO (Calcite Return Path): java.lang.IndexOutOfBoundsException for query with rank() over(partition ...)
[
https://issues.apache.org/jira/browse/HIVE-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322276#comment-15322276
]
Takuma Wakamori commented on HIVE-10337:
Hi [~mmokhtar], could you tell me the affecting version of this issue?
With my Hive 2.2.0-SNAPSHOT binary build from source, the
IndexOutOfBoundsException never be occurred.
Thanks!
> CBO (Calcite Return Path): java.lang.IndexOutOfBoundsException for query with
> rank() over(partition ...)
>
>
> Key: HIVE-10337
> URL: https://issues.apache.org/jira/browse/HIVE-10337
> Project: Hive
> Issue Type: Bug
>Reporter: Mostafa Mokhtar
>
> CBO throws Index out of bound exception for TPC-DS Q70.
> Query
> {code}
> explain
> select
> sum(ss_net_profit) as total_sum
>,s_state
>,s_county
>,grouping__id as lochierarchy
>, rank() over(partition by grouping__id, case when grouping__id == 2 then
> s_state end order by sum(ss_net_profit)) as rank_within_parent
> from
> store_sales ss join date_dim d1 on d1.d_date_sk = ss.ss_sold_date_sk
> join store s on s.s_store_sk = ss.ss_store_sk
> where
> d1.d_month_seq between 1193 and 1193+11
> and s.s_state in
> ( select s_state
>from (select s_state as s_state, sum(ss_net_profit),
> rank() over ( partition by s_state order by
> sum(ss_net_profit) desc) as ranking
> from store_sales, store, date_dim
> where d_month_seq between 1193 and 1193+11
> and date_dim.d_date_sk =
> store_sales.ss_sold_date_sk
> and store.s_store_sk = store_sales.ss_store_sk
> group by s_state
> ) tmp1
>where ranking <= 5
> )
> group by s_state,s_county with rollup
> order by
>lochierarchy desc
> ,case when lochierarchy = 0 then s_state end
> ,rank_within_parent
> limit 100
> {code}
> Exception
> {code}
> 15/04/14 02:42:52 [main]: ERROR parse.CalcitePlanner: CBO failed, skipping
> CBO.
> java.lang.IndexOutOfBoundsException: Index: 5, Size: 5
> at java.util.ArrayList.rangeCheck(ArrayList.java:635)
> at java.util.ArrayList.get(ArrayList.java:411)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter$RexVisitor.visitInputRef(ASTConverter.java:395)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter$RexVisitor.visitInputRef(ASTConverter.java:372)
> at org.apache.calcite.rex.RexInputRef.accept(RexInputRef.java:112)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter$RexVisitor.visitCall(ASTConverter.java:543)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter$RexVisitor.visitCall(ASTConverter.java:372)
> at org.apache.calcite.rex.RexCall.accept(RexCall.java:107)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter$RexVisitor.visitCall(ASTConverter.java:543)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter$RexVisitor.visitCall(ASTConverter.java:372)
> at org.apache.calcite.rex.RexCall.accept(RexCall.java:107)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter.convertOBToASTNode(ASTConverter.java:252)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter.convert(ASTConverter.java:208)
> at
> org.apache.hadoop.hive.ql.optimizer.calcite.translator.ASTConverter.convert(ASTConverter.java:98)
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.getOptimizedAST(CalcitePlanner.java:607)
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.genOPTree(CalcitePlanner.java:239)
> at
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:10003)
> at
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:202)
> at
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:224)
> at
> org.apache.hadoop.hive.ql.parse.ExplainSemanticAnalyzer.analyzeInternal(ExplainSemanticAnalyzer.java:74)
> at
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:224)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:424)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:308)
> at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1122)
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1170)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1059)
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1049)
> at
> org
[jira] [Commented] (HIVE-13958) hive.strict.checks.type.safety should apply to decimals, as well as IN... and BETWEEN... ops
[ https://issues.apache.org/jira/browse/HIVE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321948#comment-15321948 ] Takuma Wakamori commented on HIVE-13958: Hi, [~sershe]. Could you please assign me to the assignee of this issue? I will try to fix it. Thanks! > hive.strict.checks.type.safety should apply to decimals, as well as IN... and > BETWEEN... ops > > > Key: HIVE-13958 > URL: https://issues.apache.org/jira/browse/HIVE-13958 > Project: Hive > Issue Type: Bug >Reporter: Sergey Shelukhin > > String to decimal auto-casts should be prohibited for compares -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-13889) HiveServer2 shows stack trace when parsing invalid inputs
[
https://issues.apache.org/jira/browse/HIVE-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309001#comment-15309001
]
Takuma Wakamori commented on HIVE-13889:
[~jcamachorodriguez]
Thank you for pointing it out.
To be honest, I misread 'clone' as 'close'. sorry...
> HiveServer2 shows stack trace when parsing invalid inputs
> -
>
> Key: HIVE-13889
> URL: https://issues.apache.org/jira/browse/HIVE-13889
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
>Affects Versions: 2.1.0
>Reporter: Takuma Wakamori
>Priority: Trivial
>
> HiveServer2 shows stack trace when parsing invalid syntax.
> How to reproduce:
> {code}
> Input:
> hostA$ hiveserver2
> hostB$ beeline -u jdbc:hive2://localhost:1 -n user -p pass -e "invalid
> syntax;"
> Output:
> hostA$ NoViableAltException(26@[])
>
> [0/1248]
> at
> org.apache.hadoop.hive.ql.parse.HiveParser.statement(HiveParser.java:1108)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:204)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:444)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:319)
> at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1199)
> at
> org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1186)
> at
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:146)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:218)
> ...
> FAILED: ParseException line 1:0 cannot recognize input near 'invalid'
> 'syntax' ''
> hostB$ Error: Error while compiling statement: FAILED: ParseException line
> 1:0 cannot recognize input near 'invalid' 'syntax' ''
> (state=42000,code=4)
> {code}
> This issue is related to the post of Hive developer mailing list:
> http://mail-archives.apache.org/mod_mbox/hive-dev/201604.mbox/%3CCAOLfT9AaKZ8Nt77QnvrNcxWrQ_1htaj9C0UOsnN5HheoTzM6DQ%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-13889) HiveServer2 shows stack trace when parsing invalid inputs
[
https://issues.apache.org/jira/browse/HIVE-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takuma Wakamori updated HIVE-13889:
---
Summary: HiveServer2 shows stack trace when parsing invalid inputs (was:
It is resolved in latest commit of master and branch-2.1.)
> HiveServer2 shows stack trace when parsing invalid inputs
> -
>
> Key: HIVE-13889
> URL: https://issues.apache.org/jira/browse/HIVE-13889
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
>Reporter: Takuma Wakamori
>Assignee: Takuma Wakamori
>Priority: Trivial
>
> HiveServer2 shows stack trace when parsing invalid syntax.
> How to reproduce:
> {code}
> Input:
> hostA$ hiveserver2
> hostB$ beeline -u jdbc:hive2://localhost:1 -n user -p pass -e "invalid
> syntax;"
> Output:
> hostA$ NoViableAltException(26@[])
>
> [0/1248]
> at
> org.apache.hadoop.hive.ql.parse.HiveParser.statement(HiveParser.java:1108)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:204)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:444)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:319)
> at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1199)
> at
> org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1186)
> at
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:146)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:218)
> ...
> FAILED: ParseException line 1:0 cannot recognize input near 'invalid'
> 'syntax' ''
> hostB$ Error: Error while compiling statement: FAILED: ParseException line
> 1:0 cannot recognize input near 'invalid' 'syntax' ''
> (state=42000,code=4)
> {code}
> This issue is related to the post of Hive developer mailing list:
> http://mail-archives.apache.org/mod_mbox/hive-dev/201604.mbox/%3CCAOLfT9AaKZ8Nt77QnvrNcxWrQ_1htaj9C0UOsnN5HheoTzM6DQ%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-13635) HiveServer2 shows stack trace when parsing invalid inputs
[
https://issues.apache.org/jira/browse/HIVE-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305831#comment-15305831
]
Takuma Wakamori commented on HIVE-13635:
I checked this issue by using the binaries built from latest commits of master
(58d82036) and branch-2.1 (9dd70f0d), and found that the issue has been
resolved in both branches. Thanks!
> HiveServer2 shows stack trace when parsing invalid inputs
> -
>
> Key: HIVE-13635
> URL: https://issues.apache.org/jira/browse/HIVE-13635
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
>Reporter: Takuma Wakamori
>Assignee: Takuma Wakamori
>Priority: Trivial
> Attachments: HIVE-13635.1.patch
>
>
> HiveServer2 shows stack trace when parsing invalid syntax.
> How to reproduce:
> {code}
> Input:
> hostA$ hiveserver2
> hostB$ beeline -u jdbc:hive2://localhost:1 -n user -p pass -e "invalid
> syntax;"
> Output:
> hostA$ NoViableAltException(26@[])
>
> [0/1248]
> at
> org.apache.hadoop.hive.ql.parse.HiveParser.statement(HiveParser.java:1108)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:204)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:444)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:319)
> at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1199)
> at
> org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1186)
> at
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:146)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:218)
> ...
> FAILED: ParseException line 1:0 cannot recognize input near 'invalid'
> 'syntax' ''
> hostB$ Error: Error while compiling statement: FAILED: ParseException line
> 1:0 cannot recognize input near 'invalid' 'syntax' ''
> (state=42000,code=4)
> {code}
> This issue is related to the post of Hive developer mailing list:
> http://mail-archives.apache.org/mod_mbox/hive-dev/201604.mbox/%3CCAOLfT9AaKZ8Nt77QnvrNcxWrQ_1htaj9C0UOsnN5HheoTzM6DQ%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-13642) Update GUESS_FIELDS option in .reviewboardrc to support current version of RBTools.
[
https://issues.apache.org/jira/browse/HIVE-13642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takuma Wakamori updated HIVE-13642:
---
Attachment: HIVE-13642.1.patch
> Update GUESS_FIELDS option in .reviewboardrc to support current version of
> RBTools.
> ---
>
> Key: HIVE-13642
> URL: https://issues.apache.org/jira/browse/HIVE-13642
> Project: Hive
> Issue Type: Bug
>Reporter: Takuma Wakamori
>Assignee: Takuma Wakamori
>Priority: Trivial
> Attachments: HIVE-13642.1.patch
>
>
> According to the instruction of using [Review
> Board|https://cwiki.apache.org/confluence/display/Hive/Review+Board], we can
> create a review request by running the following command:
> {code}
> $ rbt post
> {code}
> However, if we use current version of RBTools (0.7.6), above command doesn't
> work because the values accepted to the option "--guess-fields" was updated
> since 0.6.
> {code}
> $ rbt --version
> RBTools 0.7.6
> $ rbt post
> ERROR: Invalid value "true" for argument "--guess-fields"
> {code}
> It is better to update the value of GUESS_FIELDS option in .reviewboardrc to
> avoid this error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-13635) HiveServer2 shows stack trace when parsing invalid inputs
[
https://issues.apache.org/jira/browse/HIVE-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takuma Wakamori updated HIVE-13635:
---
Attachment: HIVE-13635.1.patch
> HiveServer2 shows stack trace when parsing invalid inputs
> -
>
> Key: HIVE-13635
> URL: https://issues.apache.org/jira/browse/HIVE-13635
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
>Reporter: Takuma Wakamori
>Assignee: Takuma Wakamori
>Priority: Trivial
> Attachments: HIVE-13635.1.patch
>
>
> HiveServer2 shows stack trace when parsing invalid syntax.
> How to reproduce:
> {code}
> Input:
> hostA$ hiveserver2
> hostB$ beeline -u jdbc:hive2://localhost:1 -n user -p pass -e "invalid
> syntax;"
> Output:
> hostA$ NoViableAltException(26@[])
>
> [0/1248]
> at
> org.apache.hadoop.hive.ql.parse.HiveParser.statement(HiveParser.java:1108)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:204)
> at
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:166)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:444)
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:319)
> at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:1199)
> at
> org.apache.hadoop.hive.ql.Driver.compileAndRespond(Driver.java:1186)
> at
> org.apache.hive.service.cli.operation.SQLOperation.prepare(SQLOperation.java:146)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:218)
> ...
> FAILED: ParseException line 1:0 cannot recognize input near 'invalid'
> 'syntax' ''
> hostB$ Error: Error while compiling statement: FAILED: ParseException line
> 1:0 cannot recognize input near 'invalid' 'syntax' ''
> (state=42000,code=4)
> {code}
> This issue is related to the post of Hive developer mailing list:
> http://mail-archives.apache.org/mod_mbox/hive-dev/201604.mbox/%3CCAOLfT9AaKZ8Nt77QnvrNcxWrQ_1htaj9C0UOsnN5HheoTzM6DQ%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-13239) "java.lang.OutOfMemoryError: unable to create new native thread" occurs at Hive on Tez
[
https://issues.apache.org/jira/browse/HIVE-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255665#comment-15255665
]
Takuma Wakamori commented on HIVE-13239:
Does this issue already resolved?
([~wyukawa] mentioned at HIVE-13273 that the OOM Error does not occur after
upgrading to HDP2.4.)
If not, I'll address this issue.
I'm trying to fix bugs around hiveserver2.
Thanks.
> "java.lang.OutOfMemoryError: unable to create new native thread" occurs at
> Hive on Tez
> --
>
> Key: HIVE-13239
> URL: https://issues.apache.org/jira/browse/HIVE-13239
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Environment: HDP2.3.4
> JDK1.8
> CentOS 6
>Reporter: Wataru Yukawa
>
> "ps -L $(pgrep -f hiveserver2) | wc -l" is more than 15,000
> HiveServer2 memory leak occurs.
> hive query
> {code}
> FROM hoge_tmp
> INSERT INTO TABLE hoge PARTITION (...)
>SELECT ... WHERE ...
> {code}
> stacktrace
> {code}
> org.apache.hive.service.cli.HiveSQLException: Error while processing
> statement: FAILED: Execution Error, return code -101 from
> org.apache.hadoop.hive.ql.exec.tez.TezTask. unable to create new native thread
> at
> org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:315)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:156)
> at
> org.apache.hive.service.cli.operation.SQLOperation.runInternal(SQLOperation.java:183)
> at
> org.apache.hive.service.cli.operation.Operation.run(Operation.java:257)
> at
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatementInternal(HiveSessionImpl.java:410)
> at
> org.apache.hive.service.cli.session.HiveSessionImpl.executeStatement(HiveSessionImpl.java:391)
> at
> org.apache.hive.service.cli.CLIService.executeStatement(CLIService.java:261)
> at
> org.apache.hive.service.cli.thrift.ThriftCLIService.ExecuteStatement(ThriftCLIService.java:486)
> at
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1313)
> at
> org.apache.hive.service.cli.thrift.TCLIService$Processor$ExecuteStatement.getResult(TCLIService.java:1298)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:285)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:714)
> at
> org.apache.hadoop.hdfs.DFSOutputStream.start(DFSOutputStream.java:2238)
> at
> org.apache.hadoop.hdfs.DFSOutputStream.newStreamForCreate(DFSOutputStream.java:1753)
> at org.apache.hadoop.hdfs.DFSClient.create(DFSClient.java:1703)
> at org.apache.hadoop.hdfs.DFSClient.create(DFSClient.java:1638)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$7.doCall(DistributedFileSystem.java:448)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$7.doCall(DistributedFileSystem.java:444)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:444)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:387)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:909)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:890)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:787)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:776)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:577)
> at
> org.apache.tez.common.TezCommonUtils.createFileForAM(TezCommonUtils.java:310)
> at
> org.apache.tez.client.TezClientUtils.createApplicationSubmissionContext(TezClientUtils.java:559)
> at org.apache.tez.client.TezClient.start(TezClient.java:395)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezSessionState.open(TezSessionState.java:196)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezTask.updateSession(TezTask.java:271)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezTask.execu
[jira] [Updated] (HIVE-13176) OutOfMemoryError : GC overhead limit exceeded
[ https://issues.apache.org/jira/browse/HIVE-13176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuma Wakamori updated HIVE-13176: --- Description: KDetected leaks while testing hiveserver2 concurrency setup with LLAP. 2016-02-26T12:50:58,131 ERROR [HiveServer2-Background-Pool: Thread-311030]: operation.Operation (SQLOperation.java:run(230)) - Error running hive query: org.apache.hive.service.cli.HiveSQLException: Error while processing statement: FAILED: Execution Error, return code -101 from org.apache.hadoop.hive.ql.exec.StatsTask. GC overhead limit exceeded at org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:333) ~[hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:177) ~[hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at org.apache.hive.service.cli.operation.SQLOperation.access$100(SQLOperation.java:73) ~[hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at org.apache.hive.service.cli.operation.SQLOperation$1$1.run(SQLOperation.java:227) [hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_45] at javax.security.auth.Subject.doAs(Subject.java:422) [?:1.8.0_45] at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657) [hadoop-common-2.7.1.2.3.5.1-36.jar:?] at org.apache.hive.service.cli.operation.SQLOperation$1.run(SQLOperation.java:239) [hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45] was: Detected leaks while testing hiveserver2 concurrency setup with LLAP. 2016-02-26T12:50:58,131 ERROR [HiveServer2-Background-Pool: Thread-311030]: operation.Operation (SQLOperation.java:run(230)) - Error running hive query: org.apache.hive.service.cli.HiveSQLException: Error while processing statement: FAILED: Execution Error, return code -101 from org.apache.hadoop.hive.ql.exec.StatsTask. GC overhead limit exceeded at org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:333) ~[hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:177) ~[hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at org.apache.hive.service.cli.operation.SQLOperation.access$100(SQLOperation.java:73) ~[hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at org.apache.hive.service.cli.operation.SQLOperation$1$1.run(SQLOperation.java:227) [hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_45] at javax.security.auth.Subject.doAs(Subject.java:422) [?:1.8.0_45] at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657) [hadoop-common-2.7.1.2.3.5.1-36.jar:?] at org.apache.hive.service.cli.operation.SQLOperation$1.run(SQLOperation.java:239) [hive-jdbc-2.0.0.2.3.5.1-36-standalone.jar:2.0.0.2.3.5.1-36] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_45] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45] > OutOfMemoryError : GC overhead limit exceeded > -- > > Key: HIVE-13176 > URL: https://issues.apache.org/jira/browse/HIVE-13176 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Kavan Suresh >Assignee: Siddharth Seth > Attachments: dataNucleus.png, fs.png, shutdownhook.png > > > KDetected leaks while testing hiveserver2 concurrency setup with LLAP. > 2016-02-26T12:50:58,131 ERROR [HiveServer2-Background-Pool: Thread-311030]: > operation.Operation (SQLOperation.java:run(230)) - Error running hive query: > org.apache.hive.service.cli.HiveSQLException: Error while processing > statement: FAILED: Execution Error, return code -101 from > org.apache.hadoop.hive.ql.exec.StatsTask. GC over
