[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2014-03-03 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917841#comment-13917841
 ] 

Hive QA commented on HIVE-3938:
---



{color:red}Overall{color}: -1 at least one tests failed

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

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 5208 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testNegativeCliDriver_minimr_broken_pipe
{noformat}

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1598/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1598/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
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: 12632169

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0, 0.11.0, 0.12.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.patch, 
 Hive-3938-Support_for_Multi-table-insert.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2014-03-03 Thread Mithun Radhakrishnan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918140#comment-13918140
 ] 

Mithun Radhakrishnan commented on HIVE-3938:


With the updated patch, TestNegativeMinimrCliDriver has a failure.

This looks unrelated, but would someone please confirm?

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0, 0.11.0, 0.12.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.patch, 
 Hive-3938-Support_for_Multi-table-insert.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2014-03-02 Thread Hive QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917525#comment-13917525
 ] 

Hive QA commented on HIVE-3938:
---



{color:red}Overall{color}: -1 no tests executed

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

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1593/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1593/console

Messages:
{noformat}
 This message was trimmed, see log for full details 
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/src/main/resources
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (define-classpath) @ 
hive-hcatalog-it-unit ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
hive-hcatalog-it-unit ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
hive-hcatalog-it-unit ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/src/test/resources
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (setup-test-dirs) @ 
hive-hcatalog-it-unit ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/tmp
[mkdir] Created dir: 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/warehouse
[mkdir] Created dir: 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/tmp/conf
 [copy] Copying 5 files to 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/tmp/conf
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
hive-hcatalog-it-unit ---
[INFO] Compiling 7 source files to 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/test-classes
[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.16:test (default-test) @ 
hive-hcatalog-it-unit ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ hive-hcatalog-it-unit ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/hive-hcatalog-it-unit-0.13.0-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.2:test-jar (default) @ hive-hcatalog-it-unit ---
[INFO] Building jar: 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/hive-hcatalog-it-unit-0.13.0-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ 
hive-hcatalog-it-unit ---
[INFO] Installing 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/hive-hcatalog-it-unit-0.13.0-SNAPSHOT.jar
 to 
/data/hive-ptest/working/maven/org/apache/hive/hive-hcatalog-it-unit/0.13.0-SNAPSHOT/hive-hcatalog-it-unit-0.13.0-SNAPSHOT.jar
[INFO] Installing 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/pom.xml 
to 
/data/hive-ptest/working/maven/org/apache/hive/hive-hcatalog-it-unit/0.13.0-SNAPSHOT/hive-hcatalog-it-unit-0.13.0-SNAPSHOT.pom
[INFO] Installing 
/data/hive-ptest/working/apache-svn-trunk-source/itests/hcatalog-unit/target/hive-hcatalog-it-unit-0.13.0-SNAPSHOT-tests.jar
 to 
/data/hive-ptest/working/maven/org/apache/hive/hive-hcatalog-it-unit/0.13.0-SNAPSHOT/hive-hcatalog-it-unit-0.13.0-SNAPSHOT-tests.jar
[INFO] 
[INFO] 
[INFO] Building Hive Integration - Testing Utilities 0.13.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hive-it-util ---
[INFO] Deleting /data/hive-ptest/working/apache-svn-trunk-source/itests/util 
(includes = [datanucleus.log, derby.log], excludes = [])
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
hive-it-util ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/data/hive-ptest/working/apache-svn-trunk-source/itests/util/src/main/resources
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (define-classpath) @ hive-it-util ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile 

[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2014-02-28 Thread Ashutosh Chauhan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13915999#comment-13915999
 ] 

Ashutosh Chauhan commented on HIVE-3938:


+1
 [~mithun] Can you re-upload the patch with name HIVE-3938.patch That way Hive 
QA will pick it up to run test suite.

One thing which is disturbing in current code base is (which existed even 
before this patch) is we are running these pre and post hooks within 
transaction. General wisdom is to never make calls to foreign system (like 
MsgBus in our case) from within database transaction. We should try to improve 
this, though thats probably a topic for another jira.

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0, 0.11.0, 0.12.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.2.patch, 
 Hive-3938-Support_for_Multi-table-insert.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-12-09 Thread Mithun Radhakrishnan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13843561#comment-13843561
 ] 

Mithun Radhakrishnan commented on HIVE-3938:


Sorry for the delay on this, Ashutosh. I should be able to rebase this patch 
next week.

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0, 0.11.0, 0.12.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: Hive-3938-Support_for_Multi-table-insert.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-04-17 Thread Mithun Radhakrishnan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13634349#comment-13634349
 ] 

Mithun Radhakrishnan commented on HIVE-3938:


Sorry for the delay. I've only just gotten back to fixing this. I've 
incorporated your suggestions. I'm trying to get the tests going. Will update 
shortly.

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-04-17 Thread Mithun Radhakrishnan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13634523#comment-13634523
 ] 

Mithun Radhakrishnan commented on HIVE-3938:


Ok, Dilip's comment about support for multi-table inserts poses a dilemma. 

Thus far, HiveMetaStore::add_partitions_core() seems to have assumed (at least 
in part) that all the parts belong to the same table (evidenced by the 
logInfo() line). If one might call add_partitions() with parts in different 
tables, should they all be considered to be part of a single atomic set? Or 
ought I to categorize them (per table) and send separate Events out?

I'm inclined to do the former (because you retain the ability to break the 
partition-sets up downstream), but I'm open to suggestions. 

(+ [~ashutoshc], who wrote the initial version of this.)

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-03-27 Thread Mithun Radhakrishnan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615884#comment-13615884
 ] 

Mithun Radhakrishnan commented on HIVE-3938:


Thanks for the review, Sush. :]

Dilip, Namit, et al, would you guys please comment? It'd be great if a 
committer could review, too.

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-03-27 Thread Mithun Radhakrishnan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615891#comment-13615891
 ] 

Mithun Radhakrishnan commented on HIVE-3938:


Yikes! I missed the notification from the review. Thanks for reviewing. Please 
ignore previous comment.

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-03-19 Thread Dilip Joseph (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606112#comment-13606112
 ] 

Dilip Joseph commented on HIVE-3938:


[~mithun] I can review it.  Could you please upload another review and send the 
URL.  Thanks.

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-03-19 Thread Sushanth Sowmyan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13607162#comment-13607162
 ] 

Sushanth Sowmyan commented on HIVE-3938:


Looks good to me. +1 (non-binding)

One thing I will note, however, for the sake of completeness, in that this is a 
behaviour change, is that this implementation of taking the common table out of 
the partitions means that add_partitions will only work if all the partitions 
in parts are in the same table. The earlier implementation allowed a mixed 
group of partitions. I think this is better though, and atomically adding 
arbitrary groups of partitions atomically if they're not related is a recipe 
for other usage problems.

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (HIVE-3938) Hive MetaStore should send a single AddPartitionEvent for atomically added partition-set.

2013-03-18 Thread Mithun Radhakrishnan (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13605924#comment-13605924
 ] 

Mithun Radhakrishnan commented on HIVE-3938:


[~namitjain], [~cwsteinbach], [~dilipjoseph], could I bother one of you to 
review this fix?

We'd like to get this into branch-10 (apart from trunk). (That implies getting 
HIVE-4004 into branch-10 as well.) We'd appreciate the help.

Mithun

 Hive MetaStore should send a single AddPartitionEvent for atomically added 
 partition-set.
 -

 Key: HIVE-3938
 URL: https://issues.apache.org/jira/browse/HIVE-3938
 Project: Hive
  Issue Type: Bug
  Components: Metastore
Affects Versions: 0.10.0
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
 Attachments: HIVE-3938.trunk.patch


 HiveMetaStore::add_partitions() currently adds all partitions specified in 
 one call using a single meta-store transaction. This acts correctly. However, 
 there's one AddPartitionEvent created per partition specified.
 Ideally, the set of partitions added atomically can be communicated using a 
 single AddPartitionEvent, such that they are consumed together.
 I'll post a patch that does this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira