[jira] [Commented] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21943:




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

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

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

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

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: 12973774 - PreCommit-HIVE-Build

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Assignee: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1, HIVE-21943.patch.2
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An updated HIVE-21943:
--
Attachment: HIVE-21943.patch.2

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Assignee: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1, HIVE-21943.patch.2
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An updated HIVE-21943:
--
Attachment: (was: HIVE-21943.patch.2)

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Assignee: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An updated HIVE-21943:
--
Attachment: HIVE-21943.patch.2

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Assignee: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1, HIVE-21943.patch.2
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21943:


| (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 
31s{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 
40s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
3s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
59s{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 
42s{color} | {color:red} ql: The patch generated 1 new + 142 unchanged - 0 
fixed = 143 total (was 142) {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}  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 
14s{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-17883/dev-support/hive-personality.sh
 |
| git revision | master / 6e4c500 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17883/yetus/diff-checkstyle-ql.txt
 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17883/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Assignee: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21224:




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

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

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16329 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/17882/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17882/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17882/

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: 12973777 - 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.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.3#76005)


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

2019-07-05 Thread Hive QA (JIRA)


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

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 
25s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
 1s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m 
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  3m 
21s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
35s{color} | {color:blue} common in master has 62 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
43s{color} | {color:blue} serde in master has 193 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
7s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
40s{color} | {color:blue} service in master has 48 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
27s{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 
27s{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 
29s{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 
38s{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}  3m 
55s{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}  6m 
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  5m 
42s{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 + 9 unchanged - 3 
fixed = 10 total (was 12) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
20s{color} | {color:red} serde: The patch generated 271 new + 267 unchanged - 
43 fixed = 538 total (was 310) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
48s{color} | {color:red} ql: The patch generated 8 new + 879 unchanged - 131 
fixed = 887 total (was 1010) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
13s{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 
10s{color} | {color:green} cli: The patch generated 0 new + 9 unchanged - 1 
fixed = 9 total (was 10) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
10s{color} | {color:green} The patch contrib passed checkstyle {color} |
| {color:green}+1{color} | 

[jira] [Updated] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

2019-07-05 Thread mahesh kumar behera (JIRA)


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

mahesh kumar behera updated HIVE-21958:
---
Status: Open  (was: Patch Available)

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21958.01.patch, HIVE-21958.02.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

2019-07-05 Thread mahesh kumar behera (JIRA)


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

mahesh kumar behera updated HIVE-21958:
---
Attachment: HIVE-21958.02.patch

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21958.01.patch, HIVE-21958.02.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

2019-07-05 Thread mahesh kumar behera (JIRA)


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

mahesh kumar behera updated HIVE-21958:
---
Status: Patch Available  (was: Open)

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21958.01.patch, HIVE-21958.02.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21958:




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

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

{color:red}ERROR:{color} -1 due to 10 failed/errored test(s), 16361 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDump.parseFromEventId
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDump.parseLimit
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDump.parseTableName
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDump.parseToEventId
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDumpWithClause.parseFromEventId
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDumpWithClause.parseLimit
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDumpWithClause.parseTableName
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationSemanticAnalyzer$ReplDumpWithClause.parseToEventId
 (batchId=314)
org.apache.hadoop.hive.ql.parse.TestReplicationWithTableMigrationEx.testTableLevelDumpMigration
 (batchId=265)
org.apache.hadoop.hive.ql.security.authorization.plugin.TestHiveAuthorizerCheckInvocation.testReplDump
 (batchId=268)
{noformat}

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

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: 10 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12973770 - PreCommit-HIVE-Build

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21958.01.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21958:


| (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 
51s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
21s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 4s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  2m 
30s{color} | {color:blue} standalone-metastore/metastore-common in master has 
31 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
1s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
40s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs 
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
48s{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}  2m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  2m 
23s{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 22 new + 79 unchanged - 0 
fixed = 101 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:red}-1{color} | {color:red} findbugs {color} | {color:red}  4m 
15s{color} | {color:red} ql generated 10 new + 2243 unchanged - 9 fixed = 2253 
total (was 2252) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
44s{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} 40m 29s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:ql |
|  |  Should org.apache.hadoop.hive.ql.parse.HiveParser$DFA235 be a _static_ 
inner class?  At HiveParser.java:inner class?  At HiveParser.java:[lines 
48087-48100] |
|  |  Dead store to LA29_128 in 
org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int, 
IntStream)  At 
HiveParser.java:org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int,
 IntStream)  At HiveParser.java:[line 47827] |
|  |  Dead store to LA29_130 in 
org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int, 
IntStream)  At 
HiveParser.java:org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int,
 IntStream)  At HiveParser.java:[line 47840] |
|  |  Dead store to LA29_132 in 
org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int, 
IntStream)  At 
HiveParser.java:org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int,
 IntStream)  At HiveParser.java:[line 47853] |
|  |  Dead store to LA29_134 in 
org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int, 
IntStream)  At 
HiveParser.java:org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int,
 IntStream)  At HiveParser.java:[line 47866] |
|  |  Dead store to LA29_136 in 
org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int, 
IntStream)  At 
HiveParser.java:org.apache.hadoop.hive.ql.parse.HiveParser$DFA29.specialStateTransition(int,
 IntStream)  At HiveParser.java:[line 47879] |
|  |  Dead store to LA29_138 in 

[jira] [Commented] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21908:




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

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

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12973767/HIVE-21908.06.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: 12973767 - PreCommit-HIVE-Build

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch, 
> HIVE-21908.06.patch
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21909) Publish the LLAP Daemon capacity through ZooKeeper and honor the capacity when scheduling new tasks

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21909:




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

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

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

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

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: 12973764 - PreCommit-HIVE-Build

> Publish the LLAP Daemon capacity through ZooKeeper and honor the capacity 
> when scheduling new tasks
> ---
>
> Key: HIVE-21909
> URL: https://issues.apache.org/jira/browse/HIVE-21909
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21909.01.patch, HIVE-21909.02.patch, 
> HIVE-21909.03.patch, HIVE-21909.04.patch
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> The changes in LlapDaemonNode status (or executor number) should be reflected 
> in the ZooKeeper information, and we should make sure TezAMs are reading and 
> honor the changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21909) Publish the LLAP Daemon capacity through ZooKeeper and honor the capacity when scheduling new tasks

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21909:


| (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 
51s{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}  1m 
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
47s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
25s{color} | {color:blue} llap-client in master has 26 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
25s{color} | {color:blue} llap-tez in master has 17 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
42s{color} | {color:blue} llap-server in master has 83 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
38s{color} | {color:blue} service in master has 48 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
53s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
27s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
20s{color} | {color:red} llap-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
23s{color} | {color:red} service in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
21s{color} | {color:red} llap-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
21s{color} | {color:red} service in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 21s{color} 
| {color:red} llap-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 21s{color} 
| {color:red} service in the patch failed. {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
10s{color} | {color:red} llap-client: The patch generated 2 new + 29 unchanged 
- 2 fixed = 31 total (was 31) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
13s{color} | {color:red} llap-server: The patch generated 1 new + 50 unchanged 
- 0 fixed = 51 total (was 50) {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 
20s{color} | {color:red} llap-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  0m 
22s{color} | {color:red} service in the patch failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
52s{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} 21m 20s{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-17879/dev-support/hive-personality.sh
 |
| git revision | master / 6e4c500 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| mvninstall | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17879/yetus/patch-mvninstall-llap-server.txt
 |
| mvninstall | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17879/yetus/patch-mvninstall-service.txt
 |
| compile | 

[jira] [Commented] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21908:




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

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

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

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

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: 12973767 - PreCommit-HIVE-Build

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch, 
> HIVE-21908.06.patch
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2019-07-05 Thread Jason Dere (JIRA)


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

Jason Dere updated HIVE-21963:
--
Attachment: HIVE-21963.1.patch

> 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.3#76005)


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

2019-07-05 Thread Jason Dere (JIRA)


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

Jason Dere updated HIVE-21963:
--
Status: Patch Available  (was: Open)

> 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.3#76005)


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

2019-07-05 Thread Jason Dere (JIRA)


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

Jason Dere reassigned HIVE-21963:
-


> 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
>
> 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.3#76005)


[jira] [Commented] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21908:


| (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 
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
22s{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 
41s{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 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
22s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
13s{color} | {color:red} llap-server: The patch generated 2 new + 141 unchanged 
- 9 fixed = 143 total (was 150) {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 
51s{color} | {color:red} llap-server generated 1 new + 82 unchanged - 1 fixed = 
83 total (was 83) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
15s{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} 12m 46s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:llap-server |
|  |  Should 
org.apache.hadoop.hive.llap.daemon.impl.DumpingMetricsCollector$DumpingMetricsRecordBuilder
 be a _static_ inner class?  At DumpingMetricsCollector.java:inner class?  At 
DumpingMetricsCollector.java:[lines 41-106] |
\\
\\
|| 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-17878/dev-support/hive-personality.sh
 |
| git revision | master / 6e4c500 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17878/yetus/diff-checkstyle-llap-server.txt
 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17878/yetus/new-findbugs-llap-server.html
 |
| modules | C: llap-server U: llap-server |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17878/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch, 
> HIVE-21908.06.patch
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21944) Remove unused methods, fields and variables from Vectorizer

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21944:




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

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

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hiveptest/working/scratch/source-prep.sh' failed with exit 
status 1 and output '+ date '+%Y-%m-%d %T.%3N'
2019-07-05 22:04:13.153
+ [[ -n /usr/lib/jvm/java-8-openjdk-amd64 ]]
+ export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
+ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
+ export 
PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+ 
PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'MAVEN_OPTS=-Xmx1g '
+ MAVEN_OPTS='-Xmx1g '
+ cd /data/hiveptest/working/
+ tee /data/hiveptest/logs/PreCommit-HIVE-Build-17877/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z master ]]
+ [[ -d apache-github-source-source ]]
+ [[ ! -d apache-github-source-source/.git ]]
+ [[ ! -d apache-github-source-source ]]
+ date '+%Y-%m-%d %T.%3N'
2019-07-05 22:04:13.156
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 6e4c500 HIVE-21947: Move Materialized View Update under DDL 
(Miklos Gergely, reviewed by Jesus Camacho Rodriguez)
+ git clean -f -d
Removing standalone-metastore/metastore-server/src/gen/
+ git checkout master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
+ git reset --hard origin/master
HEAD is now at 6e4c500 HIVE-21947: Move Materialized View Update under DDL 
(Miklos Gergely, reviewed by Jesus Camacho Rodriguez)
+ git merge --ff-only origin/master
Already up-to-date.
+ date '+%Y-%m-%d %T.%3N'
2019-07-05 22:04:13.850
+ rm -rf ../yetus_PreCommit-HIVE-Build-17877
+ mkdir ../yetus_PreCommit-HIVE-Build-17877
+ git gc
+ cp -R . ../yetus_PreCommit-HIVE-Build-17877
+ mkdir /data/hiveptest/logs/PreCommit-HIVE-Build-17877/yetus
+ patchCommandPath=/data/hiveptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hiveptest/working/scratch/build.patch
+ [[ -f /data/hiveptest/working/scratch/build.patch ]]
+ chmod +x /data/hiveptest/working/scratch/smart-apply-patch.sh
+ /data/hiveptest/working/scratch/smart-apply-patch.sh 
/data/hiveptest/working/scratch/build.patch
error: 
a/ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/Vectorizer.java: 
does not exist in index
Going to apply patch with: git apply -p1
+ [[ maven == \m\a\v\e\n ]]
+ rm -rf /data/hiveptest/working/maven/org/apache/hive
+ mvn -B clean install -DskipTests -T 4 -q 
-Dmaven.repo.local=/data/hiveptest/working/maven
protoc-jar: executing: [/tmp/protoc1005974453977698674.exe, --version]
libprotoc 2.5.0
protoc-jar: executing: [/tmp/protoc1005974453977698674.exe, 
-I/data/hiveptest/working/apache-github-source-source/standalone-metastore/metastore-common/src/main/protobuf/org/apache/hadoop/hive/metastore,
 
--java_out=/data/hiveptest/working/apache-github-source-source/standalone-metastore/metastore-common/target/generated-sources,
 
/data/hiveptest/working/apache-github-source-source/standalone-metastore/metastore-common/src/main/protobuf/org/apache/hadoop/hive/metastore/metastore.proto]
ANTLR Parser Generator  Version 3.5.2
protoc-jar: executing: [/tmp/protoc4737604429188640761.exe, --version]
libprotoc 2.5.0
ANTLR Parser Generator  Version 3.5.2
Output file 
/data/hiveptest/working/apache-github-source-source/standalone-metastore/metastore-server/target/generated-sources/org/apache/hadoop/hive/metastore/parser/FilterParser.java
 does not exist: must build 
/data/hiveptest/working/apache-github-source-source/standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/parser/Filter.g
org/apache/hadoop/hive/metastore/parser/Filter.g
log4j:WARN No appenders could be found for logger (DataNucleus.Persistence).
log4j:WARN Please initialize the log4j system properly.
DataNucleus Enhancer (version 4.1.17) for API "JDO"
DataNucleus Enhancer completed with success for 41 classes.
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process 
(process-resource-bundles) on project hive-spark-client: Execution 
process-resource-bundles of goal 

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

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21578:




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

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

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

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

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: 12973747 - 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
>
>
> 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.3#76005)


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

2019-07-05 Thread Hive QA (JIRA)


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

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 
47s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
51s{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  
4s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
13s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
27s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
46s{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 
52s{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 
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
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} 28m 24s{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-17876/dev-support/hive-personality.sh
 |
| git revision | master / 6e4c500 |
| 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-17876/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
>
>
> 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.3#76005)


[jira] [Commented] (HIVE-21910) Multiple target location generation in HostAffinitySplitLocationProvider

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21910:




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

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

{color:red}ERROR:{color} -1 due to 16 failed/errored test(s), 16363 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.llap.tezplugins.TestLlapTaskSchedulerService.testDelayedLocalityNodeCommErrorImmediateAllocation
 (batchId=293)
org.apache.hadoop.hive.llap.tezplugins.TestLlapTaskSchedulerService.testForcedLocalityMultiplePreemptionsSameHost2
 (batchId=293)
org.apache.hadoop.hive.metastore.TestObjectStore.catalogs (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDatabaseOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDeprecatedConfigIsOverwritten
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSQLDropParitionsCleanup
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSQLDropPartitionsCacheCrossSession
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSqlErrorMetrics 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testEmptyTrustStoreProps 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testMasterKeyOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testMaxEventResponse 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testPartitionOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testQueryCloseOnError 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testRoleOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testTableOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testUseSSLProperty 
(batchId=232)
{noformat}

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

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: 16 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12973748 - PreCommit-HIVE-Build

> Multiple target location generation in HostAffinitySplitLocationProvider
> 
>
> Key: HIVE-21910
> URL: https://issues.apache.org/jira/browse/HIVE-21910
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Peter Vary
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21910.2.patch, HIVE-21910.3.patch, 
> HIVE-21910.4.patch, HIVE-21910.5.patch, HIVE-21910.6.patch, 
> HIVE-21910.7.patch, HIVE-21910.patch
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> We need to generate multiple target locations by 
> HostAffinitySplitLocationProvider, so we will have deterministic fallback 
> nodes in case the target node is disabled



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21910) Multiple target location generation in HostAffinitySplitLocationProvider

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21910:


| (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:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  1m 
39s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
 4s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 7s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
35s{color} | {color:blue} common in master has 62 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
24s{color} | {color:blue} llap-tez in master has 17 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
5s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
29s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
27s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  2m 
 0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
16s{color} | {color:green} The patch common passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
11s{color} | {color:green} The patch llap-tez passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
41s{color} | {color:green} ql: The patch generated 0 new + 37 unchanged - 1 
fixed = 37 total (was 38) {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}  4m 
14s{color} | {color:red} ql generated 1 new + 2252 unchanged - 0 fixed = 2253 
total (was 2252) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
24s{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} 31m 16s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:ql |
|  |  Possible null pointer dereference of knownLocations in new 
org.apache.hadoop.hive.ql.exec.tez.HostAffinitySplitLocationProvider(List, int) 
 Dereferenced at HostAffinitySplitLocationProvider.java:knownLocations in new 
org.apache.hadoop.hive.ql.exec.tez.HostAffinitySplitLocationProvider(List, int) 
 Dereferenced at HostAffinitySplitLocationProvider.java:[line 59] |
\\
\\
|| 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-17875/dev-support/hive-personality.sh
 |
| git revision | master / 6e4c500 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17875/yetus/new-findbugs-ql.html
 |
| modules | C: common llap-tez ql U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17875/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Multiple target location generation in HostAffinitySplitLocationProvider
> 
>
> 

[jira] [Commented] (HIVE-21868) Vectorize CAST...FORMAT

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21868:




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

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

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

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

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: 12973791 - PreCommit-HIVE-Build

> Vectorize CAST...FORMAT
> ---
>
> Key: HIVE-21868
> URL: https://issues.apache.org/jira/browse/HIVE-21868
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21868.01.patch, HIVE-21868.01.patch, 
> HIVE-21868.02.patch, HIVE-21868.03.patch, HIVE-21868.04.patch, 
> HIVE-21868.05.patch, HIVE-21868.06.patch, HIVE-21868.07.patch, 
> HIVE-21868.08.patch, HIVE-21868.08.patch, HIVE-21868.08.patch
>
>
> Vectorize UDFs for CAST ( AS STRING/CHAR/VARCHAR FORMAT 
> ) and CAST ( AS TIMESTAMP/DATE FORMAT ).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21938) Add database and table filter options to PreUpgradeTool

2019-07-05 Thread Krisztian Kasa (JIRA)


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

Krisztian Kasa updated HIVE-21938:
--
Attachment: HIVE-21938.4.patch

> Add database and table filter options to PreUpgradeTool
> ---
>
> Key: HIVE-21938
> URL: https://issues.apache.org/jira/browse/HIVE-21938
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Fix For: 4.0.0
>
> Attachments: HIVE-21938.1.patch, HIVE-21938.2.patch, 
> HIVE-21938.3.patch, HIVE-21938.4.patch
>
>
> By default pre upgrade tool scans all databases and tables in the warehouse. 
> Add database and table filter options to run the tool for a specific subset 
> of databases and tables only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21938) Add database and table filter options to PreUpgradeTool

2019-07-05 Thread Krisztian Kasa (JIRA)


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

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

> Add database and table filter options to PreUpgradeTool
> ---
>
> Key: HIVE-21938
> URL: https://issues.apache.org/jira/browse/HIVE-21938
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Fix For: 4.0.0
>
> Attachments: HIVE-21938.1.patch, HIVE-21938.2.patch, 
> HIVE-21938.3.patch, HIVE-21938.4.patch
>
>
> By default pre upgrade tool scans all databases and tables in the warehouse. 
> Add database and table filter options to run the tool for a specific subset 
> of databases and tables only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21938) Add database and table filter options to PreUpgradeTool

2019-07-05 Thread Krisztian Kasa (JIRA)


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

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

> Add database and table filter options to PreUpgradeTool
> ---
>
> Key: HIVE-21938
> URL: https://issues.apache.org/jira/browse/HIVE-21938
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Fix For: 4.0.0
>
> Attachments: HIVE-21938.1.patch, HIVE-21938.2.patch, 
> HIVE-21938.3.patch, HIVE-21938.4.patch
>
>
> By default pre upgrade tool scans all databases and tables in the warehouse. 
> Add database and table filter options to run the tool for a specific subset 
> of databases and tables only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21868) Vectorize CAST...FORMAT

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21868:


| (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 
37s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
19s{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 
57s{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  
6s{color} | {color:blue} ql in master has 2252 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 
27s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
12s{color} | {color:green} The patch common passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
44s{color} | {color:green} ql: The patch generated 0 new + 412 unchanged - 1 
fixed = 412 total (was 413) {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}  4m 
18s{color} | {color:red} ql generated 2 new + 2252 unchanged - 0 fixed = 2254 
total (was 2252) {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} 29m  6s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:ql |
|  |  Found reliance on default encoding in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastDateToString.sqlFormat(BytesColumnVector,
 long[], int, HiveSqlDateTimeFormatter):in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastDateToString.sqlFormat(BytesColumnVector,
 long[], int, HiveSqlDateTimeFormatter): String.getBytes()  At 
CastDateToString.java:[line 70] |
|  |  Found reliance on default encoding in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastTimestampToString.sqlFormat(BytesColumnVector,
 TimestampColumnVector, int, HiveSqlDateTimeFormatter):in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastTimestampToString.sqlFormat(BytesColumnVector,
 TimestampColumnVector, int, HiveSqlDateTimeFormatter): String.getBytes()  At 
CastTimestampToString.java:[line 79] |
\\
\\
|| 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-17874/dev-support/hive-personality.sh
 |
| git revision | master / 6e4c500 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17874/yetus/new-findbugs-ql.html
 |
| modules | C: common ql U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17874/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Vectorize CAST...FORMAT
> 

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

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21637:


| (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}  6m 
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m  
8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  3m 
20s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
22s{color} | {color:blue} storage-api in master has 48 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  2m 
29s{color} | {color:blue} standalone-metastore/metastore-common in master has 
31 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  1m 
12s{color} | {color:blue} standalone-metastore/metastore-server in master has 
179 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m 
13s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
29s{color} | {color:blue} beeline in master has 44 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
28s{color} | {color:blue} hcatalog/server-extensions in master has 3 extant 
Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
25s{color} | {color:blue} 
standalone-metastore/metastore-tools/metastore-benchmarks in master has 3 
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:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
47s{color} | {color:blue} itests/util in master has 44 extant Findbugs 
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  4m 
36s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
29s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m  
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  5m  
7s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} storage-api: The patch generated 1 new + 5 unchanged - 
0 fixed = 6 total (was 5) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
15s{color} | {color:red} standalone-metastore/metastore-common: The patch 
generated 9 new + 498 unchanged - 2 fixed = 507 total (was 500) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
40s{color} | {color:red} standalone-metastore/metastore-server: The patch 
generated 164 new + 2193 unchanged - 65 fixed = 2357 total (was 2258) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
50s{color} | {color:red} ql: The patch generated 27 new + 1020 unchanged - 10 
fixed = 1047 total (was 1030) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} standalone-metastore/metastore-tools/tools-common: The 
patch generated 5 new + 31 unchanged - 0 fixed = 36 total (was 31) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
12s{color} | {color:red} itests/hcatalog-unit: The patch generated 2 new + 24 
unchanged - 3 fixed = 26 total (was 27) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
19s{color} | {color:red} itests/hive-unit: The patch generated 3 new + 163 
unchanged - 1 fixed = 166 total (was 164) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | 

[jira] [Commented] (HIVE-21880) Enable flaky test TestReplicationScenariosAcidTablesBootstrap.testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites.

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21880:




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

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

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

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

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: 12973732 - PreCommit-HIVE-Build

> Enable flaky test 
> TestReplicationScenariosAcidTablesBootstrap.testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites.
> ---
>
> Key: HIVE-21880
> URL: https://issues.apache.org/jira/browse/HIVE-21880
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21880.01.patch, HIVE-21880.02.patch, 
> HIVE-21880.03.patch, HIVE-21880.04.patch, HIVE-21880.05.patch, 
> HIVE-21880.06.patch
>
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> Need tp enable 
> TestReplicationScenariosAcidTablesBootstrap.testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites
>  which is disabled as it is flaky and randomly failing with below error.
> {code}
> Error Message
> Notification events are missing in the meta store.
> Stacktrace
> java.lang.IllegalStateException: Notification events are missing in the meta 
> store.
>   at 
> org.apache.hadoop.hive.metastore.HiveMetaStoreClient.getNextNotification(HiveMetaStoreClient.java:3246)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.invoke(RetryingMetaStoreClient.java:212)
>   at com.sun.proxy.$Proxy58.getNextNotification(Unknown Source)
>   at 
> org.apache.hadoop.hive.ql.metadata.events.EventUtils$MSClientNotificationFetcher.getNextNotificationEvents(EventUtils.java:107)
>   at 
> org.apache.hadoop.hive.ql.metadata.events.EventUtils$NotificationEventIterator.fetchNextBatch(EventUtils.java:159)
>   at 
> org.apache.hadoop.hive.ql.metadata.events.EventUtils$NotificationEventIterator.hasNext(EventUtils.java:189)
>   at 
> org.apache.hadoop.hive.ql.exec.repl.ReplDumpTask.incrementalDump(ReplDumpTask.java:231)
>   at 
> org.apache.hadoop.hive.ql.exec.repl.ReplDumpTask.execute(ReplDumpTask.java:121)
>   at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:212)
>   at 
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:103)
>   at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:2709)
>   at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:2361)
>   at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:2028)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1788)
>   at org.apache.hadoop.hive.ql.Driver.run(Driver.java:1782)
>   at 
> org.apache.hadoop.hive.ql.reexec.ReExecDriver.run(ReExecDriver.java:162)
>   at 
> org.apache.hadoop.hive.ql.reexec.ReExecDriver.run(ReExecDriver.java:223)
>   at 
> org.apache.hadoop.hive.ql.parse.WarehouseInstance.run(WarehouseInstance.java:227)
>   at 
> org.apache.hadoop.hive.ql.parse.WarehouseInstance.dump(WarehouseInstance.java:282)
>   at 
> org.apache.hadoop.hive.ql.parse.WarehouseInstance.dump(WarehouseInstance.java:265)
>   at 
> org.apache.hadoop.hive.ql.parse.WarehouseInstance.dump(WarehouseInstance.java:289)
>   at 
> org.apache.hadoop.hive.ql.parse.TestReplicationScenariosAcidTablesBootstrap.testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites(TestReplicationScenariosAcidTablesBootstrap.java:328)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> 

[jira] [Work logged] (HIVE-21947) Move Materialized View Update under DDL

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


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

ASF GitHub Bot logged work on HIVE-21947:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 16:14
Start Date: 05/Jul/19 16:14
Worklog Time Spent: 10m 
  Work Description: asfgit commented on pull request #697: HIVE-21947 Move 
Materialized View Update under DDL
URL: https://github.com/apache/hive/pull/697
 
 
   
 

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: 272654)
Time Spent: 50m  (was: 40m)

> Move Materialized View Update under DDL
> ---
>
> Key: HIVE-21947
> URL: https://issues.apache.org/jira/browse/HIVE-21947
> 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, refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21947.01.patch, HIVE-21947.02.patch, 
> HIVE-21947.02.patch
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> MaterializedViewDesc is not part of the DDL framework, it has it's own task, 
> which defines itself as DDL. They should be moved to the framework.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21947) Move Materialized View Update under DDL

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


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

Jesus Camacho Rodriguez updated HIVE-21947:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to master, thanks [~mgergely]!

> Move Materialized View Update under DDL
> ---
>
> Key: HIVE-21947
> URL: https://issues.apache.org/jira/browse/HIVE-21947
> 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, refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21947.01.patch, HIVE-21947.02.patch, 
> HIVE-21947.02.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> MaterializedViewDesc is not part of the DDL framework, it has it's own task, 
> which defines itself as DDL. They should be moved to the framework.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (HIVE-21918) Handle each Alter Database types in a separate desc / operation

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


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

ASF GitHub Bot logged work on HIVE-21918:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 16:13
Start Date: 05/Jul/19 16:13
Worklog Time Spent: 10m 
  Work Description: jcamachor commented on pull request #701: HIVE-21918 
Handle each Alter Database types in a separate desc / operation
URL: https://github.com/apache/hive/pull/701
 
 
   
 

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: 272653)
Time Spent: 20m  (was: 10m)

> Handle each Alter Database types in a separate desc / operation
> ---
>
> Key: HIVE-21918
> URL: https://issues.apache.org/jira/browse/HIVE-21918
> 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-21918.01.patch
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> AlterDatabaseDesc / AlterDatabaseOperation handles all kind of alter database 
> commands. Following the logic of the DDL handling, they should be in separate 
> classes, with a mini framework handled by abstract ancestors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21880) Enable flaky test TestReplicationScenariosAcidTablesBootstrap.testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites.

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21880:


| (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 
47s{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}  2m 
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
17s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  2m 
30s{color} | {color:blue} standalone-metastore/metastore-common in master has 
31 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  1m 
10s{color} | {color:blue} standalone-metastore/metastore-server in master has 
179 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
26s{color} | {color:blue} hcatalog/server-extensions in master has 3 extant 
Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
40s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs 
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
19s{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 
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  2m 
23s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} itests/hcatalog-unit: The patch generated 3 new + 0 
unchanged - 0 fixed = 3 total (was 0) {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}  5m 
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
24s{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} 35m 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-17872/dev-support/hive-personality.sh
 |
| git revision | master / 9a9978f |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17872/yetus/diff-checkstyle-itests_hcatalog-unit.txt
 |
| modules | C: standalone-metastore/metastore-common 
standalone-metastore/metastore-server hcatalog/server-extensions 
itests/hcatalog-unit itests/hive-unit U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17872/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Enable flaky test 
> TestReplicationScenariosAcidTablesBootstrap.testBootstrapAcidTablesDuringIncrementalWithConcurrentWrites.
> ---
>
> Key: HIVE-21880
> URL: https://issues.apache.org/jira/browse/HIVE-21880
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0
>Reporter: Sankar Hariappan
>

[jira] [Commented] (HIVE-21938) Add database and table filter options to PreUpgradeTool

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21938:




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

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

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

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

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: 12973729 - PreCommit-HIVE-Build

> Add database and table filter options to PreUpgradeTool
> ---
>
> Key: HIVE-21938
> URL: https://issues.apache.org/jira/browse/HIVE-21938
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Fix For: 4.0.0
>
> Attachments: HIVE-21938.1.patch, HIVE-21938.2.patch, 
> HIVE-21938.3.patch
>
>
> By default pre upgrade tool scans all databases and tables in the warehouse. 
> Add database and table filter options to run the tool for a specific subset 
> of databases and tables only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21938) Add database and table filter options to PreUpgradeTool

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21938:


| (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 
32s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
11s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
27s{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 
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
12s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
10s{color} | {color:red} upgrade-acid/pre-upgrade: The patch generated 4 new + 
56 unchanged - 12 fixed = 60 total (was 68) {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 
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
10s{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 27s{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-17871/dev-support/hive-personality.sh
 |
| git revision | master / 9a9978f |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.1 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17871/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-17871/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Add database and table filter options to PreUpgradeTool
> ---
>
> Key: HIVE-21938
> URL: https://issues.apache.org/jira/browse/HIVE-21938
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Affects Versions: 3.1.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Blocker
> Fix For: 4.0.0
>
> Attachments: HIVE-21938.1.patch, HIVE-21938.2.patch, 
> HIVE-21938.3.patch
>
>
> By default pre upgrade tool scans all databases and tables in the warehouse. 
> Add database and table filter options to run the tool for a specific subset 
> of databases and tables only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21571) SHOW COMPACTIONS shows column names as its first output row

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21571:




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

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

{color:red}ERROR:{color} -1 due to 14 failed/errored test(s), 16361 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.metastore.TestObjectStore.catalogs (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDatabaseOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDeprecatedConfigIsOverwritten
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSQLDropParitionsCleanup
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSQLDropPartitionsCacheCrossSession
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSqlErrorMetrics 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testEmptyTrustStoreProps 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testMasterKeyOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testMaxEventResponse 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testPartitionOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testQueryCloseOnError 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testRoleOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testTableOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testUseSSLProperty 
(batchId=232)
{noformat}

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

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: 14 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12973722 - PreCommit-HIVE-Build

> SHOW COMPACTIONS shows column names as its first output row
> ---
>
> Key: HIVE-21571
> URL: https://issues.apache.org/jira/browse/HIVE-21571
> Project: Hive
>  Issue Type: Bug
>Reporter: Todd Lipcon
>Assignee: Rajkumar Singh
>Priority: Major
> Attachments: HIVE-21571.01.patch, HIVE-21571.02.patch, 
> HIVE-21571.03.patch, HIVE-21571.04.patch, HIVE-21571.05.patch, 
> HIVE-21571.06.patch, HIVE-21571.07.patch, HIVE-21571.patch
>
>
> SHOW COMPACTIONS yields a resultset with nice column names, and then the 
> first row of data is a repetition of those column names. This is somewhat 
> confusing and hard to read.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21962) Replacing ArrayList params with List in and around PlanUtils and MapWork

2019-07-05 Thread Ivan Suller (JIRA)


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

Ivan Suller updated HIVE-21962:
---
Attachment: HIVE-21962.1.patch

> Replacing ArrayList params with List in and around PlanUtils and MapWork
> 
>
> Key: HIVE-21962
> URL: https://issues.apache.org/jira/browse/HIVE-21962
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ivan Suller
>Assignee: Ivan Suller
>Priority: Minor
> Attachments: HIVE-21962.1.patch
>
>
> Using the implementing class is usually a bad practice. OO suggest to use the 
> least restrictive interface instead. ArrayList is used in many-many methods 
> as a parameter - this is just a tiny part of this work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21962) Replacing ArrayList params with List in and around PlanUtils and MapWork

2019-07-05 Thread Ivan Suller (JIRA)


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

Ivan Suller updated HIVE-21962:
---
Status: Patch Available  (was: In Progress)

> Replacing ArrayList params with List in and around PlanUtils and MapWork
> 
>
> Key: HIVE-21962
> URL: https://issues.apache.org/jira/browse/HIVE-21962
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ivan Suller
>Assignee: Ivan Suller
>Priority: Minor
> Attachments: HIVE-21962.1.patch
>
>
> Using the implementing class is usually a bad practice. OO suggest to use the 
> least restrictive interface instead. ArrayList is used in many-many methods 
> as a parameter - this is just a tiny part of this work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21868) Vectorize CAST...FORMAT

2019-07-05 Thread Karen Coppage (JIRA)


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

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

> Vectorize CAST...FORMAT
> ---
>
> Key: HIVE-21868
> URL: https://issues.apache.org/jira/browse/HIVE-21868
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21868.01.patch, HIVE-21868.01.patch, 
> HIVE-21868.02.patch, HIVE-21868.03.patch, HIVE-21868.04.patch, 
> HIVE-21868.05.patch, HIVE-21868.06.patch, HIVE-21868.07.patch, 
> HIVE-21868.08.patch, HIVE-21868.08.patch, HIVE-21868.08.patch
>
>
> Vectorize UDFs for CAST ( AS STRING/CHAR/VARCHAR FORMAT 
> ) and CAST ( AS TIMESTAMP/DATE FORMAT ).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (HIVE-21962) Replacing ArrayList params with List in and around PlanUtils and MapWork

2019-07-05 Thread Ivan Suller (JIRA)


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

Ivan Suller reassigned HIVE-21962:
--


> Replacing ArrayList params with List in and around PlanUtils and MapWork
> 
>
> Key: HIVE-21962
> URL: https://issues.apache.org/jira/browse/HIVE-21962
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ivan Suller
>Assignee: Ivan Suller
>Priority: Minor
>
> Using the implementing class is usually a bad practice. OO suggest to use the 
> least restrictive interface instead. ArrayList is used in many-many methods 
> as a parameter - this is just a tiny part of this work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work started] (HIVE-21962) Replacing ArrayList params with List in and around PlanUtils and MapWork

2019-07-05 Thread Ivan Suller (JIRA)


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

Work on HIVE-21962 started by Ivan Suller.
--
> Replacing ArrayList params with List in and around PlanUtils and MapWork
> 
>
> Key: HIVE-21962
> URL: https://issues.apache.org/jira/browse/HIVE-21962
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ivan Suller
>Assignee: Ivan Suller
>Priority: Minor
>
> Using the implementing class is usually a bad practice. OO suggest to use the 
> least restrictive interface instead. ArrayList is used in many-many methods 
> as a parameter - this is just a tiny part of this work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21868) Vectorize CAST...FORMAT

2019-07-05 Thread Karen Coppage (JIRA)


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

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

> Vectorize CAST...FORMAT
> ---
>
> Key: HIVE-21868
> URL: https://issues.apache.org/jira/browse/HIVE-21868
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21868.01.patch, HIVE-21868.01.patch, 
> HIVE-21868.02.patch, HIVE-21868.03.patch, HIVE-21868.04.patch, 
> HIVE-21868.05.patch, HIVE-21868.06.patch, HIVE-21868.07.patch, 
> HIVE-21868.08.patch, HIVE-21868.08.patch
>
>
> Vectorize UDFs for CAST ( AS STRING/CHAR/VARCHAR FORMAT 
> ) and CAST ( AS TIMESTAMP/DATE FORMAT ).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21571) SHOW COMPACTIONS shows column names as its first output row

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21571:


| (/) *{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 
30s{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 
59s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
1s{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  
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m  
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
39s{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 
17s{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} 24m 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-17870/dev-support/hive-personality.sh
 |
| git revision | master / 9a9978f |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17870/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> SHOW COMPACTIONS shows column names as its first output row
> ---
>
> Key: HIVE-21571
> URL: https://issues.apache.org/jira/browse/HIVE-21571
> Project: Hive
>  Issue Type: Bug
>Reporter: Todd Lipcon
>Assignee: Rajkumar Singh
>Priority: Major
> Attachments: HIVE-21571.01.patch, HIVE-21571.02.patch, 
> HIVE-21571.03.patch, HIVE-21571.04.patch, HIVE-21571.05.patch, 
> HIVE-21571.06.patch, HIVE-21571.07.patch, HIVE-21571.patch
>
>
> SHOW COMPACTIONS yields a resultset with nice column names, and then the 
> first row of data is a repetition of those column names. This is somewhat 
> confusing and hard to read.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21868) Vectorize CAST...FORMAT

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21868:




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

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

{color:red}ERROR:{color} -1 due to 16 failed/errored test(s), 16339 tests 
executed
*Failed tests:*
{noformat}
TestReplAcrossInstancesWithJsonMessageFormat - did not produce a TEST-*.xml 
file (likely timed out) (batchId=255)
org.apache.hadoop.hive.llap.daemon.impl.TestTaskExecutorService.testSetCapacity 
(batchId=350)
org.apache.hadoop.hive.metastore.TestObjectStore.catalogs (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDatabaseOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDeprecatedConfigIsOverwritten
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSQLDropParitionsCleanup
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSQLDropPartitionsCacheCrossSession
 (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testDirectSqlErrorMetrics 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testEmptyTrustStoreProps 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testMasterKeyOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testMaxEventResponse 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testPartitionOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testQueryCloseOnError 
(batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testRoleOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testTableOps (batchId=232)
org.apache.hadoop.hive.metastore.TestObjectStore.testUseSSLProperty 
(batchId=232)
{noformat}

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

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: 16 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12973734 - PreCommit-HIVE-Build

> Vectorize CAST...FORMAT
> ---
>
> Key: HIVE-21868
> URL: https://issues.apache.org/jira/browse/HIVE-21868
> Project: Hive
>  Issue Type: Improvement
>Reporter: Karen Coppage
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21868.01.patch, HIVE-21868.01.patch, 
> HIVE-21868.02.patch, HIVE-21868.03.patch, HIVE-21868.04.patch, 
> HIVE-21868.05.patch, HIVE-21868.06.patch, HIVE-21868.07.patch, 
> HIVE-21868.08.patch, HIVE-21868.08.patch
>
>
> Vectorize UDFs for CAST ( AS STRING/CHAR/VARCHAR FORMAT 
> ) and CAST ( AS TIMESTAMP/DATE FORMAT ).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21961) Update jetty version to 9.4.x

2019-07-05 Thread Oleksiy Sayankin (JIRA)


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

Oleksiy Sayankin updated HIVE-21961:

Description: Update jetty version to 9.4.x

> Update jetty version to 9.4.x
> -
>
> Key: HIVE-21961
> URL: https://issues.apache.org/jira/browse/HIVE-21961
> Project: Hive
>  Issue Type: Task
>Reporter: Oleksiy Sayankin
>Assignee: Oleksiy Sayankin
>Priority: Major
> Attachments: HIVE-21961.patch
>
>
> Update jetty version to 9.4.x



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21961) Update jetty version to 9.4.x

2019-07-05 Thread Oleksiy Sayankin (JIRA)


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

Oleksiy Sayankin updated HIVE-21961:

Attachment: HIVE-21961.patch

> Update jetty version to 9.4.x
> -
>
> Key: HIVE-21961
> URL: https://issues.apache.org/jira/browse/HIVE-21961
> Project: Hive
>  Issue Type: Task
>Reporter: Oleksiy Sayankin
>Assignee: Oleksiy Sayankin
>Priority: Major
> Attachments: HIVE-21961.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21961) Update jetty version to 9.4.x

2019-07-05 Thread Oleksiy Sayankin (JIRA)


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

Oleksiy Sayankin updated HIVE-21961:

Status: Patch Available  (was: In Progress)

> Update jetty version to 9.4.x
> -
>
> Key: HIVE-21961
> URL: https://issues.apache.org/jira/browse/HIVE-21961
> Project: Hive
>  Issue Type: Task
>Reporter: Oleksiy Sayankin
>Assignee: Oleksiy Sayankin
>Priority: Major
> Attachments: HIVE-21961.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (HIVE-21961) Update jetty version to 9.4.x

2019-07-05 Thread Oleksiy Sayankin (JIRA)


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

Oleksiy Sayankin reassigned HIVE-21961:
---


> Update jetty version to 9.4.x
> -
>
> Key: HIVE-21961
> URL: https://issues.apache.org/jira/browse/HIVE-21961
> Project: Hive
>  Issue Type: Task
>Reporter: Oleksiy Sayankin
>Assignee: Oleksiy Sayankin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work started] (HIVE-21961) Update jetty version to 9.4.x

2019-07-05 Thread Oleksiy Sayankin (JIRA)


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

Work on HIVE-21961 started by Oleksiy Sayankin.
---
> Update jetty version to 9.4.x
> -
>
> Key: HIVE-21961
> URL: https://issues.apache.org/jira/browse/HIVE-21961
> Project: Hive
>  Issue Type: Task
>Reporter: Oleksiy Sayankin
>Assignee: Oleksiy Sayankin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2019-07-05 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.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.3#76005)


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

2019-07-05 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.10.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.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.3#76005)


[jira] [Commented] (HIVE-21868) Vectorize CAST...FORMAT

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21868:


| (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 
34s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
 2s{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 
35s{color} | {color:blue} common in master has 62 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
9s{color} | {color:blue} ql in master has 2252 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 
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
12s{color} | {color:green} The patch common passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
44s{color} | {color:green} ql: The patch generated 0 new + 412 unchanged - 1 
fixed = 412 total (was 413) {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}  4m 
17s{color} | {color:red} ql generated 2 new + 2252 unchanged - 0 fixed = 2254 
total (was 2252) {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 44s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:ql |
|  |  Found reliance on default encoding in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastDateToString.sqlFormat(BytesColumnVector,
 long[], int, HiveSqlDateTimeFormatter):in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastDateToString.sqlFormat(BytesColumnVector,
 long[], int, HiveSqlDateTimeFormatter): String.getBytes()  At 
CastDateToString.java:[line 70] |
|  |  Found reliance on default encoding in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastTimestampToString.sqlFormat(BytesColumnVector,
 TimestampColumnVector, int, HiveSqlDateTimeFormatter):in 
org.apache.hadoop.hive.ql.exec.vector.expressions.CastTimestampToString.sqlFormat(BytesColumnVector,
 TimestampColumnVector, int, HiveSqlDateTimeFormatter): String.getBytes()  At 
CastTimestampToString.java:[line 79] |
\\
\\
|| 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-17869/dev-support/hive-personality.sh
 |
| git revision | master / 9a9978f |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17869/yetus/new-findbugs-ql.html
 |
| modules | C: common ql U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17869/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Vectorize CAST...FORMAT
> 

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

2019-07-05 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.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.3#76005)


[jira] [Updated] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An updated HIVE-21943:
--
Attachment: (was: HIVE-21943.patch.1)

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Assignee: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An updated HIVE-21943:
--
  Assignee: Hui An
Attachment: HIVE-21943.patch.1
Status: Patch Available  (was: Open)

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Assignee: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1, HIVE-21943.patch.1
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (HIVE-21960) HMS tasks on replica

2019-07-05 Thread Ashutosh Bapat (JIRA)


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

Ashutosh Bapat reassigned HIVE-21960:
-


> HMS tasks on replica
> 
>
> Key: HIVE-21960
> URL: https://issues.apache.org/jira/browse/HIVE-21960
> Project: Hive
>  Issue Type: Improvement
>  Components: HiveServer2, repl
>Affects Versions: 4.0.0
>Reporter: Ashutosh Bapat
>Assignee: Ashutosh Bapat
>Priority: Major
>
> An HMS performs a number of housekeeping tasks. Assess whether
>  # They are required to be performed in the replicated data
>  # Performing those on replicated data causes any issues and how to fix those.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

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


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

ASF GitHub Bot updated HIVE-21958:
--
Labels: pull-request-available  (was: )

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21958.01.patch
>
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

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


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

ASF GitHub Bot logged work on HIVE-21958:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 11:11
Start Date: 05/Jul/19 11:11
Worklog Time Spent: 10m 
  Work Description: maheshk114 commented on pull request #705: HIVE-21958 : 
The list of table expression in the inclusion and exclusion list should be 
separated by '|' instead of comma.
URL: https://github.com/apache/hive/pull/705
 
 
   …
 

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: 272539)
Time Spent: 10m
Remaining Estimate: 0h

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21958.01.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

2019-07-05 Thread mahesh kumar behera (JIRA)


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

mahesh kumar behera updated HIVE-21958:
---
Attachment: HIVE-21958.01.patch

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
> Attachments: HIVE-21958.01.patch
>
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21958) The list of table expression in the inclusion and exclusion list should be separated by '|' instead of comma.

2019-07-05 Thread mahesh kumar behera (JIRA)


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

mahesh kumar behera updated HIVE-21958:
---
Status: Patch Available  (was: Open)

> The list of table expression in the inclusion and exclusion list should be 
> separated by '|' instead of comma.
> -
>
> Key: HIVE-21958
> URL: https://issues.apache.org/jira/browse/HIVE-21958
> Project: Hive
>  Issue Type: Sub-task
>Reporter: mahesh kumar behera
>Assignee: mahesh kumar behera
>Priority: Major
> Attachments: HIVE-21958.01.patch
>
>
> Java regex expression does not support comma. If user wants multiple 
> expression to be present in the include or exclude list, then the expressions 
> can be provided separated by pipe ('|') character. The policy will look 
> something like db_name.'(t1*)|(t3)'.'t100'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21959) Clean up Concatenate and Msck DDL commands

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21959:




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

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

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16361 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[partition_discovery] 
(batchId=25)
{noformat}

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

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: 12973714 - PreCommit-HIVE-Build

> Clean up Concatenate and Msck DDL commands
> --
>
> Key: HIVE-21959
> URL: https://issues.apache.org/jira/browse/HIVE-21959
> 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, refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21959.01.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Concatenate and Msck DDL use basic data structure implementations instead of 
> their interfaces for variable declaration, like ArrayList instead of List, 
> LinkedHashMap instead of Map, etc. This is due to a lot of similar issues in 
> the code, which needs to be cleaned.
> Concatenate also had a non-immutable Desc class, that needs to be transformed 
> into an immutable one. Concatenate operation code should be cut into smaller 
> functions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

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


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

ASF GitHub Bot logged work on HIVE-21908:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 10:53
Start Date: 05/Jul/19 10:53
Worklog Time Spent: 10m 
  Work Description: asinkovits commented on pull request #699: HIVE-21908: 
LlapDaemon node status should be reflected in the metrics
URL: https://github.com/apache/hive/pull/699#discussion_r300637071
 
 

 ##
 File path: 
llap-server/src/java/org/apache/hadoop/hive/llap/daemon/impl/TaskExecutorService.java
 ##
 @@ -164,9 +171,9 @@ public TaskExecutorService(int numExecutors, int 
waitQueueSize,
 this.enablePreemption = enablePreemption;
 this.numSlotsAvailable = new AtomicInteger(numExecutors);
 this.metrics = metrics;
-if (metrics != null) {
-  metrics.setNumExecutorsAvailable(numSlotsAvailable.get());
-}
+metrics.setNumExecutorsAvailable(numSlotsAvailable.get());
 
 Review comment:
   Done.
 

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: 272534)
Time Spent: 1h 40m  (was: 1.5h)

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch, 
> HIVE-21908.06.patch
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

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


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

ASF GitHub Bot logged work on HIVE-21908:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 10:53
Start Date: 05/Jul/19 10:53
Worklog Time Spent: 10m 
  Work Description: asinkovits commented on pull request #699: HIVE-21908: 
LlapDaemon node status should be reflected in the metrics
URL: https://github.com/apache/hive/pull/699#discussion_r300637062
 
 

 ##
 File path: 
llap-server/src/java/org/apache/hadoop/hive/llap/metrics/LlapDaemonExecutorInfo.java
 ##
 @@ -28,7 +28,9 @@
 public enum LlapDaemonExecutorInfo implements MetricsInfo {
   ExecutorMetrics("Llap daemon cache related metrics"),
   ExecutorMaxFreeSlots("Sum of wait queue size and number of executors"),
-  ExecutorNumExecutorsPerInstance("Total number of executor threads per node"),
+  ExecutorNumExecutors("Total number of executor threads"),
+  ExecutorMaxConfiguredFreeSlots("Sum of the configured wait queue size and 
the configured number of executors"),
 
 Review comment:
   Renamed.
 

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: 272533)
Time Spent: 1.5h  (was: 1h 20m)

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch, 
> HIVE-21908.06.patch
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

2019-07-05 Thread Antal Sinkovits (JIRA)


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

Antal Sinkovits updated HIVE-21908:
---
Attachment: HIVE-21908.06.patch

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch, 
> HIVE-21908.06.patch
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21437) Vectorization: Decimal64 division with integer columns

2019-07-05 Thread Laszlo Bodor (JIRA)


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

Laszlo Bodor commented on HIVE-21437:
-

+1

> Vectorization: Decimal64 division with integer columns
> --
>
> Key: HIVE-21437
> URL: https://issues.apache.org/jira/browse/HIVE-21437
> Project: Hive
>  Issue Type: Bug
>  Components: Vectorization
>Affects Versions: 4.0.0
>Reporter: Gopal V
>Assignee: Attila Magyar
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21437.1.patch, HIVE-21437.2.patch, 
> HIVE-21437.3.patch, HIVE-21437.6.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Vectorizer fails for
> {code}
> CREATE temporary TABLE `catalog_Sales`(
>   `cs_quantity` int, 
>   `cs_wholesale_cost` decimal(7,2), 
>   `cs_list_price` decimal(7,2), 
>   `cs_sales_price` decimal(7,2), 
>   `cs_ext_discount_amt` decimal(7,2), 
>   `cs_ext_sales_price` decimal(7,2), 
>   `cs_ext_wholesale_cost` decimal(7,2), 
>   `cs_ext_list_price` decimal(7,2), 
>   `cs_ext_tax` decimal(7,2), 
>   `cs_coupon_amt` decimal(7,2), 
>   `cs_ext_ship_cost` decimal(7,2), 
>   `cs_net_paid` decimal(7,2), 
>   `cs_net_paid_inc_tax` decimal(7,2), 
>   `cs_net_paid_inc_ship` decimal(7,2), 
>   `cs_net_paid_inc_ship_tax` decimal(7,2), 
>   `cs_net_profit` decimal(7,2))
>  ;
> explain vectorization detail select maxcs_ext_list_price - 
> cs_ext_wholesale_cost) - cs_ext_discount_amt) + cs_ext_sales_price) / 2) from 
> catalog_sales;
> {code}
> {code}
> 'Map Vectorization:'
> 'enabled: true'
> 'enabledConditionsMet: 
> hive.vectorized.use.vectorized.input.format IS true'
> 'inputFileFormats: 
> org.apache.hadoop.hive.ql.io.orc.OrcInputFormat'
> 'notVectorizedReason: SELECT operator: Could not instantiate 
> DecimalColDivideDecimalScalar with arguments arguments: [21, 20, 22], 
> argument classes: [Integer, Integer, Integer], exception: 
> java.lang.IllegalArgumentException: java.lang.ClassCastException@63b56be0 
> stack trace: 
> sun.reflect.GeneratedConstructorAccessor.newInstance(Unknown 
> Source), 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45),
>  java.lang.reflect.Constructor.newInstance(Constructor.java:423), 
> org.apache.hadoop.hive.ql.exec.vector.VectorizationContext.instantiateExpression(VectorizationContext.java:2088),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.fixDecimalDataTypePhysicalVariations(Vectorizer.java:4662),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.fixDecimalDataTypePhysicalVariations(Vectorizer.java:4602),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.vectorizeSelectOperator(Vectorizer.java:4584),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.validateAndVectorizeOperator(Vectorizer.java:5171),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.doProcessChild(Vectorizer.java:923),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.doProcessChildren(Vectorizer.java:809),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.validateAndVectorizeOperatorTree(Vectorizer.java:776),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer.access$2400(Vectorizer.java:240),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer$VectorizationDispatcher.validateAndVectorizeMapOperators(Vectorizer.java:2038),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer$VectorizationDispatcher.validateAndVectorizeMapOperators(Vectorizer.java:1990),
>  
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer$VectorizationDispatcher.validateAndVectorizeMapWork(Vectorizer.java:1963),
>  ...'
> 'vectorized: false'
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (HIVE-21893) Handle concurrent write + drop when ACID tables are getting bootstrapped.

2019-07-05 Thread Ashutosh Bapat (JIRA)


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

Ashutosh Bapat reassigned HIVE-21893:
-

Assignee: Sankar Hariappan  (was: Ashutosh Bapat)

> Handle concurrent write + drop when ACID tables are getting bootstrapped.
> -
>
> Key: HIVE-21893
> URL: https://issues.apache.org/jira/browse/HIVE-21893
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0
>Reporter: Sankar Hariappan
>Assignee: Sankar Hariappan
>Priority: Major
>  Labels: DR, Replication
>
> ACID tables will be bootstrapped during incremental phase in couple of cases. 
> 1. hive.repl.bootstrap.acid.tables is set to true in WITH clause of REPL DUMP.
> 2. If replication policy is changed using REPLACE clause in REPL DUMP where 
> the ACID table is matching new policy but not old policy.
> REPL DUMP performed below sequence of operations. Let's say Thread (T1)
> 1. Get Last Repl ID (lastId)
> 2. Open Transaction (Tx1)
> 3. Dump events until lastId.
> 4. Get the list of tables in the given DB.
> 5. If table matches current policy, then bootstrap dump it.
> Let's say, concurrently another thread  (let's say T2) is running as follows.
> 11. Open Transaction (Tx2).
> 12. Insert into ACID table Tbl1.
> 13. Commit Transaction (Tx2)
> 14. Drop table (Tbl1) --> Not necessarily same thread, may be from different 
> thread as well.
> *Problematic Use-cases:*
> 1. If Step-11 happens between Step-1 and Step-2. Also, Step-13 completes 
> before we forcefully abort Tx2 from REPL DUMP thread T1. Also, assume Step-14 
> is done after bootstrap is completed. In this case, bootstrap would replicate 
> the data/writeId written by Tx2. But, the next incremental cycle would also 
> replicate the open_txn, allocate_writeid and commit_txn events which would 
> duplicate the data.
> 2. If Step-11 to Step-14 in Thread T2 happens after Step-1 in REPL DUMP 
> thread T1. In this case, table is not bootstrapped but the corresponding 
> open_txn, allocate_writeid, commit_txn and drop events would be replicated in 
> next cycle. During next cycle, REPL LOAD would fail on commmitTxn event as 
> table is dropped or event is missing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

2019-07-05 Thread Antal Sinkovits (JIRA)


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

Antal Sinkovits updated HIVE-21908:
---
Attachment: HIVE-21908.05.patch

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch, HIVE-21908.05.patch
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21893) Handle concurrent write + drop when ACID tables are getting bootstrapped.

2019-07-05 Thread Ashutosh Bapat (JIRA)


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

Ashutosh Bapat commented on HIVE-21893:
---

[~sankarh],  these two issues can happen even in case of normal bootstrap for a 
new policy, not just in case of the one during incremental phase. But anyway 
here’s my analysis of problematic cases.

The key point here is following comment in 
org.apache.hadoop.hive.ql.exec.repl.ReplDumpTask#getValidTxnListForReplDump()

 
{code:java}
// Key design point for REPL DUMP is to not have any txns older than current 
txn in which
// dump runs. This is needed to ensure that Repl dump doesn't copy any data 
files written by
// any open txns mainly for streaming ingest case where one delta file shall 
have data from
// committed/aborted/open txns. It may also have data inconsistency if the 
on-going txns
// doesn't have corresponding open/write events captured which means, catch-up 
incremental
// phase won't be able to replicate those txns. So, the logic is to wait for 
the given amount
// of time to see if all open txns < current txn is getting aborted/committed. 
If not, then
// we forcefully abort those txns just like AcidHouseKeeperService.{code}
 

 Case 1
{quote}If Step-11 happens between Step-1 and Step-2. Also, Step-13 completes 
before we forcefully abort Tx2 from REPL DUMP thread T1. Also, assume Step-14 
is done after bootstrap is completed. In this case, bootstrap would replicate 
the data/writeId written by Tx2. But, the next incremental cycle would also 
replicate the open_txn, allocate_writeid and commit_txn events which would 
duplicate the data.
{quote}
If step-11 happens between step-1 and step-2 that itself can cause multiple 
problems as the open transaction event is replayed twice (once during bootstrap 
and once during next incremental), thus causing writeIds on target going out of 
sync with the source. A better solution would be to combine 
setLastReplIdForDump() and openTransaction() in Driver.compile() for REPL DUMP 
case. We should let openTransaction() return the eventId of the open 
transaction event of the REPL DUMP. This eventId would be set as the 
lastReplIdForDump(). The next incremental dump will start from the events 
following this open transaction event.

With that we will prohibit step 11 from happening between step 1 and step 2. So 
step-11 can happen either after step 2 or before 1.
 # If it happens after 2, it will not be recorded in the snapshot of DUMP and 
thus changes within that transaction will not be replicated during bootstrap. 
The next incremental will replicate the events.

 # If step-11 happens before step-1 and commits before we start the dump, the 
changes by it will be replicated during bootstrap since that transaction will 
be considered as visible to the REPL DUMP transaction. If alloc_writeId event 
is idempotent for a given transaction on source, once the open transaction 
event has been replicated as part of bootstrap, same writeId will be allocated 
however times the alloc_writeId event is replicated, thus keeping the writeIds 
on source and target in sync. Any files written will be marked with the same 
writeId, so copying them multiple times will not duplicate data. So there’s not 
correctness issue there in this case either.

case 2
{quote}If Step-11 to Step-14 in Thread T2 happens after Step-1 in REPL DUMP 
thread T1. In this case, table is not bootstrapped but the corresponding 
open_txn, allocate_writeid, commit_txn and drop events would be replicated in 
next cycle. During next cycle, REPL LOAD would fail on commitTxn event as table 
is dropped or event is missing.
{quote}
If step-11 to step 14 happen before step-1, those will be covered by bootstrap 
itself and they will not appear in the incremental. I think you wanted to say 
that step 14 happens before step 4 thus the table is not bootstrapped, but any 
event after open transaction are part of next incremental.

This case is covered by test 
org.apache.hadoop.hive.ql.parse.TestReplicationScenariosAcidTables#testAcidTablesBootstrapWithConcurrentDropTable().

In this case, the ALTER TABLE events created by INSERT operation are converted 
to CreateTable on target and thus at the time of commit it sees the table, 
which is dropped by subsequent drop event. So, no correctness issue here as 
well.

> Handle concurrent write + drop when ACID tables are getting bootstrapped.
> -
>
> Key: HIVE-21893
> URL: https://issues.apache.org/jira/browse/HIVE-21893
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Major
>  Labels: DR, Replication
>
> ACID tables will be bootstrapped during 

[jira] [Updated] (HIVE-21909) Publish the LLAP Daemon capacity through ZooKeeper and honor the capacity when scheduling new tasks

2019-07-05 Thread Antal Sinkovits (JIRA)


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

Antal Sinkovits updated HIVE-21909:
---
Attachment: HIVE-21909.04.patch

> Publish the LLAP Daemon capacity through ZooKeeper and honor the capacity 
> when scheduling new tasks
> ---
>
> Key: HIVE-21909
> URL: https://issues.apache.org/jira/browse/HIVE-21909
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21909.01.patch, HIVE-21909.02.patch, 
> HIVE-21909.03.patch, HIVE-21909.04.patch
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> The changes in LlapDaemonNode status (or executor number) should be reflected 
> in the ZooKeeper information, and we should make sure TezAMs are reading and 
> honor the changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

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


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

ASF GitHub Bot logged work on HIVE-21908:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 10:32
Start Date: 05/Jul/19 10:32
Worklog Time Spent: 10m 
  Work Description: pvary commented on pull request #699: HIVE-21908: 
LlapDaemon node status should be reflected in the metrics
URL: https://github.com/apache/hive/pull/699#discussion_r300628748
 
 

 ##
 File path: 
llap-server/src/java/org/apache/hadoop/hive/llap/daemon/impl/TaskExecutorService.java
 ##
 @@ -164,9 +171,9 @@ public TaskExecutorService(int numExecutors, int 
waitQueueSize,
 this.enablePreemption = enablePreemption;
 this.numSlotsAvailable = new AtomicInteger(numExecutors);
 this.metrics = metrics;
-if (metrics != null) {
-  metrics.setNumExecutorsAvailable(numSlotsAvailable.get());
-}
+metrics.setNumExecutorsAvailable(numSlotsAvailable.get());
 
 Review comment:
   Or remove this from below :D
 

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: 272528)
Time Spent: 1h 20m  (was: 1h 10m)

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

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


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

ASF GitHub Bot logged work on HIVE-21908:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 10:32
Start Date: 05/Jul/19 10:32
Worklog Time Spent: 10m 
  Work Description: pvary commented on pull request #699: HIVE-21908: 
LlapDaemon node status should be reflected in the metrics
URL: https://github.com/apache/hive/pull/699#discussion_r300630116
 
 

 ##
 File path: 
llap-server/src/java/org/apache/hadoop/hive/llap/metrics/LlapDaemonExecutorInfo.java
 ##
 @@ -28,7 +28,9 @@
 public enum LlapDaemonExecutorInfo implements MetricsInfo {
   ExecutorMetrics("Llap daemon cache related metrics"),
   ExecutorMaxFreeSlots("Sum of wait queue size and number of executors"),
-  ExecutorNumExecutorsPerInstance("Total number of executor threads per node"),
+  ExecutorNumExecutors("Total number of executor threads"),
+  ExecutorMaxConfiguredFreeSlots("Sum of the configured wait queue size and 
the configured number of executors"),
 
 Review comment:
   nit: I would name it ExecutorMaxFreeSlotsConfigured 
 

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: 272529)

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Work logged] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

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


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

ASF GitHub Bot logged work on HIVE-21908:
-

Author: ASF GitHub Bot
Created on: 05/Jul/19 10:23
Start Date: 05/Jul/19 10:23
Worklog Time Spent: 10m 
  Work Description: pvary commented on pull request #699: HIVE-21908: 
LlapDaemon node status should be reflected in the metrics
URL: https://github.com/apache/hive/pull/699#discussion_r300628638
 
 

 ##
 File path: 
llap-server/src/java/org/apache/hadoop/hive/llap/daemon/impl/TaskExecutorService.java
 ##
 @@ -164,9 +171,9 @@ public TaskExecutorService(int numExecutors, int 
waitQueueSize,
 this.enablePreemption = enablePreemption;
 this.numSlotsAvailable = new AtomicInteger(numExecutors);
 this.metrics = metrics;
-if (metrics != null) {
-  metrics.setNumExecutorsAvailable(numSlotsAvailable.get());
-}
+metrics.setNumExecutorsAvailable(numSlotsAvailable.get());
 
 Review comment:
   Maybe this.metrics
 

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: 272526)
Time Spent: 1h 10m  (was: 1h)

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21959) Clean up Concatenate and Msck DDL commands

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21959:


| (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 
37s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
 5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
38s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
 8s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  1m 
11s{color} | {color:blue} standalone-metastore/metastore-server in master has 
179 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
9s{color} | {color:blue} ql in master has 2252 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
21s{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 
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
33s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
18s{color} | {color:red} standalone-metastore/metastore-server: The patch 
generated 2 new + 48 unchanged - 7 fixed = 50 total (was 55) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
53s{color} | {color:red} ql: The patch generated 5 new + 1431 unchanged - 64 
fixed = 1436 total (was 1495) {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}  5m 
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m 
19s{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} 31m 24s{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-17868/dev-support/hive-personality.sh
 |
| git revision | master / 9a9978f |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17868/yetus/diff-checkstyle-standalone-metastore_metastore-server.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17868/yetus/diff-checkstyle-ql.txt
 |
| modules | C: standalone-metastore/metastore-server ql U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17868/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Clean up Concatenate and Msck DDL commands
> --
>
> Key: HIVE-21959
> URL: https://issues.apache.org/jira/browse/HIVE-21959
> 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, refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21959.01.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Concatenate and Msck DDL use basic data structure implementations 

[jira] [Commented] (HIVE-21908) LlapDaemon node status should be reflected in the metrics

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21908:




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

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

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12973709/HIVE-21908.04.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: 12973709 - PreCommit-HIVE-Build

> LlapDaemon node status should be reflected in the metrics
> -
>
> Key: HIVE-21908
> URL: https://issues.apache.org/jira/browse/HIVE-21908
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Antal Sinkovits
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21908.01.patch, HIVE-21908.02.patch, 
> HIVE-21908.03.patch, HIVE-21908.04.patch
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> When we enable/disable a node it should be reflected in the LlapDaemon 
> metrics, so the administrator can act upon the disabled nodes. They can 
> manually check the status and either reenable them by restart, or fix the 
> existing issues causing the problems



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21947) Move Materialized View Update under DDL

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21947:




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

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

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

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

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: 12973700 - PreCommit-HIVE-Build

> Move Materialized View Update under DDL
> ---
>
> Key: HIVE-21947
> URL: https://issues.apache.org/jira/browse/HIVE-21947
> 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, refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21947.01.patch, HIVE-21947.02.patch, 
> HIVE-21947.02.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> MaterializedViewDesc is not part of the DDL framework, it has it's own task, 
> which defines itself as DDL. They should be moved to the framework.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21944) Remove unused methods, fields and variables from Vectorizer

2019-07-05 Thread Ivan Suller (JIRA)


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

Ivan Suller updated HIVE-21944:
---
Attachment: HIVE-21944.1.patch

> Remove unused methods, fields and variables from Vectorizer
> ---
>
> Key: HIVE-21944
> URL: https://issues.apache.org/jira/browse/HIVE-21944
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Ivan Suller
>Assignee: Ivan Suller
>Priority: Trivial
> Attachments: HIVE-21944.1.patch, HIVE-21944.1.patch, 
> HIVE-21944.1.patch
>
>
> It seems there are many unused fields, variables and methods in 
> org.apache.hadoop.hive.ql.optimizer.physical.Vectorizer class. Removing them 
> would make the code easier to understand.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21918) Handle each Alter Database types in a separate desc / operation

2019-07-05 Thread Zoltan Haindrich (JIRA)


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

Zoltan Haindrich updated HIVE-21918:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

pushed to master. Thank you Miklos!

> Handle each Alter Database types in a separate desc / operation
> ---
>
> Key: HIVE-21918
> URL: https://issues.apache.org/jira/browse/HIVE-21918
> 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-21918.01.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> AlterDatabaseDesc / AlterDatabaseOperation handles all kind of alter database 
> commands. Following the logic of the DDL handling, they should be in separate 
> classes, with a mini framework handled by abstract ancestors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21910) Multiple target location generation in HostAffinitySplitLocationProvider

2019-07-05 Thread Peter Vary (JIRA)


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

Peter Vary updated HIVE-21910:
--
Attachment: HIVE-21910.7.patch

> Multiple target location generation in HostAffinitySplitLocationProvider
> 
>
> Key: HIVE-21910
> URL: https://issues.apache.org/jira/browse/HIVE-21910
> Project: Hive
>  Issue Type: Sub-task
>  Components: llap
>Reporter: Peter Vary
>Assignee: Peter Vary
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-21910.2.patch, HIVE-21910.3.patch, 
> HIVE-21910.4.patch, HIVE-21910.5.patch, HIVE-21910.6.patch, 
> HIVE-21910.7.patch, HIVE-21910.patch
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> We need to generate multiple target locations by 
> HostAffinitySplitLocationProvider, so we will have deterministic fallback 
> nodes in case the target node is disabled



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2019-07-05 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.04.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
>
>
> 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.3#76005)


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

2019-07-05 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
>
>
> 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.3#76005)


[jira] [Commented] (HIVE-21947) Move Materialized View Update under DDL

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21947:


| (/) *{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 
26s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
42s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
0s{color} | {color:blue} ql in master has 2253 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
1s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m  
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
42s{color} | {color:green} ql: The patch generated 0 new + 502 unchanged - 7 
fixed = 502 total (was 509) {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 
11s{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 
14s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 38s{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-17866/dev-support/hive-personality.sh
 |
| git revision | master / 3223bda |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17866/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Move Materialized View Update under DDL
> ---
>
> Key: HIVE-21947
> URL: https://issues.apache.org/jira/browse/HIVE-21947
> 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, refactor-ddl
> Fix For: 4.0.0
>
> Attachments: HIVE-21947.01.patch, HIVE-21947.02.patch, 
> HIVE-21947.02.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> MaterializedViewDesc is not part of the DDL framework, it has it's own task, 
> which defines itself as DDL. They should be moved to the framework.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An commented on HIVE-21943:
---

[~Rajkumar Singh] Could you please review this patch?

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An updated HIVE-21943:
--
Fix Version/s: 3.1.2

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Priority: Major
> Fix For: 3.1.2
>
> Attachments: HIVE-21943.patch.1
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (HIVE-21943) Why do we not have audit log in HiveServer2?

2019-07-05 Thread Hui An (JIRA)


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

Hui An updated HIVE-21943:
--
Attachment: HIVE-21943.patch.1

> Why do we not have audit log in HiveServer2?
> 
>
> Key: HIVE-21943
> URL: https://issues.apache.org/jira/browse/HIVE-21943
> Project: Hive
>  Issue Type: Improvement
>Reporter: Hui An
>Priority: Major
> Attachments: HIVE-21943.patch.1
>
>
> Currently, we have audit log in the metastore( see 
> [HIVE-1948|https://issues.apache.org/jira/browse/HIVE-1948]), which provides 
> us useful info, like metadata operations, ip address, etc. But when we use 
> HS2 to connect HMS, all operations would assoicate with HS2 ip address, not 
> actual user's ip address. This could cause difficult problems when we want to 
> locate user's ip address. So I am thinking if we could add audit log in the 
> HS2 too?
> We could add much infomation in the audit log of HS2, like username, 
> ipAddress, queryId, queryStr, etc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21951) Llap query on external table with header or footer returns incorrect row count.

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21951:




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

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

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 16361 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.metastore.TestMetastoreHousekeepingLeaderEmptyConfig.testHouseKeepingThreadExistence
 (batchId=242)
{noformat}

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

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: 12973685 - PreCommit-HIVE-Build

> Llap query on external table with header or footer returns incorrect row 
> count.
> ---
>
> Key: HIVE-21951
> URL: https://issues.apache.org/jira/browse/HIVE-21951
> Project: Hive
>  Issue Type: Bug
>  Components: llap, Query Processor
>Affects Versions: 2.4.0, 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Sankar Hariappan
>Priority: Major
> Attachments: HIVE-21951.01.patch, HIVE-21951.02.patch
>
>
> Create a table with header and footer as follows.
> {code}
> CREATE EXTERNAL TABLE IF NOT EXISTS externaltableOpenCSV (eid int, name 
> String, salary String, destination String)
>  COMMENT 'Employee details'
>  ROW FORMAT SERDE 'org.apache.hadoop.hive.serde2.OpenCSVSerde'
>  STORED AS TEXTFILE
>  LOCATION '/externaltableOpenCSV'
>  tblproperties ("skip.header.line.count"="1", "skip.footer.line.count"="2");
> {code}
> Now, query on this table returns incorrect row count as header/footer are not 
> skipped.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HIVE-21951) Llap query on external table with header or footer returns incorrect row count.

2019-07-05 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-21951:


| (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 
46s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
10s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
55s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m  
8s{color} | {color:blue} ql in master has 2253 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
46s{color} | {color:blue} llap-server in master has 83 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 
27s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m 
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m 
29s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
40s{color} | {color:red} ql: The patch generated 3 new + 146 unchanged - 0 
fixed = 149 total (was 146) {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}  5m 
13s{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} 29m 35s{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-17865/dev-support/hive-personality.sh
 |
| git revision | master / 3223bda |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17865/yetus/diff-checkstyle-ql.txt
 |
| modules | C: ql llap-server U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-17865/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Llap query on external table with header or footer returns incorrect row 
> count.
> ---
>
> Key: HIVE-21951
> URL: https://issues.apache.org/jira/browse/HIVE-21951
> Project: Hive
>  Issue Type: Bug
>  Components: llap, Query Processor
>Affects Versions: 2.4.0, 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Sankar Hariappan
>Priority: Major
> Attachments: HIVE-21951.01.patch, HIVE-21951.02.patch
>
>
> Create a table with header and footer as follows.
> {code}
> CREATE EXTERNAL TABLE IF NOT EXISTS externaltableOpenCSV (eid int, name 
> String, salary String, destination String)
>  COMMENT 'Employee details'
>  ROW FORMAT SERDE 'org.apache.hadoop.hive.serde2.OpenCSVSerde'
>  STORED AS TEXTFILE
>  LOCATION '/externaltableOpenCSV'
>  tblproperties ("skip.header.line.count"="1", "skip.footer.line.count"="2");
> {code}
> Now, query on this table returns incorrect row count as header/footer are not 
>