[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-11-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HIVE-20542:
---

Github user ashutosh-bapat closed the pull request at:

https://github.com/apache/hive/pull/445


> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Fix For: 4.0.0
>
> Attachments: HIVE-20542.01.patch, HIVE-20542.02, HIVE-20542.03, 
> HIVE-20542.04
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-23 Thread Sankar Hariappan (JIRA)


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

Sankar Hariappan commented on HIVE-20542:
-

+1

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch, HIVE-20542.02, HIVE-20542.03, 
> HIVE-20542.04
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-22 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12944980/HIVE-20542.04

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

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

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

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

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch, HIVE-20542.02, HIVE-20542.03, 
> HIVE-20542.04
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-22 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
42s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m 
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
26s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  2m 
22s{color} | {color:blue} standalone-metastore/metastore-common in master has 
28 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 1 extant 
Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
37s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  3m 
46s{color} | {color:blue} ql in master has 2317 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  1m  
4s{color} | {color:blue} standalone-metastore/metastore-server in master has 
181 extant Findbugs warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
39s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
36s{color} | {color:red} hive-unit in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  3m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
25s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch has 4 line(s) that end in whitespace. Use git 
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply 
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  8m 
38s{color} | {color:green} the patch passed {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:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
13s{color} | {color:red} The patch generated 2 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 46m  7s{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.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-14605/dev-support/hive-personality.sh
 |
| git revision | master / b4302bb |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| mvninstall | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-14605/yetus/patch-mvninstall-itests_hive-unit.txt
 |
| whitespace | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-14605/yetus/whitespace-eol.txt
 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-14605/yetus/patch-asflicense-problems.txt
 |
| modules | C: standalone-metastore/metastore-common hcatalog/server-extensions 
itests/hcatalog-unit itests/hive-unit ql standalone-metastore/metastore-server 
U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-14605/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Incremental REPL DUMP progress information log message is incorrect.
> 
>
>   

[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-19 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12944753/HIVE-20542.03

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

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

[druidmini_dynamic_partition.q,druidmini_test_ts.q,druidmini_expressions.q,druidmini_test_alter.q,druidmini_test_insert.q]
{noformat}

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

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

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch, HIVE-20542.02, HIVE-20542.03
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-19 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:


| (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  
5s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  9m 
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  4m  
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
52s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  3m  
7s{color} | {color:blue} standalone-metastore/metastore-common in master has 28 
extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
33s{color} | {color:blue} hcatalog/server-extensions in master has 1 extant 
Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
50s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  4m 
44s{color} | {color:blue} ql in master has 2318 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  1m 
17s{color} | {color:blue} standalone-metastore/metastore-server in master has 
182 extant Findbugs warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  3m 
32s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
48s{color} | {color:red} hive-unit in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  4m  
5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  4m  
5s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
14s{color} | {color:red} itests/hcatalog-unit: The patch generated 6 new + 16 
unchanged - 0 fixed = 22 total (was 16) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
20s{color} | {color:red} itests/hive-unit: The patch generated 2 new + 74 
unchanged - 0 fixed = 76 total (was 74) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch has 4 line(s) that end in whitespace. Use git 
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply 
{color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch 1 line(s) with tabs. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  1m 
28s{color} | {color:red} standalone-metastore/metastore-server generated 1 new 
+ 182 unchanged - 0 fixed = 183 total (was 182) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  3m 
26s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
15s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 57m 35s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:standalone-metastore/metastore-server |
|  |  
org.apache.hadoop.hive.metastore.ObjectStore.getNotificationEventsCount(NotificationEventsCountRequest)
 invokes inefficient new Long(long) constructor; use Long.valueOf(long) instead 
 At ObjectStore.java:constructor; use Long.valueOf(long) instead  At 
ObjectStore.java:[line 10270] |
\\
\\
|| 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.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-14579/dev-support/hive-personality.sh
 |
| git revision | master / 4a7de47 |
| 

[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-19 Thread Ashutosh Bapat (JIRA)


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

Ashutosh Bapat commented on HIVE-20542:
---

[~sankarh], I have updated the pull request addressing your comments as well as 
the comments by Hive-QA.

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch, HIVE-20542.02, HIVE-20542.03
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-16 Thread Ashutosh Bapat (JIRA)


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

Ashutosh Bapat commented on HIVE-20542:
---

[~sankarh], replied to your comments in PR. Once we agree on the comments, I 
will provide an updated patch.

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch, HIVE-20542.02
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-12 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12943360/HIVE-20542.02

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

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

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

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

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch, HIVE-20542.02
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-12 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
46s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  8m 
 1s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
28s{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 
28 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
30s{color} | {color:blue} hcatalog/server-extensions in master has 1 extant 
Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m 
37s{color} | {color:blue} itests/hive-unit in master has 2 extant Findbugs 
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  3m 
55s{color} | {color:blue} ql in master has 2318 extant Findbugs warnings. 
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  1m  
8s{color} | {color:blue} standalone-metastore/metastore-server in master has 
182 extant Findbugs warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  3m  
1s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
41s{color} | {color:red} hive-unit in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m 
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  3m 
25s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
12s{color} | {color:red} itests/hcatalog-unit: The patch generated 6 new + 16 
unchanged - 0 fixed = 22 total (was 16) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
17s{color} | {color:red} itests/hive-unit: The patch generated 2 new + 74 
unchanged - 0 fixed = 76 total (was 74) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
39s{color} | {color:red} ql: The patch generated 2 new + 22 unchanged - 0 fixed 
= 24 total (was 22) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch has 4 line(s) that end in whitespace. Use git 
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply 
{color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red}  0m  
0s{color} | {color:red} The patch 1 line(s) with tabs. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red}  1m 
15s{color} | {color:red} standalone-metastore/metastore-server generated 1 new 
+ 182 unchanged - 0 fixed = 183 total (was 182) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
57s{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} 47m 52s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:standalone-metastore/metastore-server |
|  |  
org.apache.hadoop.hive.metastore.ObjectStore.getNotificationEventsCount(NotificationEventsCountRequest)
 invokes inefficient new Long(long) constructor; use Long.valueOf(long) instead 
 At ObjectStore.java:constructor; use Long.valueOf(long) instead  At 
ObjectStore.java:[line 10177] |
\\
\\
|| 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.36-1+deb8u1 (2016-09-03) x86_64 

[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-12 Thread Sankar Hariappan (JIRA)


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

Sankar Hariappan commented on HIVE-20542:
-

[~ashutosh.bapat]

Please find few comments posted in PR.

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch, HIVE-20542.02
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-10-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HIVE-20542:
---

GitHub user ashutosh-bapat opened a pull request:

https://github.com/apache/hive/pull/445

HIVE-20542

Changes for HIVE-20542. There are three separate commits, with each commit 
message explaining purpose of that commit. They all should be pulled together 
as a single commit into Apache hive repository. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ashutosh-bapat/hive hive20542

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/hive/pull/445.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #445


commit e76dd0d51662d5e1bc1890010b95d305f2505ea8
Author: Ashutosh Bapat 
Date:   2018-10-01T05:17:06Z

HIVE-20542: Insert NULL value for columns of NOTIFICATION_LOG for which 
values are not available

When no database is associated with an event we insert 'null' as database 
name in the metastore.
With this commit, we insert NULL as database name.

When no tablename is associated with an event we insert an empty string as 
table name in the
metastore. With this commit, we insert NULL as table name.

Even if a catalog name is associated with an event, addNotificationLog() 
doesn't insert catalog in
the metastore. With this commit we take care of that as well.

Ashutosh Bapat.

commit 31aee469baffb95641fb68f70a6bcaa0ca725d28
Author: Ashutosh Bapat 
Date:   2018-10-01T06:11:15Z

HIVE-20542: Modify query used to count the number of events to be 
replicated incrementally

The query used to count the events for a given incremental replication does 
not
1. Count event with NULL database, table or catalog names.
2. Does not consider toEventId and Limit for the given incremental 
replication.

Ashutosh Bapat.

commit d3a319c5fd347018572c13b40e1e8f7cdbe72050
Author: Ashutosh Bapat 
Date:   2018-10-04T04:08:44Z

HIVE-20644: Add tests for testing getNotificationEventsCount().

Ashutosh Bapat.




> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication, pull-request-available
> Attachments: HIVE-20542.01.patch
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-09-22 Thread Sankar Hariappan (JIRA)


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

Sankar Hariappan commented on HIVE-20542:
-

[~ashutosh.bapat], I've few comments
 # Need to use Java naming conventions for variables. Eg, dbname_val should be 
dbNameVal etc.
 # In addNotificationLoag method, seen similar issue where table name is set to 
" " (with single space) if it is not an input. Can we make it null if not 
available.
 # addNotificationLog can use event.getCatName()  to set catalogue name instead 
of always setting it to NULL.
 # getNotificationEventsCount can take an optional toEventId as it is allowed 
for incremental replication.
 # In  getNotificationEventsCount, can we use (dbName IS NULL) instead of 
(dbName == null)? Same with catalogName too.
 # Can add a unit test to verify if getNotificationEventsCount return proper 
count for events with db name and not.

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication
> Attachments: HIVE-20542.01.patch
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-09-21 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:




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

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

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

[druidmini_masking.q,druidmini_test1.q,druidkafkamini_basic.q,druidmini_joins.q,druid_timestamptz.q]
org.apache.hive.jdbc.miniHS2.TestHs2ConnectionMetricsBinary.testOpenConnectionMetrics
 (batchId=255)
{noformat}

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

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

This message is automatically generated.

ATTACHMENT ID: 12940588 - PreCommit-HIVE-Build

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication
> Attachments: HIVE-20542.01.patch
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-09-20 Thread Hive QA (JIRA)


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

Hive QA commented on HIVE-20542:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
34s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
18s{color} | {color:green} master passed {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:red}-1{color} | {color:red} findbugs {color} | {color:red}  0m 
13s{color} | {color:red} metastore-server in master failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
30s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
10s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
43s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
10s{color} | {color:red} hcatalog/server-extensions: The patch generated 5 new 
+ 3 unchanged - 0 fixed = 8 total (was 3) {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 
13s{color} | {color:red} metastore-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
29s{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} 13m 58s{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.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-13945/dev-support/hive-personality.sh
 |
| git revision | master / 3635c4d |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-13945/yetus/branch-findbugs-standalone-metastore_metastore-server.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-13945/yetus/diff-checkstyle-hcatalog_server-extensions.txt
 |
| findbugs | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-13945/yetus/patch-findbugs-standalone-metastore_metastore-server.txt
 |
| modules | C: hcatalog/server-extensions standalone-metastore/metastore-server 
U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-13945/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication
> Attachments: HIVE-20542.01.patch
>
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are 

[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-09-20 Thread Ashutosh Bapat (JIRA)


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

Ashutosh Bapat commented on HIVE-20542:
---

There are two issues
1. For every event, DbNotificationListner adds an event in the metastore using 
addNotificationLog() method. When the event has no database associated with it 
e.g. an open transaction event, this method inserts a row with dbname set to 
'null' instead of NULL. The fix is not to list DB_NAME column when inserting 
such events. The dbname is set to 'null' because of we try to use a null String 
object in concatenation. This seems to be an unintentional side-effect.

2. When reporting the estimated number of events in 
ObjectStore::getNotificationEventsCount() the query has equality condition on 
db_name and catname columns. The condition filters out all the events with NULL 
dbname and NULL catname, i.e. the events related to transactions. These events 
are important for replication since they need to be replicated to provide 
consistent data to the readers running in parallel to the load operation. The 
fix is to add a "OR is NULL clause on the DB_NAME and CAT_NAME".

Attached patch fixes both these issues.

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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


[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

2018-09-20 Thread Ashutosh Bapat (JIRA)


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

Ashutosh Bapat commented on HIVE-20542:
---

To reproduce the issue run
mvn test -DskipSparkTests -Dtest=TestReplicationScenarios#testIncrementalLoad
Check itests/hive-unit/target/tmp/log/hive.log for messages with 
eventsDumpProgress.

> Incremental REPL DUMP progress information log message is incorrect.
> 
>
> Key: HIVE-20542
> URL: https://issues.apache.org/jira/browse/HIVE-20542
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Affects Versions: 4.0.0, 3.2.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Minor
>  Labels: DR, Replication
>
> Incremental REPL DUMP have the progress information logged as 
> "eventsDumpProgress":"49/0".
> It should actually log the estimated number of events are denominator but it 
> is coming as 0 always.



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