[jira] [Commented] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache

2018-07-12 Thread Eugene Koifman (JIRA) 


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

Eugene Koifman commented on HIVE-19387:
---

branch-3 run of unrelated HIVE-20100 has the same set of failures

> Truncate table for Acid tables conflicts with ResultSet cache
> -
>
> Key: HIVE-19387
> URL: https://issues.apache.org/jira/browse/HIVE-19387
> Project: Hive
>  Issue Type: New Feature
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Blocker
> Attachments: HIVE-19387.01-branch-3.patch, HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T 
> where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating 
> Snapshot Isolation semantics.
> This makes sense for specific partition or unpartitioned table.  What about 
> "Truncate T" where T is partitioned?  Is the expectation to wipe out all 
> partition info or to make each partition empty?



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

[jira] [Commented] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache

2018-07-12 Thread Hive QA (JIRA) 


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

Hive QA commented on HIVE-19387:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12931219/HIVE-19387.01-branch-3.patch

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

{color:red}ERROR:{color} -1 due to 8 failed/errored test(s), 14397 tests 
executed
*Failed tests:*
{noformat}
TestBeeLineDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=258)
TestDummy - did not produce a TEST-*.xml file (likely timed out) (batchId=258)
TestMiniDruidCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=258)
TestMiniDruidKafkaCliDriver - did not produce a TEST-*.xml file (likely timed 
out) (batchId=258)
TestTezPerfCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=258)
org.apache.hadoop.hive.ql.TestWarehouseExternalDir.testManagedPaths 
(batchId=235)
org.apache.hive.service.TestHS2ImpersonationWithRemoteMS.testImpersonation 
(batchId=243)
org.apache.hive.spark.client.rpc.TestRpc.testServerPort (batchId=310)
{noformat}

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

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

This message is automatically generated.

ATTACHMENT ID: 12931219 - PreCommit-HIVE-Build

> Truncate table for Acid tables conflicts with ResultSet cache
> -
>
> Key: HIVE-19387
> URL: https://issues.apache.org/jira/browse/HIVE-19387
> Project: Hive
>  Issue Type: New Feature
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Blocker
> Attachments: HIVE-19387.01-branch-3.patch, HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T 
> where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating 
> Snapshot Isolation semantics.
> This makes sense for specific partition or unpartitioned table.  What about 
> "Truncate T" where T is partitioned?  Is the expectation to wipe out all 
> partition info or to make each partition empty?



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

[jira] [Commented] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache

2018-07-12 Thread Hive QA (JIRA) 


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

Hive QA commented on HIVE-19387:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  9s{color} 
| {color:red} 
/data/hiveptest/logs/PreCommit-HIVE-Build-12553/patches/PreCommit-HIVE-Build-12553.patch
 does not apply to master. Rebase required? Wrong Branch? See 
http://cwiki.apache.org/confluence/display/Hive/HowToContribute for help. 
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-12553/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Truncate table for Acid tables conflicts with ResultSet cache
> -
>
> Key: HIVE-19387
> URL: https://issues.apache.org/jira/browse/HIVE-19387
> Project: Hive
>  Issue Type: New Feature
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Blocker
> Attachments: HIVE-19387.01-branch-3.patch, HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T 
> where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating 
> Snapshot Isolation semantics.
> This makes sense for specific partition or unpartitioned table.  What about 
> "Truncate T" where T is partitioned?  Is the expectation to wipe out all 
> partition info or to make each partition empty?



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

[jira] [Commented] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache

2018-07-11 Thread Eugene Koifman (JIRA) 


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

Eugene Koifman commented on HIVE-19387:
---

pushed to master
thanks Jason for the review

> Truncate table for Acid tables conflicts with ResultSet cache
> -
>
> Key: HIVE-19387
> URL: https://issues.apache.org/jira/browse/HIVE-19387
> Project: Hive
>  Issue Type: New Feature
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Blocker
> Attachments: HIVE-19387.01-branch-3.patch, HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T 
> where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating 
> Snapshot Isolation semantics.
> This makes sense for specific partition or unpartitioned table.  What about 
> "Truncate T" where T is partitioned?  Is the expectation to wipe out all 
> partition info or to make each partition empty?



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

[jira] [Commented] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache

2018-07-11 Thread Hive QA (JIRA) 


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

Hive QA commented on HIVE-19387:




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

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

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

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

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

> Truncate table for Acid tables conflicts with ResultSet cache
> -
>
> Key: HIVE-19387
> URL: https://issues.apache.org/jira/browse/HIVE-19387
> Project: Hive
>  Issue Type: New Feature
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Blocker
> Attachments: HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T 
> where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating 
> Snapshot Isolation semantics.
> This makes sense for specific partition or unpartitioned table.  What about 
> "Truncate T" where T is partitioned?  Is the expectation to wipe out all 
> partition info or to make each partition empty?



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

[jira] [Commented] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache

2018-07-11 Thread Hive QA (JIRA) 


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

Hive QA commented on HIVE-19387:


| (/) *{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 
46s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
2s{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}  3m 
49s{color} | {color:blue} ql in master has 2287 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
56s{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}  1m 
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  1m  
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
41s{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  
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
56s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
12s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 23m 50s{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-12536/dev-support/hive-personality.sh
 |
| git revision | master / 385a26a |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: ql itests U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-12536/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Truncate table for Acid tables conflicts with ResultSet cache
> -
>
> Key: HIVE-19387
> URL: https://issues.apache.org/jira/browse/HIVE-19387
> Project: Hive
>  Issue Type: New Feature
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Blocker
> Attachments: HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T 
> where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating 
> Snapshot Isolation semantics.
> This makes sense for specific partition or unpartitioned table.  What about 
> "Truncate T" where T is partitioned?  Is the expectation to wipe out all 
> partition info or to make each partition empty?



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

[jira] [Commented] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache

2018-07-11 Thread Jason Dere (JIRA) 


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

Jason Dere commented on HIVE-19387:
---

+1

> Truncate table for Acid tables conflicts with ResultSet cache
> -
>
> Key: HIVE-19387
> URL: https://issues.apache.org/jira/browse/HIVE-19387
> Project: Hive
>  Issue Type: New Feature
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Blocker
> Attachments: HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T 
> where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating 
> Snapshot Isolation semantics.
> This makes sense for specific partition or unpartitioned table.  What about 
> "Truncate T" where T is partitioned?  Is the expectation to wipe out all 
> partition info or to make each partition empty?



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