[jira] [Commented] (HIVE-21758) DBInstall tests broken on master and branch-3.1

2019-07-11 Thread Laszlo Bodor (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882693#comment-16882693
 ] 

Laszlo Bodor commented on HIVE-21758:
-

"For SqlServer the cause of the failures is not immediately clear."

[~aditya-shah]: for later reference, it seems like mssql docker has a min 
memory requirement, setting up docker according to that solved the problem for 
me

{code}
docker logs 1497061a4ec7
sqlservr: This program requires a machine with at least 3250 megabytes of memory
{code}

> DBInstall tests broken on master and branch-3.1
> ---
>
> Key: HIVE-21758
> URL: https://issues.apache.org/jira/browse/HIVE-21758
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore, Tests
>Affects Versions: 3.1.1
>Reporter: Alan Gates
>Assignee: Aditya Shah
>Priority: Major
> Fix For: 4.0.0, 3.1.2
>
> Attachments: HIVE-21758.patch
>
>
> The Oracle and SqlServer install and upgrade tests in standalone-metastore 
> fail in master and branch-3.1.  In the Oracle case it appears the docker 
> container that was used no longer exists.  For SqlServer the cause of the 
> failures is not immediately clear.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21984) Clean up TruncateTable operation and desc

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21984:
--
Attachment: HIVE-21984.01.patch

> Clean up TruncateTable operation and desc
> -
>
> Key: HIVE-21984
> URL: https://issues.apache.org/jira/browse/HIVE-21984
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21984.01.patch, HIVE-21984.01.patch
>
>
> TruncateTableDesc is not immutable, should be fixed. The DDLSemanticAnalyzer 
> has a long and complicated function for parsing truncate commands, should e 
> cut to pieces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21977) Clean up DescTableOperation

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21977:
--
Attachment: (was: HIVE-21977.02.patch)

> Clean up DescTableOperation
> ---
>
> Key: HIVE-21977
> URL: https://issues.apache.org/jira/browse/HIVE-21977
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21977.01.patch, HIVE-21977.02.patch
>
>
> DescTable operation is messy, with some unclean solutions. It should be 
> refactored.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21920) Extract command authorisation from the Driver

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21920:
--
Attachment: (was: HIVE-21920.02.patch)

> Extract command authorisation from the Driver
> -
>
> Key: HIVE-21920
> URL: https://issues.apache.org/jira/browse/HIVE-21920
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21920.01.patch, HIVE-21920.02.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are ~400 lines of command authorisation in the Driver class, which are 
> also used by ExplainTask. Extract them into a separate package under  
> org.apache.hadoop.hive.ql.security.authorization.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21920) Extract command authorisation from the Driver

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21920:
--
Attachment: HIVE-21920.02.patch

> Extract command authorisation from the Driver
> -
>
> Key: HIVE-21920
> URL: https://issues.apache.org/jira/browse/HIVE-21920
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21920.01.patch, HIVE-21920.02.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are ~400 lines of command authorisation in the Driver class, which are 
> also used by ExplainTask. Extract them into a separate package under  
> org.apache.hadoop.hive.ql.security.authorization.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21983) Cut DropTableDesc/Operation to drop table, view and materialized view

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21983:
--
Attachment: HIVE-21983.01.patch

> Cut DropTableDesc/Operation to drop table, view and materialized view
> -
>
> Key: HIVE-21983
> URL: https://issues.apache.org/jira/browse/HIVE-21983
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21983.01.patch, HIVE-21983.01.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21977) Clean up DescTableOperation

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21977:
--
Attachment: HIVE-21977.02.patch

> Clean up DescTableOperation
> ---
>
> Key: HIVE-21977
> URL: https://issues.apache.org/jira/browse/HIVE-21977
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21977.01.patch, HIVE-21977.02.patch
>
>
> DescTable operation is messy, with some unclean solutions. It should be 
> refactored.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21984) Clean up TruncateTable operation and desc

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21984:
--
Attachment: (was: HIVE-21984.01.patch)

> Clean up TruncateTable operation and desc
> -
>
> Key: HIVE-21984
> URL: https://issues.apache.org/jira/browse/HIVE-21984
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21984.01.patch
>
>
> TruncateTableDesc is not immutable, should be fixed. The DDLSemanticAnalyzer 
> has a long and complicated function for parsing truncate commands, should e 
> cut to pieces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21983) Cut DropTableDesc/Operation to drop table, view and materialized view

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21983:
--
Attachment: (was: HIVE-21983.01.patch)

> Cut DropTableDesc/Operation to drop table, view and materialized view
> -
>
> Key: HIVE-21983
> URL: https://issues.apache.org/jira/browse/HIVE-21983
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21983.01.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21963) TransactionalValidationListener.validateTableStructure should check the partition directories in the case of partitioned tables

2019-07-11 Thread Vaibhav Gumashta (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882710#comment-16882710
 ] 

Vaibhav Gumashta commented on HIVE-21963:
-

+1

> TransactionalValidationListener.validateTableStructure should check the 
> partition directories in the case of partitioned tables
> ---
>
> Key: HIVE-21963
> URL: https://issues.apache.org/jira/browse/HIVE-21963
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Reporter: Jason Dere
>Assignee: Jason Dere
>Priority: Major
> Attachments: HIVE-21963.1.patch
>
>
> The transactional validation check is checking just the base table directory, 
> but for partitioned tables this should be checking the partitioned 
> directories (some of which may not even be in the base table directory).



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21164) ACID: explore how we can avoid a move step during inserts/compaction

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882714#comment-16882714
 ] 

Hive QA commented on HIVE-21164:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
46s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 6s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  3m 
53s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
43s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs 
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
22s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
26s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  2m 
 9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
49s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
48s{color} | {color:red} ql: The patch generated 19 new + 1191 unchanged - 8 
fixed = 1210 total (was 1199) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
16s{color} | {color:red} itests/hive-unit: The patch generated 1 new + 34 
unchanged - 1 fixed = 35 total (was 35) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch has 27 line(s) that end in whitespace. Use 
git apply --whitespace=fix <>. Refer 
https://git-scm.com/docs/git-apply {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
23s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
13s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 30m 30s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17974/dev-support/hive-personality.sh
 |
| git revision | master / 634d93d |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17974/yetus/diff-checkstyle-ql.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17974/yetus/diff-checkstyle-itests_hive-unit.txt
 |
| whitespace | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17974/yetus/whitespace-eol.txt
 |
| modules | C: ql itests/hive-unit U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17974/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> ACID: explore how we can avoid a move step during inserts/compaction
> 
>
> Key: HIVE-21164
> URL: https://issues.apache.org/jira/browse/HIVE-21164
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Affects Versions: 3.1.1
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-21164.1.patch, HIVE-21164.2.patch, 
> HIVE-21164.3.patch, HIVE

[jira] [Updated] (HIVE-21923) Vectorized MapJoin may miss results when only the join key is selected

2019-07-11 Thread Zoltan Haindrich (JIRA)


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

Zoltan Haindrich updated HIVE-21923:

Attachment: HIVE-21923.07.patch

> Vectorized MapJoin may miss results when only the join key is selected
> --
>
> Key: HIVE-21923
> URL: https://issues.apache.org/jira/browse/HIVE-21923
> Project: Hive
>  Issue Type: Bug
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21923.01.patch, HIVE-21923.02.patch, 
> HIVE-21923.03.patch, HIVE-21923.04.patch, HIVE-21923.05.patch, 
> HIVE-21923.06.patch, HIVE-21923.06.patch, HIVE-21923.07.patch
>
>
> HIVE-21189 have introduced some resultset changes
> in ql/src/test/results/clientpositive/llap/hybridgrace_hashjoin_2.q.out
> https://github.com/apache/hive/commit/5799398450c17d06e8ef144ce835a8524f5abec9#diff-56b3ab96b6c90fdbebe2c4f84e8595afL500



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21980) Parsing time can be high in case of deeply nested subqueries

2019-07-11 Thread Zoltan Haindrich (JIRA)


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

Zoltan Haindrich updated HIVE-21980:

Attachment: HIVE-21980.01.patch

> Parsing time can be high in case of deeply nested subqueries
> 
>
> Key: HIVE-21980
> URL: https://issues.apache.org/jira/browse/HIVE-21980
> Project: Hive
>  Issue Type: Improvement
>  Components: Parser
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21980.01.patch, HIVE-21980.01.patch
>
>
> for queries which are recursively doing:
> {code}
> SELECT ...
> FROM (SELECT ...
>  FROM ( [...]
>  ) JOIN
> (SELECT ...
> FROM ( [...] )
> JOIN ( [...]
> )
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21980) Parsing time can be high in case of deeply nested subqueries

2019-07-11 Thread Zoltan Haindrich (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882720#comment-16882720
 ] 

Zoltan Haindrich commented on HIVE-21980:
-

[~vgarg] Could you please take a look?

> Parsing time can be high in case of deeply nested subqueries
> 
>
> Key: HIVE-21980
> URL: https://issues.apache.org/jira/browse/HIVE-21980
> Project: Hive
>  Issue Type: Improvement
>  Components: Parser
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21980.01.patch, HIVE-21980.01.patch
>
>
> for queries which are recursively doing:
> {code}
> SELECT ...
> FROM (SELECT ...
>  FROM ( [...]
>  ) JOIN
> (SELECT ...
> FROM ( [...] )
> JOIN ( [...]
> )
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21164) ACID: explore how we can avoid a move step during inserts/compaction

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882747#comment-16882747
 ] 

Hive QA commented on HIVE-21164:




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

{color:green}SUCCESS:{color} +1 due to 4 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 18 failed/errored test(s), 16647 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[acid_subquery] 
(batchId=43)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[create_transactional_full_acid]
 (batchId=83)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[mm_all] (batchId=74)
org.apache.hadoop.hive.cli.TestEncryptedHDFSCliDriver.testCliDriver[encryption_insert_partition_dynamic]
 (batchId=190)
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[acid_bucket_pruning]
 (batchId=155)
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[mm_all] 
(batchId=157)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[acid_no_buckets]
 (batchId=179)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[bucket_num_reducers_acid2]
 (batchId=173)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[bucket_num_reducers_acid]
 (batchId=175)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[insert_overwrite]
 (batchId=165)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[schema_evol_orc_acidvec_table]
 (batchId=185)
org.apache.hadoop.hive.ql.TestAcidOnTez.testAcidInsertWithRemoveUnion 
(batchId=243)
org.apache.hadoop.hive.ql.TestTxnCommands.testMoreBucketsThanReducers 
(batchId=341)
org.apache.hadoop.hive.ql.TestTxnCommandsWithSplitUpdateAndVectorization.testMoreBucketsThanReducers
 (batchId=324)
org.apache.hadoop.hive.ql.TestTxnNoBuckets.testInsertToAcidWithUnionRemove 
(batchId=322)
org.apache.hadoop.hive.ql.TestTxnNoBucketsVectorized.testInsertToAcidWithUnionRemove
 (batchId=324)
org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.testWriteSetTracking7 
(batchId=340)
org.apache.hadoop.hive.ql.parse.TestReplicationScenariosIncrementalLoadAcidTables.testAcidTableIncrementalReplication
 (batchId=263)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17974/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17974/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17974/

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

This message is automatically generated.

ATTACHMENT ID: 12974360 - PreCommit-HIVE-Build

> ACID: explore how we can avoid a move step during inserts/compaction
> 
>
> Key: HIVE-21164
> URL: https://issues.apache.org/jira/browse/HIVE-21164
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Affects Versions: 3.1.1
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-21164.1.patch, HIVE-21164.2.patch, 
> HIVE-21164.3.patch, HIVE-21164.4.patch, HIVE-21164.5.patch, 
> HIVE-21164.6.patch, HIVE-21164.7.patch
>
>
> Currently, we write compacted data to a temporary location and then move the 
> files to a final location, which is an expensive operation on some cloud file 
> systems. Since HIVE-20823 is already in, it can control the visibility of 
> compacted data for the readers. Therefore, we can perhaps avoid writing data 
> to a temporary location and directly write compacted data to the intended 
> final path.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21977) Clean up DescTableOperation

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882772#comment-16882772
 ] 

Hive QA commented on HIVE-21977:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
1s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
41s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
4s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
58s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m  
7s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
43s{color} | {color:red} ql: The patch generated 11 new + 399 unchanged - 7 
fixed = 410 total (was 406) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
0s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
14s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 25m  1s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17975/dev-support/hive-personality.sh
 |
| git revision | master / 634d93d |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17975/yetus/diff-checkstyle-ql.txt
 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17975/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Clean up DescTableOperation
> ---
>
> Key: HIVE-21977
> URL: https://issues.apache.org/jira/browse/HIVE-21977
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21977.01.patch, HIVE-21977.02.patch
>
>
> DescTable operation is messy, with some unclean solutions. It should be 
> refactored.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21977) Clean up DescTableOperation

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21977:
--
Attachment: (was: HIVE-21977.03.patch)

> Clean up DescTableOperation
> ---
>
> Key: HIVE-21977
> URL: https://issues.apache.org/jira/browse/HIVE-21977
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21977.01.patch, HIVE-21977.02.patch
>
>
> DescTable operation is messy, with some unclean solutions. It should be 
> refactored.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21977) Clean up DescTableOperation

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21977:
--
Attachment: HIVE-21977.03.patch

> Clean up DescTableOperation
> ---
>
> Key: HIVE-21977
> URL: https://issues.apache.org/jira/browse/HIVE-21977
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21977.01.patch, HIVE-21977.02.patch
>
>
> DescTable operation is messy, with some unclean solutions. It should be 
> refactored.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21977) Clean up DescTableOperation

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882804#comment-16882804
 ] 

Hive QA commented on HIVE-21977:




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

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 11 failed/errored test(s), 16647 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[alterColumnStats] 
(batchId=61)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[alter_table_column_stats]
 (batchId=71)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[autoColumnStats_10] 
(batchId=81)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[column_names_with_leading_and_trailing_spaces]
 (batchId=26)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[compustat_avro] 
(batchId=98)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[describe_syntax] 
(batchId=87)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[display_colstats_tbllvl] 
(batchId=4)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[inputddl6] (batchId=57)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[temp_table_display_colstats_tbllvl]
 (batchId=86)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[autoColumnStats_10]
 (batchId=181)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[column_names_with_leading_and_trailing_spaces]
 (batchId=166)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17975/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17975/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17975/

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

This message is automatically generated.

ATTACHMENT ID: 12974364 - PreCommit-HIVE-Build

> Clean up DescTableOperation
> ---
>
> Key: HIVE-21977
> URL: https://issues.apache.org/jira/browse/HIVE-21977
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21977.01.patch, HIVE-21977.02.patch
>
>
> DescTable operation is messy, with some unclean solutions. It should be 
> refactored.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21983) Cut DropTableDesc/Operation to drop table, view and materialized view

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882834#comment-16882834
 ] 

Hive QA commented on HIVE-21983:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  1m 
45s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
58s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
58s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
36s{color} | {color:blue} common in master has 62 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
2s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
14s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
26s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
25s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
16s{color} | {color:red} common: The patch generated 1 new + 437 unchanged - 1 
fixed = 438 total (was 438) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
42s{color} | {color:red} ql: The patch generated 5 new + 293 unchanged - 2 
fixed = 298 total (was 295) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
12s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
13s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 28m 29s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17976/dev-support/hive-personality.sh
 |
| git revision | master / 634d93d |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17976/yetus/diff-checkstyle-common.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17976/yetus/diff-checkstyle-ql.txt
 |
| modules | C: common ql U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17976/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Cut DropTableDesc/Operation to drop table, view and materialized view
> -
>
> Key: HIVE-21983
> URL: https://issues.apache.org/jira/browse/HIVE-21983
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21983.01.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21983) Cut DropTableDesc/Operation to drop table, view and materialized view

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882870#comment-16882870
 ] 

Hive QA commented on HIVE-21983:




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

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 16647 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[drop_table_failure2]
 (batchId=100)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[drop_view_failure1]
 (batchId=101)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[materialized_view_drop2]
 (batchId=101)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[materialized_view_drop]
 (batchId=100)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17976/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17976/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17976/

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

This message is automatically generated.

ATTACHMENT ID: 12974366 - PreCommit-HIVE-Build

> Cut DropTableDesc/Operation to drop table, view and materialized view
> -
>
> Key: HIVE-21983
> URL: https://issues.apache.org/jira/browse/HIVE-21983
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21983.01.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21948:
--
Attachment: HIVE-21948.4.patch

> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21948:
--
Status: Patch Available  (was: Open)

> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21948:
--
Status: Open  (was: Patch Available)

> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21984) Clean up TruncateTable operation and desc

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882886#comment-16882886
 ] 

Hive QA commented on HIVE-21984:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
1s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
41s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  3m 
57s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
2s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m  
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
40s{color} | {color:green} ql: The patch generated 0 new + 208 unchanged - 1 
fixed = 208 total (was 209) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git 
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply 
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
4s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
13s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 26s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17977/dev-support/hive-personality.sh
 |
| git revision | master / 634d93d |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| whitespace | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17977/yetus/whitespace-eol.txt
 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17977/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Clean up TruncateTable operation and desc
> -
>
> Key: HIVE-21984
> URL: https://issues.apache.org/jira/browse/HIVE-21984
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21984.01.patch
>
>
> TruncateTableDesc is not immutable, should be fixed. The DDLSemanticAnalyzer 
> has a long and complicated function for parsing truncate commands, should e 
> cut to pieces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21965) Implement parallel processing in HiveStrictManagedMigration

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21965:
--
Status: Open  (was: Patch Available)

> Implement parallel processing in HiveStrictManagedMigration
> ---
>
> Key: HIVE-21965
> URL: https://issues.apache.org/jira/browse/HIVE-21965
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21965.1.patch, HIVE-21965.2.patch, 
> HIVE-21965.3.patch, HIVE-21965.4.patch
>
>
> This process, kicked off from Ambari can take many days for systems with 
> 1000's of tables. The process needs to support parallel execution as it 
> iterates through the Databases and Tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21965) Implement parallel processing in HiveStrictManagedMigration

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21965:
--
Attachment: HIVE-21965.4.patch

> Implement parallel processing in HiveStrictManagedMigration
> ---
>
> Key: HIVE-21965
> URL: https://issues.apache.org/jira/browse/HIVE-21965
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21965.1.patch, HIVE-21965.2.patch, 
> HIVE-21965.3.patch, HIVE-21965.4.patch
>
>
> This process, kicked off from Ambari can take many days for systems with 
> 1000's of tables. The process needs to support parallel execution as it 
> iterates through the Databases and Tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21965) Implement parallel processing in HiveStrictManagedMigration

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21965:
--
Status: Patch Available  (was: Open)

> Implement parallel processing in HiveStrictManagedMigration
> ---
>
> Key: HIVE-21965
> URL: https://issues.apache.org/jira/browse/HIVE-21965
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21965.1.patch, HIVE-21965.2.patch, 
> HIVE-21965.3.patch, HIVE-21965.4.patch
>
>
> This process, kicked off from Ambari can take many days for systems with 
> 1000's of tables. The process needs to support parallel execution as it 
> iterates through the Databases and Tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21979) TestReplication tests time out regularily

2019-07-11 Thread Zoltan Haindrich (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882893#comment-16882893
 ] 

Zoltan Haindrich commented on HIVE-21979:
-

https://builds.apache.org/job/PreCommit-HIVE-Build/lastCompletedBuild/testReport/org.apache.hadoop.hive.ql.parse/

> TestReplication tests time out regularily
> -
>
> Key: HIVE-21979
> URL: https://issues.apache.org/jira/browse/HIVE-21979
> Project: Hive
>  Issue Type: Improvement
>  Components: Test
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
>
> I think we should add TestTableLevelReplicationScenarios and friends to be 
> executed in isolation
> from a recent ptest execution:
> {code}
> [INFO] Running org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 150.413 s - in org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Running 
> org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.084 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Running org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.062 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Running org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.568 
> s - in org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 348.769 s - in org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.089 
> s - in org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,044.666 s - in 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 225.734 s - in 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplAcrossInstancesWithJsonMessageFormat
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21979) TestReplication tests time out regularily

2019-07-11 Thread Zoltan Haindrich (JIRA)


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

Zoltan Haindrich updated HIVE-21979:

Attachment: HIVE-21979.01.patch

> TestReplication tests time out regularily
> -
>
> Key: HIVE-21979
> URL: https://issues.apache.org/jira/browse/HIVE-21979
> Project: Hive
>  Issue Type: Improvement
>  Components: Test
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21979.01.patch
>
>
> I think we should add TestTableLevelReplicationScenarios and friends to be 
> executed in isolation
> from a recent ptest execution:
> {code}
> [INFO] Running org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 150.413 s - in org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Running 
> org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.084 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Running org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.062 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Running org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.568 
> s - in org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 348.769 s - in org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.089 
> s - in org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,044.666 s - in 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 225.734 s - in 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplAcrossInstancesWithJsonMessageFormat
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21979) TestReplication tests time out regularily

2019-07-11 Thread Zoltan Haindrich (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882907#comment-16882907
 ] 

Zoltan Haindrich commented on HIVE-21979:
-

[~pvary] could you please take a look?

> TestReplication tests time out regularily
> -
>
> Key: HIVE-21979
> URL: https://issues.apache.org/jira/browse/HIVE-21979
> Project: Hive
>  Issue Type: Improvement
>  Components: Test
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21979.01.patch
>
>
> I think we should add TestTableLevelReplicationScenarios and friends to be 
> executed in isolation
> from a recent ptest execution:
> {code}
> [INFO] Running org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 150.413 s - in org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Running 
> org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.084 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Running org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.062 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Running org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.568 
> s - in org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 348.769 s - in org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.089 
> s - in org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,044.666 s - in 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 225.734 s - in 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplAcrossInstancesWithJsonMessageFormat
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21578) Introduce SQL:2016 formats FM, FX, and nested strings

2019-07-11 Thread Karen Coppage (JIRA)


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

Karen Coppage updated HIVE-21578:
-
Status: Open  (was: Patch Available)

> Introduce SQL:2016 formats FM, FX, and nested strings
> -
>
> Key: HIVE-21578
> URL: https://issues.apache.org/jira/browse/HIVE-21578
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21578.01.patch, HIVE-21578.02.patch, 
> HIVE-21578.02.patch, HIVE-21578.03.patch, HIVE-21578.04.patch, 
> HIVE-21578.04.patch
>
>
> Enable Hive to parse the following datetime formats when any combination or 
> subset of these or previously implemented formats is provided in one string. 
>  * "text" (nested strings)
>  * FM
>  * FX
> [Definitions 
> here|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21578) Introduce SQL:2016 formats FM, FX, and nested strings

2019-07-11 Thread Karen Coppage (JIRA)


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

Karen Coppage updated HIVE-21578:
-
Attachment: HIVE-21578.05.patch
Status: Patch Available  (was: Open)

> Introduce SQL:2016 formats FM, FX, and nested strings
> -
>
> Key: HIVE-21578
> URL: https://issues.apache.org/jira/browse/HIVE-21578
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21578.01.patch, HIVE-21578.02.patch, 
> HIVE-21578.02.patch, HIVE-21578.03.patch, HIVE-21578.04.patch, 
> HIVE-21578.04.patch, HIVE-21578.05.patch
>
>
> Enable Hive to parse the following datetime formats when any combination or 
> subset of these or previously implemented formats is provided in one string. 
>  * "text" (nested strings)
>  * FM
>  * FX
> [Definitions 
> here|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21984) Clean up TruncateTable operation and desc

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882918#comment-16882918
 ] 

Hive QA commented on HIVE-21984:




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

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16618 tests 
executed
*Failed tests:*
{noformat}
TestReplAcrossInstancesWithJsonMessageFormat - did not produce a TEST-*.xml 
file (likely timed out) (batchId=255)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17977/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17977/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17977/

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

This message is automatically generated.

ATTACHMENT ID: 12974363 - PreCommit-HIVE-Build

> Clean up TruncateTable operation and desc
> -
>
> Key: HIVE-21984
> URL: https://issues.apache.org/jira/browse/HIVE-21984
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21984.01.patch
>
>
> TruncateTableDesc is not immutable, should be fixed. The DDLSemanticAnalyzer 
> has a long and complicated function for parsing truncate commands, should e 
> cut to pieces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21979) TestReplication tests time out regularily

2019-07-11 Thread Peter Vary (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882919#comment-16882919
 ] 

Peter Vary commented on HIVE-21979:
---

+1

> TestReplication tests time out regularily
> -
>
> Key: HIVE-21979
> URL: https://issues.apache.org/jira/browse/HIVE-21979
> Project: Hive
>  Issue Type: Improvement
>  Components: Test
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21979.01.patch
>
>
> I think we should add TestTableLevelReplicationScenarios and friends to be 
> executed in isolation
> from a recent ptest execution:
> {code}
> [INFO] Running org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 150.413 s - in org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Running 
> org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.084 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Running org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.062 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Running org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.568 
> s - in org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 348.769 s - in org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.089 
> s - in org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,044.666 s - in 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 225.734 s - in 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplAcrossInstancesWithJsonMessageFormat
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (HIVE-21979) TestReplication tests time out regularily

2019-07-11 Thread Zoltan Haindrich (JIRA)


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

Zoltan Haindrich resolved HIVE-21979.
-
   Resolution: Fixed
Fix Version/s: 4.0.0

pushed to master. Thank you Peter for taking a look!

> TestReplication tests time out regularily
> -
>
> Key: HIVE-21979
> URL: https://issues.apache.org/jira/browse/HIVE-21979
> Project: Hive
>  Issue Type: Improvement
>  Components: Test
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21979.01.patch
>
>
> I think we should add TestTableLevelReplicationScenarios and friends to be 
> executed in isolation
> from a recent ptest execution:
> {code}
> [INFO] Running org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 150.413 s - in org.apache.hadoop.hive.ql.TestCreateUdfEntities
> [INFO] Running 
> org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.084 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication
> [INFO] Running org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 61.062 
> s - in org.apache.hadoop.hive.ql.txn.compactor.TestCrudCompactorOnTez
> [INFO] Running org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 57.568 
> s - in org.apache.hadoop.hive.ql.TestWarehouseExternalDir
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 348.769 s - in org.apache.hadoop.hive.ql.parse.TestReplicationOfHiveStreaming
> [INFO] Running org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.089 
> s - in org.apache.hadoop.hive.ql.parse.TestExportImport
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 1,044.666 s - in 
> org.apache.hadoop.hive.ql.parse.TestTableLevelReplicationScenarios
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
> 225.734 s - in 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosExternalTables
> [INFO] Running 
> org.apache.hadoop.hive.ql.parse.TestReplAcrossInstancesWithJsonMessageFormat
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21920) Extract command authorisation from the Driver

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882941#comment-16882941
 ] 

Hive QA commented on HIVE-21920:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
27s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
6s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
41s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
6s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
0s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
10s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
41s{color} | {color:red} ql: The patch generated 7 new + 184 unchanged - 4 
fixed = 191 total (was 188) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
13s{color} | {color:green} ql generated 0 new + 2253 unchanged - 2 fixed = 2253 
total (was 2255) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
0s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
15s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 40s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17978/dev-support/hive-personality.sh
 |
| git revision | master / 634d93d |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17978/yetus/diff-checkstyle-ql.txt
 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17978/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Extract command authorisation from the Driver
> -
>
> Key: HIVE-21920
> URL: https://issues.apache.org/jira/browse/HIVE-21920
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21920.01.patch, HIVE-21920.02.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are ~400 lines of command authorisation in the Driver class, which are 
> also used by ExplainTask. Extract them into a separate package under  
> org.apache.hadoop.hive.ql.security.authorization.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Laszlo Bodor (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882961#comment-16882961
 ] 

Laszlo Bodor commented on HIVE-21224:
-

1. found a few minor things in 15.patch, discussed with [~bpusztahazi], 
otherwise +1
2. metastore integration tests pass locally for me too

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.2.patch, 
> HIVE-21224.3.patch, HIVE-21224.4.patch, HIVE-21224.5.patch, 
> HIVE-21224.6.patch, HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21920) Extract command authorisation from the Driver

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882991#comment-16882991
 ] 

Hive QA commented on HIVE-21920:




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

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16618 tests 
executed
*Failed tests:*
{noformat}
TestReplAcrossInstancesWithJsonMessageFormat - did not produce a TEST-*.xml 
file (likely timed out) (batchId=255)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17978/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17978/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17978/

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

This message is automatically generated.

ATTACHMENT ID: 12974365 - PreCommit-HIVE-Build

> Extract command authorisation from the Driver
> -
>
> Key: HIVE-21920
> URL: https://issues.apache.org/jira/browse/HIVE-21920
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21920.01.patch, HIVE-21920.02.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are ~400 lines of command authorisation in the Driver class, which are 
> also used by ExplainTask. Extract them into a separate package under  
> org.apache.hadoop.hive.ql.security.authorization.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Status: Open  (was: Patch Available)

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.2.patch, HIVE-21224.3.patch, HIVE-21224.4.patch, 
> HIVE-21224.5.patch, HIVE-21224.6.patch, HIVE-21224.7.patch, 
> HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Attachment: HIVE-21224.16.patch

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.2.patch, HIVE-21224.3.patch, HIVE-21224.4.patch, 
> HIVE-21224.5.patch, HIVE-21224.6.patch, HIVE-21224.7.patch, 
> HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Status: Patch Available  (was: Open)

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.2.patch, HIVE-21224.3.patch, HIVE-21224.4.patch, 
> HIVE-21224.5.patch, HIVE-21224.6.patch, HIVE-21224.7.patch, 
> HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Zoltan Haindrich (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883036#comment-16883036
 ] 

Zoltan Haindrich commented on HIVE-21224:
-

actually this patch seem to have also found ~46 new testcases; I see that it 
also lost ~3 or so
I'll  commit it - before it gets into some conflict

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.2.patch, HIVE-21224.3.patch, HIVE-21224.4.patch, 
> HIVE-21224.5.patch, HIVE-21224.6.patch, HIVE-21224.7.patch, 
> HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Zoltan Haindrich (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883057#comment-16883057
 ] 

Zoltan Haindrich commented on HIVE-21224:
-

it turned out that the "new testcases" were just appeard because of the 
previous run had some timed out tests...
The 3 missing tests are:
{code}
TestHiveMetastoreTransformer#testCreateTable TestGenericUDFRound#testUdf 
TestObjectInspectorUtils#testBucketHashGeneration
{code}
I was tempted to add the {{@Test}} but for the {{TestGenericUDFRound}} it 
seemed wierd - there was Ignored class... - so might be better handle it 
separaetly; along with the issue [~abstractdog] mentioned 
[~bpusztahazi] could you please open a followup ticket?


> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.2.patch, HIVE-21224.3.patch, HIVE-21224.4.patch, 
> HIVE-21224.5.patch, HIVE-21224.6.patch, HIVE-21224.7.patch, 
> HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21923) Vectorized MapJoin may miss results when only the join key is selected

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883091#comment-16883091
 ] 

Hive QA commented on HIVE-21923:




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

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 16648 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.ql.TestWarehouseExternalDir.org.apache.hadoop.hive.ql.TestWarehouseExternalDir
 (batchId=255)
org.apache.hadoop.hive.ql.TestWarehouseExternalDir.testExternalDefaultPaths 
(batchId=255)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17979/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17979/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17979/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
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: 12974371 - PreCommit-HIVE-Build

> Vectorized MapJoin may miss results when only the join key is selected
> --
>
> Key: HIVE-21923
> URL: https://issues.apache.org/jira/browse/HIVE-21923
> Project: Hive
>  Issue Type: Bug
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21923.01.patch, HIVE-21923.02.patch, 
> HIVE-21923.03.patch, HIVE-21923.04.patch, HIVE-21923.05.patch, 
> HIVE-21923.06.patch, HIVE-21923.06.patch, HIVE-21923.07.patch
>
>
> HIVE-21189 have introduced some resultset changes
> in ql/src/test/results/clientpositive/llap/hybridgrace_hashjoin_2.q.out
> https://github.com/apache/hive/commit/5799398450c17d06e8ef144ce835a8524f5abec9#diff-56b3ab96b6c90fdbebe2c4f84e8595afL500



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21987) Hive is unable to read Parquet int32 annotated with decimal

2019-07-11 Thread Nandor Kollar (JIRA)


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

Nandor Kollar updated HIVE-21987:
-
Attachment: 
part-0-d6ee992d-ef56-4384-8855-5a170d3e3660-c000.snappy.parquet

> Hive is unable to read Parquet int32 annotated with decimal
> ---
>
> Key: HIVE-21987
> URL: https://issues.apache.org/jira/browse/HIVE-21987
> Project: Hive
>  Issue Type: Bug
>Reporter: Nandor Kollar
>Priority: Major
> Attachments: 
> part-0-d6ee992d-ef56-4384-8855-5a170d3e3660-c000.snappy.parquet
>
>
> When I tried to read a Parquet file from a Hive (with Tez execution engine) 
> table with a small decimal column, I got the following exception:
> {code}
> Caused by: java.lang.UnsupportedOperationException: 
> org.apache.hadoop.hive.ql.io.parquet.convert.ETypeConverter$8$1
>   at 
> org.apache.parquet.io.api.PrimitiveConverter.addInt(PrimitiveConverter.java:98)
>   at 
> org.apache.parquet.column.impl.ColumnReaderImpl$2$3.writeValue(ColumnReaderImpl.java:248)
>   at 
> org.apache.parquet.column.impl.ColumnReaderImpl.writeCurrentValueToConverter(ColumnReaderImpl.java:367)
>   at 
> org.apache.parquet.io.RecordReaderImplementation.read(RecordReaderImplementation.java:406)
>   at 
> org.apache.parquet.hadoop.InternalParquetRecordReader.nextKeyValue(InternalParquetRecordReader.java:226)
>   ... 28 more
> {code}
> Steps to reproduce:
> - Create a Hive table with a single decimal(4, 2) column
> - Create a Parquet file with int32 column annotated with decimal(4, 2) 
> logical type, put it into the previously created table location (or use the 
> attached parquet file)
> - Execute a {{select *}} on this table



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21987) Hive is unable to read Parquet int32 annotated with decimal

2019-07-11 Thread Nandor Kollar (JIRA)


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

Nandor Kollar updated HIVE-21987:
-
Description: 
When I tried to read a Parquet file from a Hive (with Tez execution engine) 
table with a small decimal column, I got the following exception:
{code}
Caused by: java.lang.UnsupportedOperationException: 
org.apache.hadoop.hive.ql.io.parquet.convert.ETypeConverter$8$1
at 
org.apache.parquet.io.api.PrimitiveConverter.addInt(PrimitiveConverter.java:98)
at 
org.apache.parquet.column.impl.ColumnReaderImpl$2$3.writeValue(ColumnReaderImpl.java:248)
at 
org.apache.parquet.column.impl.ColumnReaderImpl.writeCurrentValueToConverter(ColumnReaderImpl.java:367)
at 
org.apache.parquet.io.RecordReaderImplementation.read(RecordReaderImplementation.java:406)
at 
org.apache.parquet.hadoop.InternalParquetRecordReader.nextKeyValue(InternalParquetRecordReader.java:226)
... 28 more
{code}

Steps to reproduce:
- Create a Hive table with a single decimal(4, 2) column
- Create a Parquet file with int32 column annotated with decimal(4, 2) logical 
type, put it into the previously created table location (or use the attached 
parquet file)
- Execute a {{select *}} on this table

Also, I'm afraid that similar problems can happen with int64 decimals too. 
[Parquet specification | 
https://github.com/apache/parquet-format/blob/master/LogicalTypes.md] allows 
both of these cases.

  was:
When I tried to read a Parquet file from a Hive (with Tez execution engine) 
table with a small decimal column, I got the following exception:
{code}
Caused by: java.lang.UnsupportedOperationException: 
org.apache.hadoop.hive.ql.io.parquet.convert.ETypeConverter$8$1
at 
org.apache.parquet.io.api.PrimitiveConverter.addInt(PrimitiveConverter.java:98)
at 
org.apache.parquet.column.impl.ColumnReaderImpl$2$3.writeValue(ColumnReaderImpl.java:248)
at 
org.apache.parquet.column.impl.ColumnReaderImpl.writeCurrentValueToConverter(ColumnReaderImpl.java:367)
at 
org.apache.parquet.io.RecordReaderImplementation.read(RecordReaderImplementation.java:406)
at 
org.apache.parquet.hadoop.InternalParquetRecordReader.nextKeyValue(InternalParquetRecordReader.java:226)
... 28 more
{code}

Steps to reproduce:
- Create a Hive table with a single decimal(4, 2) column
- Create a Parquet file with int32 column annotated with decimal(4, 2) logical 
type, put it into the previously created table location (or use the attached 
parquet file)
- Execute a {{select *}} on this table


> Hive is unable to read Parquet int32 annotated with decimal
> ---
>
> Key: HIVE-21987
> URL: https://issues.apache.org/jira/browse/HIVE-21987
> Project: Hive
>  Issue Type: Bug
>Reporter: Nandor Kollar
>Priority: Major
> Attachments: 
> part-0-d6ee992d-ef56-4384-8855-5a170d3e3660-c000.snappy.parquet
>
>
> When I tried to read a Parquet file from a Hive (with Tez execution engine) 
> table with a small decimal column, I got the following exception:
> {code}
> Caused by: java.lang.UnsupportedOperationException: 
> org.apache.hadoop.hive.ql.io.parquet.convert.ETypeConverter$8$1
>   at 
> org.apache.parquet.io.api.PrimitiveConverter.addInt(PrimitiveConverter.java:98)
>   at 
> org.apache.parquet.column.impl.ColumnReaderImpl$2$3.writeValue(ColumnReaderImpl.java:248)
>   at 
> org.apache.parquet.column.impl.ColumnReaderImpl.writeCurrentValueToConverter(ColumnReaderImpl.java:367)
>   at 
> org.apache.parquet.io.RecordReaderImplementation.read(RecordReaderImplementation.java:406)
>   at 
> org.apache.parquet.hadoop.InternalParquetRecordReader.nextKeyValue(InternalParquetRecordReader.java:226)
>   ... 28 more
> {code}
> Steps to reproduce:
> - Create a Hive table with a single decimal(4, 2) column
> - Create a Parquet file with int32 column annotated with decimal(4, 2) 
> logical type, put it into the previously created table location (or use the 
> attached parquet file)
> - Execute a {{select *}} on this table
> Also, I'm afraid that similar problems can happen with int64 decimals too. 
> [Parquet specification | 
> https://github.com/apache/parquet-format/blob/master/LogicalTypes.md] allows 
> both of these cases.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21969) Beeline doesnt support HiveQL

2019-07-11 Thread Valeriy Trofimov (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883097#comment-16883097
 ] 

Valeriy Trofimov commented on HIVE-21969:
-

When developing repro steps it didnt repro. Never mind.

> Beeline doesnt support HiveQL
> -
>
> Key: HIVE-21969
> URL: https://issues.apache.org/jira/browse/HIVE-21969
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline
>Affects Versions: 2.3.5
>Reporter: Valeriy Trofimov
>Priority: Major
>
> Beeline doesnt support HiveQL. I can provide repro steps if they arent 
> obvious - run a HiveQL query in Beeline, watch it faill.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (HIVE-21969) Beeline doesnt support HiveQL

2019-07-11 Thread Valeriy Trofimov (JIRA)


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

Valeriy Trofimov resolved HIVE-21969.
-
Resolution: Cannot Reproduce

> Beeline doesnt support HiveQL
> -
>
> Key: HIVE-21969
> URL: https://issues.apache.org/jira/browse/HIVE-21969
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline
>Affects Versions: 2.3.5
>Reporter: Valeriy Trofimov
>Priority: Major
>
> Beeline doesnt support HiveQL. I can provide repro steps if they arent 
> obvious - run a HiveQL query in Beeline, watch it faill.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Status: Patch Available  (was: Open)

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Status: Open  (was: Patch Available)

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Attachment: HIVE-21224.17.patch

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883105#comment-16883105
 ] 

Bruno Pusztahazi commented on HIVE-21224:
-

[~kgyrtkirk] I have added the missing test to patch 17. 
{code:java}
TestHiveMetastoreTransformer#testCreateTable TestGenericUDFRound#testUdf {code}
These seem to be missing in the latest version of these files, so I have 
ignored them (must have been factored out since the tests were run last time).

I have added 
{code:java}
TestObjectInspectorUtils#testBucketHashGeneration{code}

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Work logged] (HIVE-21976) Offset should be null instead of zero in Calcite HiveSortLimit

2019-07-11 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21976?focusedWorklogId=275377&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275377
 ]

ASF GitHub Bot logged work on HIVE-21976:
-

Author: ASF GitHub Bot
Created on: 11/Jul/19 15:47
Start Date: 11/Jul/19 15:47
Worklog Time Spent: 10m 
  Work Description: asfgit commented on pull request #716: HIVE-21976
URL: https://github.com/apache/hive/pull/716
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 275377)
Time Spent: 20m  (was: 10m)

> Offset should be null instead of zero in Calcite HiveSortLimit
> --
>
> Key: HIVE-21976
> URL: https://issues.apache.org/jira/browse/HIVE-21976
> Project: Hive
>  Issue Type: Bug
>  Components: CBO
>Affects Versions: 4.0.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21976.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Calcite expects a value equal or greater than 1. Otherwise, it may generate 
> SQL from a plan incorrectly ({{offset 0}}).



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21976) Offset should be null instead of zero in Calcite HiveSortLimit

2019-07-11 Thread Jesus Camacho Rodriguez (JIRA)


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

Jesus Camacho Rodriguez updated HIVE-21976:
---
   Resolution: Fixed
Fix Version/s: 4.0.0
   Status: Resolved  (was: Patch Available)

Pushed to master, thanks for reviewing [~vgarg]

> Offset should be null instead of zero in Calcite HiveSortLimit
> --
>
> Key: HIVE-21976
> URL: https://issues.apache.org/jira/browse/HIVE-21976
> Project: Hive
>  Issue Type: Bug
>  Components: CBO
>Affects Versions: 4.0.0
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21976.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Calcite expects a value equal or greater than 1. Otherwise, it may generate 
> SQL from a plan incorrectly ({{offset 0}}).



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Status: Open  (was: Patch Available)

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Status: Patch Available  (was: Open)

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Attachment: (was: HIVE-21224.17.patch)

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


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

Bruno Pusztahazi updated HIVE-21224:

Attachment: HIVE-21224.17.patch

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Comment Edited] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Bruno Pusztahazi (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883105#comment-16883105
 ] 

Bruno Pusztahazi edited comment on HIVE-21224 at 7/11/19 3:58 PM:
--

[~kgyrtkirk] I have added the missing tests to patch 17. 
{code:java}
TestHiveMetastoreTransformer#testCreateTable {code}
This seem to be missing in the latest version of these files, so I have ignored 
it (must have been factored out since the tests were run last time).

I have added 
{code:java}
TestObjectInspectorUtils#testBucketHashGeneration, 
TestGenericUDFRound#testUdf{code}


was (Author: bpusztahazi):
[~kgyrtkirk] I have added the missing test to patch 17. 
{code:java}
TestHiveMetastoreTransformer#testCreateTable TestGenericUDFRound#testUdf {code}
These seem to be missing in the latest version of these files, so I have 
ignored them (must have been factored out since the tests were run last time).

I have added 
{code:java}
TestObjectInspectorUtils#testBucketHashGeneration{code}

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21923) Vectorized MapJoin may miss results when only the join key is selected

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883130#comment-16883130
 ] 

Hive QA commented on HIVE-21923:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  1m 
38s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  7m 
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 19m 
 4s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
33s{color} | {color:blue} common in master has 62 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
5s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  7m 
51s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
24s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  7m 
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  7m 
12s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
27s{color} | {color:red} common: The patch generated 1 new + 1922 unchanged - 0 
fixed = 1923 total (was 1922) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 19m 
43s{color} | {color:red} root: The patch generated 1 new + 72764 unchanged - 0 
fixed = 72765 total (was 72764) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  0m 
42s{color} | {color:red} patch/common cannot run setBugDatabaseInfo from 
findbugs {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  5m 
41s{color} | {color:red} patch/ql cannot run setBugDatabaseInfo from findbugs 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 13m  
1s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
21s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}109m 49s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17979/dev-support/hive-personality.sh
 |
| git revision | master / 4e8b940 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17979/yetus/diff-checkstyle-common.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17979/yetus/diff-checkstyle-root.txt
 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17979/yetus/patch-findbugs-common.txt
 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17979/yetus/patch-findbugs-ql.txt
 |
| modules | C: common ql . U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17979/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Vectorized MapJoin may miss results when only the join key is selected
> --
>
> Key: HIVE-21923
> URL: https://issues.apache.org/jira/browse/HIVE-21923
> Project: Hive
>  Issue Type: Bug
>Reporter: Zoltan Haindrich
>Assignee: Zolt

[jira] [Commented] (HIVE-21980) Parsing time can be high in case of deeply nested subqueries

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883131#comment-16883131
 ] 

Hive QA commented on HIVE-21980:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 10m 
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 6s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  6m 
14s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
33s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  2m 
 3s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
31s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
38s{color} | {color:red} ql: The patch generated 3 new + 4 unchanged - 2 fixed 
= 7 total (was 6) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
59s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
15s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 31m 54s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17980/dev-support/hive-personality.sh
 |
| git revision | master / 4e8b940 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17980/yetus/diff-checkstyle-ql.txt
 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17980/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Parsing time can be high in case of deeply nested subqueries
> 
>
> Key: HIVE-21980
> URL: https://issues.apache.org/jira/browse/HIVE-21980
> Project: Hive
>  Issue Type: Improvement
>  Components: Parser
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21980.01.patch, HIVE-21980.01.patch
>
>
> for queries which are recursively doing:
> {code}
> SELECT ...
> FROM (SELECT ...
>  FROM ( [...]
>  ) JOIN
> (SELECT ...
> FROM ( [...] )
> JOIN ( [...]
> )
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21980) Parsing time can be high in case of deeply nested subqueries

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883168#comment-16883168
 ] 

Hive QA commented on HIVE-21980:




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

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 7 failed/errored test(s), 16648 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[materialized_view_create_rewrite]
 (batchId=295)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[setop_subq] (batchId=7)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[stats_part] (batchId=52)
org.apache.hadoop.hive.cli.TestMiniDruidCliDriver.testCliDriver[druidmini_mv] 
(batchId=197)
org.apache.hadoop.hive.cli.TestMiniDruidKafkaCliDriver.testCliDriver[druidkafkamini_basic]
 (batchId=295)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[materialized_view_create_rewrite]
 (batchId=160)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[materialized_view_create_rewrite_dummy]
 (batchId=175)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17980/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17980/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17980/

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

This message is automatically generated.

ATTACHMENT ID: 12974372 - PreCommit-HIVE-Build

> Parsing time can be high in case of deeply nested subqueries
> 
>
> Key: HIVE-21980
> URL: https://issues.apache.org/jira/browse/HIVE-21980
> Project: Hive
>  Issue Type: Improvement
>  Components: Parser
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21980.01.patch, HIVE-21980.01.patch
>
>
> for queries which are recursively doing:
> {code}
> SELECT ...
> FROM (SELECT ...
>  FROM ( [...]
>  ) JOIN
> (SELECT ...
> FROM ( [...] )
> JOIN ( [...]
> )
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21637) Synchronized metastore cache

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883169#comment-16883169
 ] 

Hive QA commented on HIVE-21637:




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

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17981/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17981/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17981/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12974284/HIVE-21637.25.patch 
was found in seen patch url's cache and a test was probably run already on it. 
Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12974284 - PreCommit-HIVE-Build

> Synchronized metastore cache
> 
>
> Key: HIVE-21637
> URL: https://issues.apache.org/jira/browse/HIVE-21637
> Project: Hive
>  Issue Type: New Feature
>Reporter: Daniel Dai
>Assignee: Daniel Dai
>Priority: Major
> Attachments: HIVE-21637-1.patch, HIVE-21637.10.patch, 
> HIVE-21637.11.patch, HIVE-21637.12.patch, HIVE-21637.13.patch, 
> HIVE-21637.14.patch, HIVE-21637.15.patch, HIVE-21637.16.patch, 
> HIVE-21637.17.patch, HIVE-21637.18.patch, HIVE-21637.19.patch, 
> HIVE-21637.19.patch, HIVE-21637.2.patch, HIVE-21637.20.patch, 
> HIVE-21637.21.patch, HIVE-21637.22.patch, HIVE-21637.23.patch, 
> HIVE-21637.24.patch, HIVE-21637.25.patch, HIVE-21637.3.patch, 
> HIVE-21637.4.patch, HIVE-21637.5.patch, HIVE-21637.6.patch, 
> HIVE-21637.7.patch, HIVE-21637.8.patch, HIVE-21637.9.patch
>
>
> Currently, HMS has a cache implemented by CachedStore. The cache is 
> asynchronized and in HMS HA setting, we can only get eventual consistency. In 
> this Jira, we try to make it synchronized.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883184#comment-16883184
 ] 

Hive QA commented on HIVE-21948:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
10s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
26s{color} | {color:blue} upgrade-acid/pre-upgrade in master has 1 extant 
Findbugs warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
10s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
13s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} upgrade-acid/pre-upgrade: The patch generated 13 new + 
35 unchanged - 6 fixed = 48 total (was 41) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m  
9s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
14s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 11m 18s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17982/dev-support/hive-personality.sh
 |
| git revision | master / 7cfe729 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.1 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17982/yetus/diff-checkstyle-upgrade-acid_pre-upgrade.txt
 |
| modules | C: upgrade-acid/pre-upgrade U: upgrade-acid/pre-upgrade |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17982/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Work logged] (HIVE-21934) Materialized view on top of Druid not pushing everything

2019-07-11 Thread ASF GitHub Bot (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-21934?focusedWorklogId=275439&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275439
 ]

ASF GitHub Bot logged work on HIVE-21934:
-

Author: ASF GitHub Bot
Created on: 11/Jul/19 17:50
Start Date: 11/Jul/19 17:50
Worklog Time Spent: 10m 
  Work Description: b-slim commented on issue #717: HIVE-21934
URL: https://github.com/apache/hive/pull/717#issuecomment-510586895
 
 
   LGTM thanks!
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 275439)
Time Spent: 20m  (was: 10m)

> Materialized view on top of Druid not pushing everything
> 
>
> Key: HIVE-21934
> URL: https://issues.apache.org/jira/browse/HIVE-21934
> Project: Hive
>  Issue Type: Improvement
>  Components: Druid integration, Materialized views
>Reporter: slim bouguerra
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21934.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The title is not very informative, but examples hopefully are.
> this is the plan with the view
> {code}
> explain SELECT MONTH(`dates_n1`.`__time`) AS `mn___time_ok`,
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`dates_n1`.`__time`) AS `yr___time_ok`
> FROM `mv_ssb_100_scale`.`lineorder_n0` `lineorder_n0`
> JOIN `mv_ssb_100_scale`.`dates_n1` `dates_n1` ON 
> (`lineorder_n0`.`lo_orderdate` = `dates_n1`.`d_datekey`)
> JOIN `mv_ssb_100_scale`.`customer_n1` `customer_n1` ON 
> (`lineorder_n0`.`lo_custkey` = `customer_n1`.`c_custkey`)
> JOIN `mv_ssb_100_scale`.`supplier_n0` `supplier_n0` ON 
> (`lineorder_n0`.`lo_suppkey` = `supplier_n0`.`s_suppkey`)
> JOIN `mv_ssb_100_scale`.`ssb_part_n0` `ssb_part_n0` ON 
> (`lineorder_n0`.`lo_partkey` = `ssb_part_n0`.`p_partkey`)
> GROUP BY MONTH(`dates_n1`.`__time`),
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`dates_n1`.`__time`)
> INFO : Starting task [Stage-3:EXPLAIN] in serial mode
> INFO : Completed executing 
> command(queryId=sbouguerra_20190627113101_1493ee87-0288-4e30-b53c-0ee729ce3977);
>  Time taken: 0.005 seconds
> INFO : OK
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Vertex dependency in root stage |
> | Reducer 2 <- Map 1 (SIMPLE_EDGE) |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Stage-1 |
> | Reducer 2 vectorized, llap |
> | File Output Operator [FS_13] |
> | Select Operator [SEL_12] (rows=300018951 width=38) |
> | Output:["_col0","_col1","_col2","_col3"] |
> | Group By Operator [GBY_11] (rows=300018951 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(VALUE._col0)"],keys:KEY._col0,
>  KEY._col1, KEY._col2 |
> | <-Map 1 [SIMPLE_EDGE] vectorized, llap |
> | SHUFFLE [RS_10] |
> | PartitionCols:_col0, _col1, _col2 |
> | Group By Operator [GBY_9] (rows=600037902 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(1)"],keys:_col0, 
> _col1, _col2 |
> | Select Operator [SEL_8] (rows=600037902 width=38) |
> | Output:["_col0","_col1","_col2"] |
> | TableScan [TS_0] (rows=600037902 width=38) |
> | 
> mv_ssb_100_scale@ssb_mv_druid_100,ssb_mv_druid_100,Tbl:COMPLETE,Col:NONE,Output:["vc"],properties:\{"druid.fieldNames":"vc","druid.fieldTypes":"timestamp","druid.query.json":"{\"queryType\":\"scan\",\"dataSource\":\"mv_ssb_100_scale.ssb_mv_druid_100\",\"intervals\":[\"1900-01-01T00:00:00.000Z/3000-01-01T00:00:00.000Z\"],\"virtualColumns\":[{\"type\":\"expression\",\"name\":\"vc\",\"expression\":\"\\\"__time\\\"\",\"outputType\":\"LONG\"}],\"columns\":[\"vc\"],\"resultFormat\":\"compactedList\"}","druid.query.type":"scan"}
>  |
> | |
> ++
>  
> {code}
> if i use a simple druid table without MV 
> {code}
> explain SELECT MONTH(`__time`) AS `mn___time_ok`,
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`__time`) AS `yr___time_ok`
> FROM `druid_ssb.ssb_druid_100`
> GROUP BY MONTH(`__time`),
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`__time`);
> {code}
> {code}
> ++
> | Explain |
> +---

[jira] [Commented] (HIVE-21934) Materialized view on top of Druid not pushing everything

2019-07-11 Thread slim bouguerra (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883221#comment-16883221
 ] 

slim bouguerra commented on HIVE-21934:
---

+1

> Materialized view on top of Druid not pushing everything
> 
>
> Key: HIVE-21934
> URL: https://issues.apache.org/jira/browse/HIVE-21934
> Project: Hive
>  Issue Type: Improvement
>  Components: Druid integration, Materialized views
>Reporter: slim bouguerra
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21934.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The title is not very informative, but examples hopefully are.
> this is the plan with the view
> {code}
> explain SELECT MONTH(`dates_n1`.`__time`) AS `mn___time_ok`,
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`dates_n1`.`__time`) AS `yr___time_ok`
> FROM `mv_ssb_100_scale`.`lineorder_n0` `lineorder_n0`
> JOIN `mv_ssb_100_scale`.`dates_n1` `dates_n1` ON 
> (`lineorder_n0`.`lo_orderdate` = `dates_n1`.`d_datekey`)
> JOIN `mv_ssb_100_scale`.`customer_n1` `customer_n1` ON 
> (`lineorder_n0`.`lo_custkey` = `customer_n1`.`c_custkey`)
> JOIN `mv_ssb_100_scale`.`supplier_n0` `supplier_n0` ON 
> (`lineorder_n0`.`lo_suppkey` = `supplier_n0`.`s_suppkey`)
> JOIN `mv_ssb_100_scale`.`ssb_part_n0` `ssb_part_n0` ON 
> (`lineorder_n0`.`lo_partkey` = `ssb_part_n0`.`p_partkey`)
> GROUP BY MONTH(`dates_n1`.`__time`),
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`dates_n1`.`__time`)
> INFO : Starting task [Stage-3:EXPLAIN] in serial mode
> INFO : Completed executing 
> command(queryId=sbouguerra_20190627113101_1493ee87-0288-4e30-b53c-0ee729ce3977);
>  Time taken: 0.005 seconds
> INFO : OK
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Vertex dependency in root stage |
> | Reducer 2 <- Map 1 (SIMPLE_EDGE) |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Stage-1 |
> | Reducer 2 vectorized, llap |
> | File Output Operator [FS_13] |
> | Select Operator [SEL_12] (rows=300018951 width=38) |
> | Output:["_col0","_col1","_col2","_col3"] |
> | Group By Operator [GBY_11] (rows=300018951 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(VALUE._col0)"],keys:KEY._col0,
>  KEY._col1, KEY._col2 |
> | <-Map 1 [SIMPLE_EDGE] vectorized, llap |
> | SHUFFLE [RS_10] |
> | PartitionCols:_col0, _col1, _col2 |
> | Group By Operator [GBY_9] (rows=600037902 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(1)"],keys:_col0, 
> _col1, _col2 |
> | Select Operator [SEL_8] (rows=600037902 width=38) |
> | Output:["_col0","_col1","_col2"] |
> | TableScan [TS_0] (rows=600037902 width=38) |
> | 
> mv_ssb_100_scale@ssb_mv_druid_100,ssb_mv_druid_100,Tbl:COMPLETE,Col:NONE,Output:["vc"],properties:\{"druid.fieldNames":"vc","druid.fieldTypes":"timestamp","druid.query.json":"{\"queryType\":\"scan\",\"dataSource\":\"mv_ssb_100_scale.ssb_mv_druid_100\",\"intervals\":[\"1900-01-01T00:00:00.000Z/3000-01-01T00:00:00.000Z\"],\"virtualColumns\":[{\"type\":\"expression\",\"name\":\"vc\",\"expression\":\"\\\"__time\\\"\",\"outputType\":\"LONG\"}],\"columns\":[\"vc\"],\"resultFormat\":\"compactedList\"}","druid.query.type":"scan"}
>  |
> | |
> ++
>  
> {code}
> if i use a simple druid table without MV 
> {code}
> explain SELECT MONTH(`__time`) AS `mn___time_ok`,
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`__time`) AS `yr___time_ok`
> FROM `druid_ssb.ssb_druid_100`
> GROUP BY MONTH(`__time`),
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`__time`);
> {code}
> {code}
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Select Operator [SEL_1] |
> | Output:["_col0","_col1","_col2","_col3"] |
> | TableScan [TS_0] |
> | 
> Output:["extract_month","vc","$f3","extract_year"],properties:\{"druid.fieldNames":"extract_month,vc,extract_year,$f3","druid.fieldTypes":"int,bigint,int,bigint","druid.query.json":"{\"queryType\":\"groupBy\",\"dataSource\":\"druid_ssb.ssb_druid_100\",\"granularity\":\"all\",\"dimensions\":[{\"type\":\"extraction\",\"dimension\":\"__time\",\"outputName\":\"extract_month\",\"extractionFn\":{\"type\":\"timeFormat\",\"format\":\"M\",\"timeZone\":\"America/New_York\",\"locale\":\"en-US\"}},\{\"type\":\"default\",\"dimension\":\"vc\"

[jira] [Commented] (HIVE-21980) Parsing time can be high in case of deeply nested subqueries

2019-07-11 Thread Vineet Garg (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883234#comment-16883234
 ] 

Vineet Garg commented on HIVE-21980:


[~kgyrtkirk] Looks like there are test failures due to the change in grammar.

> Parsing time can be high in case of deeply nested subqueries
> 
>
> Key: HIVE-21980
> URL: https://issues.apache.org/jira/browse/HIVE-21980
> Project: Hive
>  Issue Type: Improvement
>  Components: Parser
>Reporter: Zoltan Haindrich
>Assignee: Zoltan Haindrich
>Priority: Major
> Attachments: HIVE-21980.01.patch, HIVE-21980.01.patch
>
>
> for queries which are recursively doing:
> {code}
> SELECT ...
> FROM (SELECT ...
>  FROM ( [...]
>  ) JOIN
> (SELECT ...
> FROM ( [...] )
> JOIN ( [...]
> )
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Assigned] (HIVE-21988) Do not consider nodes with 0 capacity when calculating host affinity

2019-07-11 Thread Peter Vary (JIRA)


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

Peter Vary reassigned HIVE-21988:
-


> Do not consider nodes with 0 capacity when calculating host affinity
> 
>
> Key: HIVE-21988
> URL: https://issues.apache.org/jira/browse/HIVE-21988
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Peter Vary
>Priority: Major
>
> When a node is blacklisted (capacity set to 0) then we should not assign any 
> more tasks to it



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883237#comment-16883237
 ] 

Hive QA commented on HIVE-21948:




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

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 16655 tests 
executed
*Failed tests:*
{noformat}
org.apache.hive.jdbc.TestTriggersNoTezSessionPool.testTriggerSlowQueryExecutionTime
 (batchId=280)
org.apache.hive.jdbc.TestTriggersNoTezSessionPool.testTriggerTotalLaunchedTasks 
(batchId=280)
org.apache.hive.jdbc.TestTriggersNoTezSessionPool.testTriggerVertexTotalTasks 
(batchId=280)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17982/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17982/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17982/

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

This message is automatically generated.

ATTACHMENT ID: 12974391 - PreCommit-HIVE-Build

> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21838) Hive Metastore Translation: Add API call to tell client why table has limited access

2019-07-11 Thread Naveen Gangam (JIRA)


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

Naveen Gangam updated HIVE-21838:
-
Status: Open  (was: Patch Available)

> Hive Metastore Translation: Add API call to tell client why table has limited 
> access
> 
>
> Key: HIVE-21838
> URL: https://issues.apache.org/jira/browse/HIVE-21838
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Yongzhi Chen
>Assignee: Naveen Gangam
>Priority: Major
> Attachments: HIVE-21838.2.patch, HIVE-21838.3.patch, 
> HIVE-21838.4.patch, HIVE-21838.5.patch, HIVE-21838.6.patch, 
> HIVE-21838.7.patch, HIVE-21838.8.patch, HIVE-21838.patch
>
>
> When a table access type is Read-only or None, we need a way to tell clients 
> why. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21838) Hive Metastore Translation: Add API call to tell client why table has limited access

2019-07-11 Thread Naveen Gangam (JIRA)


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

Naveen Gangam updated HIVE-21838:
-
Attachment: HIVE-21838.9.patch

> Hive Metastore Translation: Add API call to tell client why table has limited 
> access
> 
>
> Key: HIVE-21838
> URL: https://issues.apache.org/jira/browse/HIVE-21838
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Yongzhi Chen
>Assignee: Naveen Gangam
>Priority: Major
> Attachments: HIVE-21838.2.patch, HIVE-21838.3.patch, 
> HIVE-21838.4.patch, HIVE-21838.5.patch, HIVE-21838.6.patch, 
> HIVE-21838.7.patch, HIVE-21838.8.patch, HIVE-21838.9.patch, HIVE-21838.patch
>
>
> When a table access type is Read-only or None, we need a way to tell clients 
> why. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21838) Hive Metastore Translation: Add API call to tell client why table has limited access

2019-07-11 Thread Naveen Gangam (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883251#comment-16883251
 ] 

Naveen Gangam commented on HIVE-21838:
--

Somehow the precommit build skipped this patch. I see a whole bunch of builds 
that just failed instantly. Re-attaching patch8 with some minor changes.

> Hive Metastore Translation: Add API call to tell client why table has limited 
> access
> 
>
> Key: HIVE-21838
> URL: https://issues.apache.org/jira/browse/HIVE-21838
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Yongzhi Chen
>Assignee: Naveen Gangam
>Priority: Major
> Attachments: HIVE-21838.2.patch, HIVE-21838.3.patch, 
> HIVE-21838.4.patch, HIVE-21838.5.patch, HIVE-21838.6.patch, 
> HIVE-21838.7.patch, HIVE-21838.8.patch, HIVE-21838.9.patch, HIVE-21838.patch
>
>
> When a table access type is Read-only or None, we need a way to tell clients 
> why. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21838) Hive Metastore Translation: Add API call to tell client why table has limited access

2019-07-11 Thread Naveen Gangam (JIRA)


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

Naveen Gangam updated HIVE-21838:
-
Status: Patch Available  (was: Open)

> Hive Metastore Translation: Add API call to tell client why table has limited 
> access
> 
>
> Key: HIVE-21838
> URL: https://issues.apache.org/jira/browse/HIVE-21838
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Yongzhi Chen
>Assignee: Naveen Gangam
>Priority: Major
> Attachments: HIVE-21838.2.patch, HIVE-21838.3.patch, 
> HIVE-21838.4.patch, HIVE-21838.5.patch, HIVE-21838.6.patch, 
> HIVE-21838.7.patch, HIVE-21838.8.patch, HIVE-21838.9.patch, HIVE-21838.patch
>
>
> When a table access type is Read-only or None, we need a way to tell clients 
> why. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21965) Implement parallel processing in HiveStrictManagedMigration

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883264#comment-16883264
 ] 

Hive QA commented on HIVE-21965:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
40s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
4s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
58s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m  
8s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
41s{color} | {color:red} ql: The patch generated 8 new + 62 unchanged - 17 
fixed = 70 total (was 79) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
0s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
13s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 28s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17983/dev-support/hive-personality.sh
 |
| git revision | master / 7cfe729 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17983/yetus/diff-checkstyle-ql.txt
 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17983/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Implement parallel processing in HiveStrictManagedMigration
> ---
>
> Key: HIVE-21965
> URL: https://issues.apache.org/jira/browse/HIVE-21965
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21965.1.patch, HIVE-21965.2.patch, 
> HIVE-21965.3.patch, HIVE-21965.4.patch
>
>
> This process, kicked off from Ambari can take many days for systems with 
> 1000's of tables. The process needs to support parallel execution as it 
> iterates through the Databases and Tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21965) Implement parallel processing in HiveStrictManagedMigration

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883283#comment-16883283
 ] 

Hive QA commented on HIVE-21965:




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

{color:green}SUCCESS:{color} +1 due to 3 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 16648 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17983/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17983/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17983/

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

This message is automatically generated.

ATTACHMENT ID: 12974393 - PreCommit-HIVE-Build

> Implement parallel processing in HiveStrictManagedMigration
> ---
>
> Key: HIVE-21965
> URL: https://issues.apache.org/jira/browse/HIVE-21965
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21965.1.patch, HIVE-21965.2.patch, 
> HIVE-21965.3.patch, HIVE-21965.4.patch
>
>
> This process, kicked off from Ambari can take many days for systems with 
> 1000's of tables. The process needs to support parallel execution as it 
> iterates through the Databases and Tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21934) Materialized view on top of Druid not pushing everything

2019-07-11 Thread Jesus Camacho Rodriguez (JIRA)


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

Jesus Camacho Rodriguez updated HIVE-21934:
---
Status: Open  (was: Patch Available)

> Materialized view on top of Druid not pushing everything
> 
>
> Key: HIVE-21934
> URL: https://issues.apache.org/jira/browse/HIVE-21934
> Project: Hive
>  Issue Type: Improvement
>  Components: Druid integration, Materialized views
>Reporter: slim bouguerra
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21934.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The title is not very informative, but examples hopefully are.
> this is the plan with the view
> {code}
> explain SELECT MONTH(`dates_n1`.`__time`) AS `mn___time_ok`,
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`dates_n1`.`__time`) AS `yr___time_ok`
> FROM `mv_ssb_100_scale`.`lineorder_n0` `lineorder_n0`
> JOIN `mv_ssb_100_scale`.`dates_n1` `dates_n1` ON 
> (`lineorder_n0`.`lo_orderdate` = `dates_n1`.`d_datekey`)
> JOIN `mv_ssb_100_scale`.`customer_n1` `customer_n1` ON 
> (`lineorder_n0`.`lo_custkey` = `customer_n1`.`c_custkey`)
> JOIN `mv_ssb_100_scale`.`supplier_n0` `supplier_n0` ON 
> (`lineorder_n0`.`lo_suppkey` = `supplier_n0`.`s_suppkey`)
> JOIN `mv_ssb_100_scale`.`ssb_part_n0` `ssb_part_n0` ON 
> (`lineorder_n0`.`lo_partkey` = `ssb_part_n0`.`p_partkey`)
> GROUP BY MONTH(`dates_n1`.`__time`),
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`dates_n1`.`__time`)
> INFO : Starting task [Stage-3:EXPLAIN] in serial mode
> INFO : Completed executing 
> command(queryId=sbouguerra_20190627113101_1493ee87-0288-4e30-b53c-0ee729ce3977);
>  Time taken: 0.005 seconds
> INFO : OK
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Vertex dependency in root stage |
> | Reducer 2 <- Map 1 (SIMPLE_EDGE) |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Stage-1 |
> | Reducer 2 vectorized, llap |
> | File Output Operator [FS_13] |
> | Select Operator [SEL_12] (rows=300018951 width=38) |
> | Output:["_col0","_col1","_col2","_col3"] |
> | Group By Operator [GBY_11] (rows=300018951 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(VALUE._col0)"],keys:KEY._col0,
>  KEY._col1, KEY._col2 |
> | <-Map 1 [SIMPLE_EDGE] vectorized, llap |
> | SHUFFLE [RS_10] |
> | PartitionCols:_col0, _col1, _col2 |
> | Group By Operator [GBY_9] (rows=600037902 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(1)"],keys:_col0, 
> _col1, _col2 |
> | Select Operator [SEL_8] (rows=600037902 width=38) |
> | Output:["_col0","_col1","_col2"] |
> | TableScan [TS_0] (rows=600037902 width=38) |
> | 
> mv_ssb_100_scale@ssb_mv_druid_100,ssb_mv_druid_100,Tbl:COMPLETE,Col:NONE,Output:["vc"],properties:\{"druid.fieldNames":"vc","druid.fieldTypes":"timestamp","druid.query.json":"{\"queryType\":\"scan\",\"dataSource\":\"mv_ssb_100_scale.ssb_mv_druid_100\",\"intervals\":[\"1900-01-01T00:00:00.000Z/3000-01-01T00:00:00.000Z\"],\"virtualColumns\":[{\"type\":\"expression\",\"name\":\"vc\",\"expression\":\"\\\"__time\\\"\",\"outputType\":\"LONG\"}],\"columns\":[\"vc\"],\"resultFormat\":\"compactedList\"}","druid.query.type":"scan"}
>  |
> | |
> ++
>  
> {code}
> if i use a simple druid table without MV 
> {code}
> explain SELECT MONTH(`__time`) AS `mn___time_ok`,
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`__time`) AS `yr___time_ok`
> FROM `druid_ssb.ssb_druid_100`
> GROUP BY MONTH(`__time`),
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`__time`);
> {code}
> {code}
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Select Operator [SEL_1] |
> | Output:["_col0","_col1","_col2","_col3"] |
> | TableScan [TS_0] |
> | 
> Output:["extract_month","vc","$f3","extract_year"],properties:\{"druid.fieldNames":"extract_month,vc,extract_year,$f3","druid.fieldTypes":"int,bigint,int,bigint","druid.query.json":"{\"queryType\":\"groupBy\",\"dataSource\":\"druid_ssb.ssb_druid_100\",\"granularity\":\"all\",\"dimensions\":[{\"type\":\"extraction\",\"dimension\":\"__time\",\"outputName\":\"extract_month\",\"extractionFn\":{\"type\":\"timeFormat\",\"format\":\"M\",\"timeZone\":\"America/New_York\",\"locale\":\"en-US\"}},\{\"type\":\"default\",\"dimension\":\"vc\",\

[jira] [Updated] (HIVE-21934) Materialized view on top of Druid not pushing everything

2019-07-11 Thread Jesus Camacho Rodriguez (JIRA)


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

Jesus Camacho Rodriguez updated HIVE-21934:
---
Status: Patch Available  (was: In Progress)

> Materialized view on top of Druid not pushing everything
> 
>
> Key: HIVE-21934
> URL: https://issues.apache.org/jira/browse/HIVE-21934
> Project: Hive
>  Issue Type: Improvement
>  Components: Druid integration, Materialized views
>Reporter: slim bouguerra
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21934.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The title is not very informative, but examples hopefully are.
> this is the plan with the view
> {code}
> explain SELECT MONTH(`dates_n1`.`__time`) AS `mn___time_ok`,
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`dates_n1`.`__time`) AS `yr___time_ok`
> FROM `mv_ssb_100_scale`.`lineorder_n0` `lineorder_n0`
> JOIN `mv_ssb_100_scale`.`dates_n1` `dates_n1` ON 
> (`lineorder_n0`.`lo_orderdate` = `dates_n1`.`d_datekey`)
> JOIN `mv_ssb_100_scale`.`customer_n1` `customer_n1` ON 
> (`lineorder_n0`.`lo_custkey` = `customer_n1`.`c_custkey`)
> JOIN `mv_ssb_100_scale`.`supplier_n0` `supplier_n0` ON 
> (`lineorder_n0`.`lo_suppkey` = `supplier_n0`.`s_suppkey`)
> JOIN `mv_ssb_100_scale`.`ssb_part_n0` `ssb_part_n0` ON 
> (`lineorder_n0`.`lo_partkey` = `ssb_part_n0`.`p_partkey`)
> GROUP BY MONTH(`dates_n1`.`__time`),
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`dates_n1`.`__time`)
> INFO : Starting task [Stage-3:EXPLAIN] in serial mode
> INFO : Completed executing 
> command(queryId=sbouguerra_20190627113101_1493ee87-0288-4e30-b53c-0ee729ce3977);
>  Time taken: 0.005 seconds
> INFO : OK
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Vertex dependency in root stage |
> | Reducer 2 <- Map 1 (SIMPLE_EDGE) |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Stage-1 |
> | Reducer 2 vectorized, llap |
> | File Output Operator [FS_13] |
> | Select Operator [SEL_12] (rows=300018951 width=38) |
> | Output:["_col0","_col1","_col2","_col3"] |
> | Group By Operator [GBY_11] (rows=300018951 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(VALUE._col0)"],keys:KEY._col0,
>  KEY._col1, KEY._col2 |
> | <-Map 1 [SIMPLE_EDGE] vectorized, llap |
> | SHUFFLE [RS_10] |
> | PartitionCols:_col0, _col1, _col2 |
> | Group By Operator [GBY_9] (rows=600037902 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(1)"],keys:_col0, 
> _col1, _col2 |
> | Select Operator [SEL_8] (rows=600037902 width=38) |
> | Output:["_col0","_col1","_col2"] |
> | TableScan [TS_0] (rows=600037902 width=38) |
> | 
> mv_ssb_100_scale@ssb_mv_druid_100,ssb_mv_druid_100,Tbl:COMPLETE,Col:NONE,Output:["vc"],properties:\{"druid.fieldNames":"vc","druid.fieldTypes":"timestamp","druid.query.json":"{\"queryType\":\"scan\",\"dataSource\":\"mv_ssb_100_scale.ssb_mv_druid_100\",\"intervals\":[\"1900-01-01T00:00:00.000Z/3000-01-01T00:00:00.000Z\"],\"virtualColumns\":[{\"type\":\"expression\",\"name\":\"vc\",\"expression\":\"\\\"__time\\\"\",\"outputType\":\"LONG\"}],\"columns\":[\"vc\"],\"resultFormat\":\"compactedList\"}","druid.query.type":"scan"}
>  |
> | |
> ++
>  
> {code}
> if i use a simple druid table without MV 
> {code}
> explain SELECT MONTH(`__time`) AS `mn___time_ok`,
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`__time`) AS `yr___time_ok`
> FROM `druid_ssb.ssb_druid_100`
> GROUP BY MONTH(`__time`),
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`__time`);
> {code}
> {code}
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Select Operator [SEL_1] |
> | Output:["_col0","_col1","_col2","_col3"] |
> | TableScan [TS_0] |
> | 
> Output:["extract_month","vc","$f3","extract_year"],properties:\{"druid.fieldNames":"extract_month,vc,extract_year,$f3","druid.fieldTypes":"int,bigint,int,bigint","druid.query.json":"{\"queryType\":\"groupBy\",\"dataSource\":\"druid_ssb.ssb_druid_100\",\"granularity\":\"all\",\"dimensions\":[{\"type\":\"extraction\",\"dimension\":\"__time\",\"outputName\":\"extract_month\",\"extractionFn\":{\"type\":\"timeFormat\",\"format\":\"M\",\"timeZone\":\"America/New_York\",\"locale\":\"en-US\"}},\{\"type\":\"default\",\"dimension\":\

[jira] [Work started] (HIVE-21934) Materialized view on top of Druid not pushing everything

2019-07-11 Thread Jesus Camacho Rodriguez (JIRA)


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

Work on HIVE-21934 started by Jesus Camacho Rodriguez.
--
> Materialized view on top of Druid not pushing everything
> 
>
> Key: HIVE-21934
> URL: https://issues.apache.org/jira/browse/HIVE-21934
> Project: Hive
>  Issue Type: Improvement
>  Components: Druid integration, Materialized views
>Reporter: slim bouguerra
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21934.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The title is not very informative, but examples hopefully are.
> this is the plan with the view
> {code}
> explain SELECT MONTH(`dates_n1`.`__time`) AS `mn___time_ok`,
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`dates_n1`.`__time`) AS `yr___time_ok`
> FROM `mv_ssb_100_scale`.`lineorder_n0` `lineorder_n0`
> JOIN `mv_ssb_100_scale`.`dates_n1` `dates_n1` ON 
> (`lineorder_n0`.`lo_orderdate` = `dates_n1`.`d_datekey`)
> JOIN `mv_ssb_100_scale`.`customer_n1` `customer_n1` ON 
> (`lineorder_n0`.`lo_custkey` = `customer_n1`.`c_custkey`)
> JOIN `mv_ssb_100_scale`.`supplier_n0` `supplier_n0` ON 
> (`lineorder_n0`.`lo_suppkey` = `supplier_n0`.`s_suppkey`)
> JOIN `mv_ssb_100_scale`.`ssb_part_n0` `ssb_part_n0` ON 
> (`lineorder_n0`.`lo_partkey` = `ssb_part_n0`.`p_partkey`)
> GROUP BY MONTH(`dates_n1`.`__time`),
> CAST((MONTH(`dates_n1`.`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`dates_n1`.`__time`)
> INFO : Starting task [Stage-3:EXPLAIN] in serial mode
> INFO : Completed executing 
> command(queryId=sbouguerra_20190627113101_1493ee87-0288-4e30-b53c-0ee729ce3977);
>  Time taken: 0.005 seconds
> INFO : OK
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Vertex dependency in root stage |
> | Reducer 2 <- Map 1 (SIMPLE_EDGE) |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Stage-1 |
> | Reducer 2 vectorized, llap |
> | File Output Operator [FS_13] |
> | Select Operator [SEL_12] (rows=300018951 width=38) |
> | Output:["_col0","_col1","_col2","_col3"] |
> | Group By Operator [GBY_11] (rows=300018951 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(VALUE._col0)"],keys:KEY._col0,
>  KEY._col1, KEY._col2 |
> | <-Map 1 [SIMPLE_EDGE] vectorized, llap |
> | SHUFFLE [RS_10] |
> | PartitionCols:_col0, _col1, _col2 |
> | Group By Operator [GBY_9] (rows=600037902 width=38) |
> | 
> Output:["_col0","_col1","_col2","_col3"],aggregations:["sum(1)"],keys:_col0, 
> _col1, _col2 |
> | Select Operator [SEL_8] (rows=600037902 width=38) |
> | Output:["_col0","_col1","_col2"] |
> | TableScan [TS_0] (rows=600037902 width=38) |
> | 
> mv_ssb_100_scale@ssb_mv_druid_100,ssb_mv_druid_100,Tbl:COMPLETE,Col:NONE,Output:["vc"],properties:\{"druid.fieldNames":"vc","druid.fieldTypes":"timestamp","druid.query.json":"{\"queryType\":\"scan\",\"dataSource\":\"mv_ssb_100_scale.ssb_mv_druid_100\",\"intervals\":[\"1900-01-01T00:00:00.000Z/3000-01-01T00:00:00.000Z\"],\"virtualColumns\":[{\"type\":\"expression\",\"name\":\"vc\",\"expression\":\"\\\"__time\\\"\",\"outputType\":\"LONG\"}],\"columns\":[\"vc\"],\"resultFormat\":\"compactedList\"}","druid.query.type":"scan"}
>  |
> | |
> ++
>  
> {code}
> if i use a simple druid table without MV 
> {code}
> explain SELECT MONTH(`__time`) AS `mn___time_ok`,
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT) AS `qr___time_ok`,
> SUM(1) AS `sum_number_of_records_ok`,
> YEAR(`__time`) AS `yr___time_ok`
> FROM `druid_ssb.ssb_druid_100`
> GROUP BY MONTH(`__time`),
> CAST((MONTH(`__time`) - 1) / 3 + 1 AS BIGINT),
> YEAR(`__time`);
> {code}
> {code}
> ++
> | Explain |
> ++
> | Plan optimized by CBO. |
> | |
> | Stage-0 |
> | Fetch Operator |
> | limit:-1 |
> | Select Operator [SEL_1] |
> | Output:["_col0","_col1","_col2","_col3"] |
> | TableScan [TS_0] |
> | 
> Output:["extract_month","vc","$f3","extract_year"],properties:\{"druid.fieldNames":"extract_month,vc,extract_year,$f3","druid.fieldTypes":"int,bigint,int,bigint","druid.query.json":"{\"queryType\":\"groupBy\",\"dataSource\":\"druid_ssb.ssb_druid_100\",\"granularity\":\"all\",\"dimensions\":[{\"type\":\"extraction\",\"dimension\":\"__time\",\"outputName\":\"extract_month\",\"extractionFn\":{\"type\":\"timeFormat\",\"format\":\"M\",\"timeZone\":\"America/New_York\",\"locale\":\"en-US\"}},\{\"type\":\"default\",\"dimension\":\"vc\",\"outputName\":\"vc\"

[jira] [Updated] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21948:
--
Attachment: HIVE-21948.5.patch

> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch, HIVE-21948.5.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21948:
--
Status: Patch Available  (was: Open)

> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch, HIVE-21948.5.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21948) Implement parallel processing in Pre Upgrade Tool

2019-07-11 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21948:
--
Status: Open  (was: Patch Available)

> Implement parallel processing in Pre Upgrade Tool
> -
>
> Key: HIVE-21948
> URL: https://issues.apache.org/jira/browse/HIVE-21948
> Project: Hive
>  Issue Type: Improvement
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21948.1.patch, HIVE-21948.2.patch, 
> HIVE-21948.3.patch, HIVE-21948.4.patch, HIVE-21948.5.patch
>
>
> Pre Upgrade Tool scans for all databases and tables in the warehouse 
> sequentially which can be very slow in case of lots of tables.
> Example: It took the process 8-10 hours to complete on ~500k tables.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21578) Introduce SQL:2016 formats FM, FX, and nested strings

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883304#comment-16883304
 ] 

Hive QA commented on HIVE-21578:


| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  1m 
50s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
 0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
53s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
36s{color} | {color:blue} common in master has 62 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
3s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
16s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
25s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
44s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  4m 
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
15s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
14s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 28m 34s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17984/dev-support/hive-personality.sh
 |
| git revision | master / 7cfe729 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: common ql U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17984/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Introduce SQL:2016 formats FM, FX, and nested strings
> -
>
> Key: HIVE-21578
> URL: https://issues.apache.org/jira/browse/HIVE-21578
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21578.01.patch, HIVE-21578.02.patch, 
> HIVE-21578.02.patch, HIVE-21578.03.patch, HIVE-21578.04.patch, 
> HIVE-21578.04.patch, HIVE-21578.05.patch
>
>
> Enable Hive to parse the following datetime formats when any combination or 
> subset of these or previously implemented formats is provided in one string. 
>  * "text" (nested strings)
>  * FM
>  * FX
> [Definitions 
> here|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21578) Introduce SQL:2016 formats FM, FX, and nested strings

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883327#comment-16883327
 ] 

Hive QA commented on HIVE-21578:




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

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 16649 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17984/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17984/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17984/

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

This message is automatically generated.

ATTACHMENT ID: 12974400 - PreCommit-HIVE-Build

> Introduce SQL:2016 formats FM, FX, and nested strings
> -
>
> Key: HIVE-21578
> URL: https://issues.apache.org/jira/browse/HIVE-21578
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21578.01.patch, HIVE-21578.02.patch, 
> HIVE-21578.02.patch, HIVE-21578.03.patch, HIVE-21578.04.patch, 
> HIVE-21578.04.patch, HIVE-21578.05.patch
>
>
> Enable Hive to parse the following datetime formats when any combination or 
> subset of these or previously implemented formats is provided in one string. 
>  * "text" (nested strings)
>  * FM
>  * FX
> [Definitions 
> here|https://docs.google.com/document/d/1V7k6-lrPGW7_uhqM-FhKl3QsxwCRy69v2KIxPsGjc1k/edit]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21981) When LlapDaemon capacity is set to 0 and the waitqueue is not empty then the queries are stuck

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883337#comment-16883337
 ] 

Hive QA commented on HIVE-21981:


| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
14s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
43s{color} | {color:blue} llap-server in master has 83 extant Findbugs 
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
15s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 1s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
14s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
14s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 12m 41s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-17985/dev-support/hive-personality.sh
 |
| git revision | master / 7cfe729 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: llap-server U: llap-server |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17985/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> When LlapDaemon capacity is set to 0 and the waitqueue is not empty then the 
> queries are stuck
> --
>
> Key: HIVE-21981
> URL: https://issues.apache.org/jira/browse/HIVE-21981
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Peter Vary
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21981.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When an LlapDaemon executor capacity is set to 0 then the already queued 
> tasks are not handled causing the queries to stuck



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21986) HiveServer Web UI: Setting the Strict-Transport-Security in default response header

2019-07-11 Thread Rajkumar Singh (JIRA)


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

Rajkumar Singh updated HIVE-21986:
--
Attachment: (was: HIVE-21986.01.patch)

> HiveServer Web UI: Setting the Strict-Transport-Security in default response 
> header
> ---
>
> Key: HIVE-21986
> URL: https://issues.apache.org/jira/browse/HIVE-21986
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Affects Versions: 3.1.1
>Reporter: Rajkumar Singh
>Assignee: Rajkumar Singh
>Priority: Major
> Attachments: HIVE-21986.patch
>
>
> Currently, HiveServer UI HTTP response header doesn't have 
> Strict-Transport-Security set so will be adding this to default header.
> expected response after patch:
> {code:java}
> HTTP/1.1 200 OK
> Date: Wed, 10 Jul 2019 22:47:34 GMT
> Content-Type: text/html;charset=utf-8
> Strict-Transport-Security: max-age=31536000; includeSubDomains
> X-Content-Type-Options: nosniff
> X-FRAME-OPTIONS: SAMEORIGIN
> X-XSS-Protection: 1; mode=block
> Set-Cookie: JSESSIONID=fby9p6p5olb12xui7kj93uys;Path=/;HttpOnly
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Length: 3824
> Server: Jetty(9.3.25.v20180904)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21986) HiveServer Web UI: Setting the Strict-Transport-Security in default response header

2019-07-11 Thread Rajkumar Singh (JIRA)


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

Rajkumar Singh updated HIVE-21986:
--
Attachment: HIVE-21986.01.patch

> HiveServer Web UI: Setting the Strict-Transport-Security in default response 
> header
> ---
>
> Key: HIVE-21986
> URL: https://issues.apache.org/jira/browse/HIVE-21986
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Affects Versions: 3.1.1
>Reporter: Rajkumar Singh
>Assignee: Rajkumar Singh
>Priority: Major
> Attachments: HIVE-21986.patch
>
>
> Currently, HiveServer UI HTTP response header doesn't have 
> Strict-Transport-Security set so will be adding this to default header.
> expected response after patch:
> {code:java}
> HTTP/1.1 200 OK
> Date: Wed, 10 Jul 2019 22:47:34 GMT
> Content-Type: text/html;charset=utf-8
> Strict-Transport-Security: max-age=31536000; includeSubDomains
> X-Content-Type-Options: nosniff
> X-FRAME-OPTIONS: SAMEORIGIN
> X-XSS-Protection: 1; mode=block
> Set-Cookie: JSESSIONID=fby9p6p5olb12xui7kj93uys;Path=/;HttpOnly
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Length: 3824
> Server: Jetty(9.3.25.v20180904)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21986) HiveServer Web UI: Setting the Strict-Transport-Security in default response header

2019-07-11 Thread Rajkumar Singh (JIRA)


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

Rajkumar Singh updated HIVE-21986:
--
Attachment: HIVE-21986.01.patch
Status: Patch Available  (was: Open)

> HiveServer Web UI: Setting the Strict-Transport-Security in default response 
> header
> ---
>
> Key: HIVE-21986
> URL: https://issues.apache.org/jira/browse/HIVE-21986
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Affects Versions: 3.1.1
>Reporter: Rajkumar Singh
>Assignee: Rajkumar Singh
>Priority: Major
> Attachments: HIVE-21986.01.patch, HIVE-21986.patch
>
>
> Currently, HiveServer UI HTTP response header doesn't have 
> Strict-Transport-Security set so will be adding this to default header.
> expected response after patch:
> {code:java}
> HTTP/1.1 200 OK
> Date: Wed, 10 Jul 2019 22:47:34 GMT
> Content-Type: text/html;charset=utf-8
> Strict-Transport-Security: max-age=31536000; includeSubDomains
> X-Content-Type-Options: nosniff
> X-FRAME-OPTIONS: SAMEORIGIN
> X-XSS-Protection: 1; mode=block
> Set-Cookie: JSESSIONID=fby9p6p5olb12xui7kj93uys;Path=/;HttpOnly
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Length: 3824
> Server: Jetty(9.3.25.v20180904)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21986) HiveServer Web UI: Setting the Strict-Transport-Security in default response header

2019-07-11 Thread Rajkumar Singh (JIRA)


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

Rajkumar Singh updated HIVE-21986:
--
Status: Open  (was: Patch Available)

> HiveServer Web UI: Setting the Strict-Transport-Security in default response 
> header
> ---
>
> Key: HIVE-21986
> URL: https://issues.apache.org/jira/browse/HIVE-21986
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Affects Versions: 3.1.1
>Reporter: Rajkumar Singh
>Assignee: Rajkumar Singh
>Priority: Major
> Attachments: HIVE-21986.patch
>
>
> Currently, HiveServer UI HTTP response header doesn't have 
> Strict-Transport-Security set so will be adding this to default header.
> expected response after patch:
> {code:java}
> HTTP/1.1 200 OK
> Date: Wed, 10 Jul 2019 22:47:34 GMT
> Content-Type: text/html;charset=utf-8
> Strict-Transport-Security: max-age=31536000; includeSubDomains
> X-Content-Type-Options: nosniff
> X-FRAME-OPTIONS: SAMEORIGIN
> X-XSS-Protection: 1; mode=block
> Set-Cookie: JSESSIONID=fby9p6p5olb12xui7kj93uys;Path=/;HttpOnly
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Length: 3824
> Server: Jetty(9.3.25.v20180904)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21986) HiveServer Web UI: Setting the Strict-Transport-Security in default response header

2019-07-11 Thread Rajkumar Singh (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883368#comment-16883368
 ] 

Rajkumar Singh commented on HIVE-21986:
---

[~gopalv] I have uploaded the updated patch, can you please review it?

> HiveServer Web UI: Setting the Strict-Transport-Security in default response 
> header
> ---
>
> Key: HIVE-21986
> URL: https://issues.apache.org/jira/browse/HIVE-21986
> Project: Hive
>  Issue Type: Bug
>  Components: HiveServer2
>Affects Versions: 3.1.1
>Reporter: Rajkumar Singh
>Assignee: Rajkumar Singh
>Priority: Major
> Attachments: HIVE-21986.01.patch, HIVE-21986.patch
>
>
> Currently, HiveServer UI HTTP response header doesn't have 
> Strict-Transport-Security set so will be adding this to default header.
> expected response after patch:
> {code:java}
> HTTP/1.1 200 OK
> Date: Wed, 10 Jul 2019 22:47:34 GMT
> Content-Type: text/html;charset=utf-8
> Strict-Transport-Security: max-age=31536000; includeSubDomains
> X-Content-Type-Options: nosniff
> X-FRAME-OPTIONS: SAMEORIGIN
> X-XSS-Protection: 1; mode=block
> Set-Cookie: JSESSIONID=fby9p6p5olb12xui7kj93uys;Path=/;HttpOnly
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Length: 3824
> Server: Jetty(9.3.25.v20180904)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21981) When LlapDaemon capacity is set to 0 and the waitqueue is not empty then the queries are stuck

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883371#comment-16883371
 ] 

Hive QA commented on HIVE-21981:




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

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 16648 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17985/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17985/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17985/

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

This message is automatically generated.

ATTACHMENT ID: 12974167 - PreCommit-HIVE-Build

> When LlapDaemon capacity is set to 0 and the waitqueue is not empty then the 
> queries are stuck
> --
>
> Key: HIVE-21981
> URL: https://issues.apache.org/jira/browse/HIVE-21981
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Peter Vary
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21981.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When an LlapDaemon executor capacity is set to 0 then the already queued 
> tasks are not handled causing the queries to stuck



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21977) Clean up DescTableOperation

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21977:
--
Attachment: HIVE-21977.03.patch

> Clean up DescTableOperation
> ---
>
> Key: HIVE-21977
> URL: https://issues.apache.org/jira/browse/HIVE-21977
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21977.01.patch, HIVE-21977.02.patch, 
> HIVE-21977.03.patch
>
>
> DescTable operation is messy, with some unclean solutions. It should be 
> refactored.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21509) LLAP may cache corrupted column vectors and return wrong query result

2019-07-11 Thread Jesus Camacho Rodriguez (JIRA)


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

Jesus Camacho Rodriguez updated HIVE-21509:
---
Fix Version/s: 4.0.0

> LLAP may cache corrupted column vectors and return wrong query result
> -
>
> Key: HIVE-21509
> URL: https://issues.apache.org/jira/browse/HIVE-21509
> Project: Hive
>  Issue Type: Bug
>  Components: llap
>Reporter: Adam Szita
>Assignee: Adam Szita
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21509.0.wip.patch, HIVE-21509.1.wip.patch, 
> HIVE-21509.2.patch, HIVE-21509.3.patch, HIVE-21509.4.patch
>
>
> In some scenarios, LLAP might store column vectors in cache that are getting 
> reused and reset just before their original content would be written.
> The issue is a concurrency issue and is thereby flaky. It is not easy to 
> reproduce, but the odds of surfacing this issue can by improved by setting 
> LLAP executor and IO thread counts this way:
>  * set hive.llap.daemon.num.executors=32;
>  * set hive.llap.io.threadpool.size=1;
>  * using TPCDS input data of store_sales table, have at least a couple of 
> 100k's of rows, and use text format:
> {code:java}
> ROW FORMAT SERDE    'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe'  
> WITH SERDEPROPERTIES (    'field.delim'='|',    'serialization.format'='|')  
> STORED AS INPUTFORMAT    'org.apache.hadoop.mapred.TextInputFormat'  
> OUTPUTFORMAT    
> 'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat'{code}
>  * having more splits increases the issue showing itself, so it is worth to 
> _set tez.grouping.min-size=1024; set tez.grouping.max-size=1024;_
>  * run query on this this table: select min(ss_sold_date_sk) from store_sales;
> The first query result is correct (2450816 in my case). Repeating the query 
> will trigger reading from LLAP cache and produce a wrong result: 0.
> If one wants to make sure of running into this issue, place a 
> Thread.sleep(250) at the beginning of VectorDeserializeOrcWriter#run().
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-19113) Bucketing: Make CLUSTERED BY do CLUSTER BY if no explicit sorting is specified

2019-07-11 Thread Jesus Camacho Rodriguez (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-19113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883393#comment-16883393
 ] 

Jesus Camacho Rodriguez commented on HIVE-19113:


[~gopalv], correct me if I am wrong. Currently the same behavior could be 
obtained by clustering and sorting by same column:

{code}
CREATE EXTERNAL TABLE bucketed (key int)
CLUSTERED BY(key) SORTED BY(key) INTO 4 BUCKETS;
{code}

It is just that {{CLUSTERED}} here acts as {{DISTRIBUTED}} and you are saying 
that it is misleading since {{CLUSTERED BY != CLUSTER BY}}?


> Bucketing: Make CLUSTERED BY do CLUSTER BY if no explicit sorting is specified
> --
>
> Key: HIVE-19113
> URL: https://issues.apache.org/jira/browse/HIVE-19113
> Project: Hive
>  Issue Type: Improvement
>  Components: Logical Optimizer
>Affects Versions: 3.0.0
>Reporter: Gopal V
>Assignee: Deepak Jaiswal
>Priority: Major
>
> The user's expectation of 
> "create external table bucketed (key int) clustered by (key) into 4 buckets 
> stored as orc;"
> is that the table will cluster the key into 4 buckets, while the file layout 
> does not do any actual clustering of rows.
> In the absence of a "SORTED BY", this can automatically do a "SORTED BY 
> (key)" to cluster the keys within the file as expected.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21983) Cut DropTableDesc/Operation to drop table, view and materialized view

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21983:
--
Attachment: HIVE-21983.02.patch

> Cut DropTableDesc/Operation to drop table, view and materialized view
> -
>
> Key: HIVE-21983
> URL: https://issues.apache.org/jira/browse/HIVE-21983
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21983.01.patch, HIVE-21983.02.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21984) Clean up TruncateTable operation and desc

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21984:
--
Attachment: HIVE-21984.01.patch

> Clean up TruncateTable operation and desc
> -
>
> Key: HIVE-21984
> URL: https://issues.apache.org/jira/browse/HIVE-21984
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21984.01.patch
>
>
> TruncateTableDesc is not immutable, should be fixed. The DDLSemanticAnalyzer 
> has a long and complicated function for parsing truncate commands, should e 
> cut to pieces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21984) Clean up TruncateTable operation and desc

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21984:
--
Attachment: (was: HIVE-21984.01.patch)

> Clean up TruncateTable operation and desc
> -
>
> Key: HIVE-21984
> URL: https://issues.apache.org/jira/browse/HIVE-21984
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-21984.01.patch
>
>
> TruncateTableDesc is not immutable, should be fixed. The DDLSemanticAnalyzer 
> has a long and complicated function for parsing truncate commands, should e 
> cut to pieces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (HIVE-21920) Extract command authorisation from the Driver

2019-07-11 Thread Miklos Gergely (JIRA)


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

Miklos Gergely updated HIVE-21920:
--
Attachment: HIVE-21920.03.patch

> Extract command authorisation from the Driver
> -
>
> Key: HIVE-21920
> URL: https://issues.apache.org/jira/browse/HIVE-21920
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive
>Affects Versions: 3.1.1
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Major
>  Labels: pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-21920.01.patch, HIVE-21920.02.patch, 
> HIVE-21920.03.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are ~400 lines of command authorisation in the Driver class, which are 
> also used by ExplainTask. Extract them into a separate package under  
> org.apache.hadoop.hive.ql.security.authorization.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883406#comment-16883406
 ] 

Hive QA commented on HIVE-21224:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  1m 
36s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
 7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m 
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  3m 
43s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
34s{color} | {color:blue} common in master has 62 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
44s{color} | {color:blue} serde in master has 193 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
6s{color} | {color:blue} ql in master has 2255 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
39s{color} | {color:blue} service in master has 48 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
32s{color} | {color:blue} accumulo-handler in master has 21 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
28s{color} | {color:blue} cli in master has 8 extant Findbugs warnings. {color} 
|
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
24s{color} | {color:blue} contrib in master has 10 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
31s{color} | {color:blue} druid-handler in master has 3 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
31s{color} | {color:blue} hbase-handler in master has 15 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
39s{color} | {color:blue} hcatalog/core in master has 29 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
28s{color} | {color:blue} hcatalog/webhcat/java-client in master has 3 extant 
Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
41s{color} | {color:blue} hcatalog/webhcat/svr in master has 96 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
41s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs 
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  4m  
6s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
25s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  6m  
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  6m  
2s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
13s{color} | {color:red} common: The patch generated 1 new + 24 unchanged - 3 
fixed = 25 total (was 27) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
18s{color} | {color:red} serde: The patch generated 234 new + 273 unchanged - 
37 fixed = 507 total (was 310) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
55s{color} | {color:red} ql: The patch generated 8 new + 1544 unchanged - 132 
fixed = 1552 total (was 1676) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
12s{color} | {color:red} service: The patch generated 1 new + 17 unchanged - 6 
fixed = 18 total (was 23) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
12s{color} | {color:green} The patch accumulo-handler passed checkstyle {color} 
|
| {color:green}+1{color

[jira] [Commented] (HIVE-21224) Upgrade tests JUnit3 to JUnit4

2019-07-11 Thread Hive QA (JIRA)


[ 
https://issues.apache.org/jira/browse/HIVE-21224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883414#comment-16883414
 ] 

Hive QA commented on HIVE-21224:




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

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/17987/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17987/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17987/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12974423/HIVE-21224.17.patch 
was found in seen patch url's cache and a test was probably run already on it. 
Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12974423 - PreCommit-HIVE-Build

> Upgrade tests JUnit3 to JUnit4
> --
>
> Key: HIVE-21224
> URL: https://issues.apache.org/jira/browse/HIVE-21224
> Project: Hive
>  Issue Type: Improvement
>Reporter: Bruno Pusztahazi
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21224.1.patch, HIVE-21224.10.patch, 
> HIVE-21224.11.patch, HIVE-21224.12.patch, HIVE-21224.13.patch, 
> HIVE-21224.14.patch, HIVE-21224.15.patch, HIVE-21224.16.patch, 
> HIVE-21224.17.patch, HIVE-21224.2.patch, HIVE-21224.3.patch, 
> HIVE-21224.4.patch, HIVE-21224.5.patch, HIVE-21224.6.patch, 
> HIVE-21224.7.patch, HIVE-21224.8.patch, HIVE-21224.9.patch
>
>
> Old JUnit3 tests should be upgraded to JUnit4



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


  1   2   >