[jira] [Commented] (HIVE-2055) Hive HBase Integration issue
[ https://issues.apache.org/jira/browse/HIVE-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13639889#comment-13639889 ] Giridharan Kesavan commented on HIVE-2055: -- [~ashutoshc] I dont think having a list of minimal jars is scalable solution. What if the next release of hbase depends of bunch of new jar's that are not part of the list that's provided in the bin/hive script? And, this would require fixing bin/hive scripts every time when hbase comes up with a new runtime dependency. As Nick pointed out hbase libs are appended to hive's classpath and hive libs still take the precedence. Hive HBase Integration issue Key: HIVE-2055 URL: https://issues.apache.org/jira/browse/HIVE-2055 Project: Hive Issue Type: Bug Components: HBase Handler Affects Versions: 0.10.0 Reporter: sajith v Attachments: 0001-HIVE-2055-include-hbase-dependencies-in-launch-scrip.patch, HIVE-2055.patch Created an external table in hive , which points to the HBase table. When tried to query a column using the column name in select clause got the following exception : ( java.lang.ClassNotFoundException: org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat), errorCode:12, SQLState:42000) -- 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] [Updated] (HIVE-2055) Hive HBase Integration issue
[ https://issues.apache.org/jira/browse/HIVE-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated HIVE-2055: - Attachment: HIVE-2055.patch HIVE-2055.patch fixes bin/hive script to include hbase and hcat lib's into the classpath Hive HBase Integration issue Key: HIVE-2055 URL: https://issues.apache.org/jira/browse/HIVE-2055 Project: Hive Issue Type: Bug Components: HBase Handler Reporter: sajith v Attachments: HIVE-2055.patch Created an external table in hive , which points to the HBase table. When tried to query a column using the column name in select clause got the following exception : ( java.lang.ClassNotFoundException: org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat), errorCode:12, SQLState:42000) -- 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] [Created] (HIVE-3520) ivysettings.xml does not let you override .m2/repository
Giridharan Kesavan created HIVE-3520: Summary: ivysettings.xml does not let you override .m2/repository Key: HIVE-3520 URL: https://issues.apache.org/jira/browse/HIVE-3520 Project: Hive Issue Type: Bug Components: Build Infrastructure Affects Versions: 0.9.0 Reporter: Giridharan Kesavan ivysettings.xml does not let you override .m2/repository. In other words repo.dir ivysetting should be an overridable property -- 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] [Created] (HIVE-3340) shims unit test failures fails further test progress
Giridharan Kesavan created HIVE-3340: Summary: shims unit test failures fails further test progress Key: HIVE-3340 URL: https://issues.apache.org/jira/browse/HIVE-3340 Project: Hive Issue Type: Bug Components: Build Infrastructure Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan enable failonerror flag so that unit test's can continue on even when shims unit test fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3340) shims unit test failures fails further test progress
[ https://issues.apache.org/jira/browse/HIVE-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated HIVE-3340: - Attachment: HIVE-3340.patch shims unit test failures fails further test progress Key: HIVE-3340 URL: https://issues.apache.org/jira/browse/HIVE-3340 Project: Hive Issue Type: Bug Components: Build Infrastructure Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan Attachments: HIVE-3340.patch enable failonerror flag so that unit test's can continue on even when shims unit test fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3340) shims unit test failures fails further test progress
[ https://issues.apache.org/jira/browse/HIVE-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated HIVE-3340: - Status: Patch Available (was: Open) shims unit test failures fails further test progress Key: HIVE-3340 URL: https://issues.apache.org/jira/browse/HIVE-3340 Project: Hive Issue Type: Bug Components: Build Infrastructure Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan Attachments: HIVE-3340.patch enable failonerror flag so that unit test's can continue on even when shims unit test fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3291) fix fs resolvers
[ https://issues.apache.org/jira/browse/HIVE-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan reassigned HIVE-3291: Assignee: Giridharan Kesavan fix fs resolvers - Key: HIVE-3291 URL: https://issues.apache.org/jira/browse/HIVE-3291 Project: Hive Issue Type: Bug Reporter: Giridharan Kesavan Assignee: Giridharan Kesavan shims module fails to compile when compiling hive against 1.0 using the fs resolvers as the force=true flag forces it to use the available version of hadoop. In a scenario where you want to build hadoop-1.0 and shims would still want to build against 20.2 and if you happen to use fs resolver ie -Dresolvers=true , fs resolvers would just use 1.0 of hadoop for shims and shims compilation will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3291) fix fs resolvers
Giridharan Kesavan created HIVE-3291: Summary: fix fs resolvers Key: HIVE-3291 URL: https://issues.apache.org/jira/browse/HIVE-3291 Project: Hive Issue Type: Bug Reporter: Giridharan Kesavan shims module fails to compile when compiling hive against 1.0 using the fs resolvers as the force=true flag forces it to use the available version of hadoop. In a scenario where you want to build hadoop-1.0 and shims would still want to build against 20.2 and if you happen to use fs resolver ie -Dresolvers=true , fs resolvers would just use 1.0 of hadoop for shims and shims compilation will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2243) Can't publish maven release artifacts to apache repository
[
https://issues.apache.org/jira/browse/HIVE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072919#comment-13072919
]
Giridharan Kesavan commented on HIVE-2243:
--
can someone try the following command with credentials in the .m2/settings.xml
and post the output? ( I don't have repo access to verify this).
{noformat}
ant clean maven-build maven-publish -Dmvn.publish.repo=staging -Dversion=0.8.0
{noformat}
This would publish the artifacts to the apache staging repo. we can delete them
post publishing.. by logging on to the repository.apache.org.
If the command works then I would submit a patch for gpg signing.
Can't publish maven release artifacts to apache repository
--
Key: HIVE-2243
URL: https://issues.apache.org/jira/browse/HIVE-2243
Project: Hive
Issue Type: Bug
Components: Build Infrastructure
Affects Versions: 0.7.1
Reporter: Carl Steinbach
Assignee: Giridharan Kesavan
So far I haven't been able to push the maven artifacts to the Apache release
repository. Here's the error I get:
{noformat}
% ant maven-publish -Dmvn.publish.repo=releases
...
maven-publish-artifact:
[artifact:install-provider] Installing provider:
org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
[artifact:deploy] Deploying to
https://repository.apache.org/content/repositories/releases
[artifact:deploy] Uploading:
org/apache/hive/hive-anttasks/0.7.1/hive-anttasks-0.7.1.jar to repository
apache.releases.https at
https://repository.apache.org/content/repositories/releases
[artifact:deploy] Transferring 9K from apache.releases.https
[artifact:deploy] An error has occurred while processing the Maven artifact
tasks.
[artifact:deploy] Diagnosis:
[artifact:deploy]
[artifact:deploy] Error deploying artifact
'org.apache.hive:hive-anttasks:jar': Error deploying artifact: Authorization
failed: Access denied to:
https://repository.apache.org/content/repositories/releases/org/apache/hive/hive-anttasks/0.7.1/hive-anttasks-0.7.1.jar
{noformat}
I get the same error when I try to publish to the staging repository.
I took another look at the Apache Publishing Maven Artifacts guide
(http://www.apache.org/dev/publishing-maven-artifacts.html) and think that
we're probably failing to include a couple fields that are required in the
pom files. It also looks like we should be pushing this to the staging
repository as opposed to the releases repository.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2243) Can't publish maven release artifacts to apache repository
[
https://issues.apache.org/jira/browse/HIVE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072175#comment-13072175
]
Giridharan Kesavan commented on HIVE-2243:
--
Hi Carl,
I can work on this jira if you are busy; let me know.
Can't publish maven release artifacts to apache repository
--
Key: HIVE-2243
URL: https://issues.apache.org/jira/browse/HIVE-2243
Project: Hive
Issue Type: Bug
Components: Build Infrastructure
Affects Versions: 0.7.1
Reporter: Carl Steinbach
Assignee: Carl Steinbach
So far I haven't been able to push the maven artifacts to the Apache release
repository. Here's the error I get:
{noformat}
% ant maven-publish -Dmvn.publish.repo=releases
...
maven-publish-artifact:
[artifact:install-provider] Installing provider:
org.apache.maven.wagon:wagon-http:jar:1.0-beta-2:runtime
[artifact:deploy] Deploying to
https://repository.apache.org/content/repositories/releases
[artifact:deploy] Uploading:
org/apache/hive/hive-anttasks/0.7.1/hive-anttasks-0.7.1.jar to repository
apache.releases.https at
https://repository.apache.org/content/repositories/releases
[artifact:deploy] Transferring 9K from apache.releases.https
[artifact:deploy] An error has occurred while processing the Maven artifact
tasks.
[artifact:deploy] Diagnosis:
[artifact:deploy]
[artifact:deploy] Error deploying artifact
'org.apache.hive:hive-anttasks:jar': Error deploying artifact: Authorization
failed: Access denied to:
https://repository.apache.org/content/repositories/releases/org/apache/hive/hive-anttasks/0.7.1/hive-anttasks-0.7.1.jar
{noformat}
I get the same error when I try to publish to the staging repository.
I took another look at the Apache Publishing Maven Artifacts guide
(http://www.apache.org/dev/publishing-maven-artifacts.html) and think that
we're probably failing to include a couple fields that are required in the
pom files. It also looks like we should be pushing this to the staging
repository as opposed to the releases repository.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2280) Publish daily hive snapshot builds to maven repo
[ https://issues.apache.org/jira/browse/HIVE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13072181#comment-13072181 ] Giridharan Kesavan commented on HIVE-2280: -- With the latest builds the hive artifacts are getting published to the apache snapshot repository. https://builds.apache.org/view/G-L/view/Hive/job/Hive-trunk-h0.21/855/console this jira can be closed. Publish daily hive snapshot builds to maven repo - Key: HIVE-2280 URL: https://issues.apache.org/jira/browse/HIVE-2280 Project: Hive Issue Type: Task Components: Build Infrastructure Reporter: Amareshwari Sriramadasu Publish daily hive snapshot builds to maven repo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2280) Publish daily hive snapshot builds to maven repo
[ https://issues.apache.org/jira/browse/HIVE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giridharan Kesavan updated HIVE-2280: - Component/s: Build Infrastructure Publish daily hive snapshot builds to maven repo - Key: HIVE-2280 URL: https://issues.apache.org/jira/browse/HIVE-2280 Project: Hive Issue Type: Task Components: Build Infrastructure Reporter: Amareshwari Sriramadasu Publish daily hive snapshot builds to maven repo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2280) Publish daily hive snapshot builds to maven repo
[ https://issues.apache.org/jira/browse/HIVE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064269#comment-13064269 ] Giridharan Kesavan commented on HIVE-2280: -- It looks like the hive build jobs are already setup to publish artifact to the repo, in the order of ant clean checkstyle tar binary test maven-build maven-publish But the builds are not publishing the artifacts due to test failures. Publish daily hive snapshot builds to maven repo - Key: HIVE-2280 URL: https://issues.apache.org/jira/browse/HIVE-2280 Project: Hive Issue Type: Task Components: Build Infrastructure Reporter: Amareshwari Sriramadasu Publish daily hive snapshot builds to maven repo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1095) Hive in Maven
[ https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13016462#comment-13016462 ] Giridharan Kesavan commented on HIVE-1095: -- since everyone is getting a 401 error (I tried with the hudson CI user as well and got the same 401). We need to check with the nexus admin to see if hive repo is available and ready for artifact publishing. Hive in Maven - Key: HIVE-1095 URL: https://issues.apache.org/jira/browse/HIVE-1095 Project: Hive Issue Type: Task Components: Build Infrastructure Affects Versions: 0.6.0 Reporter: Gerrit Jansen van Vuuren Priority: Minor Attachments: HIVE-1095-trunk.patch, HIVE-1095.v2.PATCH, HIVE-1095.v3.PATCH, HIVE-1095.v4.PATCH, HIVE-1095.v5.PATCH, hiveReleasedToMaven.tar.gz, make-maven.log Getting hive into maven main repositories Documentation on how to do this is on: http://maven.apache.org/guides/mini/guide-central-repository-upload.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1095) Hive in Maven
[ https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012641#comment-13012641 ] Giridharan Kesavan commented on HIVE-1095: -- @Carl Steinbach. I proposed this for the purpose of testing; For publishing to staging repo we don't have to go for a voting. If someone can confirm that this patch work by publishing artifacts to staging then the same committer can drop the artifact from the staging repo. And later someone can work on porting the patch to 0.7 branch. Hive in Maven - Key: HIVE-1095 URL: https://issues.apache.org/jira/browse/HIVE-1095 Project: Hive Issue Type: Task Components: Build Infrastructure Affects Versions: 0.6.0 Reporter: Gerrit Jansen van Vuuren Priority: Minor Attachments: HIVE-1095-trunk.patch, HIVE-1095.v2.PATCH, HIVE-1095.v3.PATCH, HIVE-1095.v4.PATCH, HIVE-1095.v5.PATCH, hiveReleasedToMaven.tar.gz Getting hive into maven main repositories Documentation on how to do this is on: http://maven.apache.org/guides/mini/guide-central-repository-upload.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1095) Hive in Maven
[
https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011514#comment-13011514
]
Giridharan Kesavan commented on HIVE-1095:
--
I got the same error as Amareshwari mentioned in the previous comment. But I
fixed locally by changing the dependency of make-pom target. ie made the
make-pom target to depend on check-ivy instead of ivy-init.
{code:xml}build-common.xml
- target name=make-pom if=ivy.present depends=ivy-init, jar
+ target name=make-pom if=ivy.present depends=check-ivy, jar
{code}
This seem to work fine..
About snapshot versioning:
I think we cannot publish snapshots to the staging/release repository.
Snapshots can only go the the snapshots repo.
We need to fix the version string so that we can publish to the staging/release
repo.
Hive in Maven
-
Key: HIVE-1095
URL: https://issues.apache.org/jira/browse/HIVE-1095
Project: Hive
Issue Type: Task
Components: Build Infrastructure
Affects Versions: 0.6.0
Reporter: Gerrit Jansen van Vuuren
Priority: Minor
Attachments: HIVE-1095-trunk.patch, HIVE-1095.v2.PATCH,
HIVE-1095.v3.PATCH, HIVE-1095.v4.PATCH, hiveReleasedToMaven.tar.gz
Getting hive into maven main repositories
Documentation on how to do this is on:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1095) Hive in Maven
[ https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011521#comment-13011521 ] Giridharan Kesavan commented on HIVE-1095: -- someone with hive committer access should try this to see if we are able to publish to the nexus staging repo. ant make-maven -Dversion=0.8.0 ant maven-publish -Dversion=0.8.0 Hive in Maven - Key: HIVE-1095 URL: https://issues.apache.org/jira/browse/HIVE-1095 Project: Hive Issue Type: Task Components: Build Infrastructure Affects Versions: 0.6.0 Reporter: Gerrit Jansen van Vuuren Priority: Minor Attachments: HIVE-1095-trunk.patch, HIVE-1095.v2.PATCH, HIVE-1095.v3.PATCH, HIVE-1095.v4.PATCH, hiveReleasedToMaven.tar.gz Getting hive into maven main repositories Documentation on how to do this is on: http://maven.apache.org/guides/mini/guide-central-repository-upload.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HIVE-1095) Hive in Maven
[ https://issues.apache.org/jira/browse/HIVE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13007344#comment-13007344 ] Giridharan Kesavan commented on HIVE-1095: -- v3 version of patch fails with a conflict on build-common.xml Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file build-common.xml.rej Hive in Maven - Key: HIVE-1095 URL: https://issues.apache.org/jira/browse/HIVE-1095 Project: Hive Issue Type: Task Components: Build Infrastructure Affects Versions: 0.6.0 Reporter: Gerrit Jansen van Vuuren Priority: Minor Attachments: HIVE-1095-trunk.patch, HIVE-1095.v2.PATCH, HIVE-1095.v3.PATCH, hiveReleasedToMaven.tar.gz Getting hive into maven main repositories Documentation on how to do this is on: http://maven.apache.org/guides/mini/guide-central-repository-upload.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
