[
https://issues.apache.org/jira/browse/BIGTOP-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Grover updated BIGTOP-920:
-------------------------------
Attachment: BIGTOP-920.1.patch-0.3.1
Cos, sorry about the delay in response. The patch didn't apply cleanly, it had
minor conflicts plus the version numbers had to be changed to 0.3.1-incubating
instead of 0.6.0.
I am attaching the patch for branch 0.3.1. As I said before I wasn't able to
test this because the artifacts haven't been built for a while. Moreover, the
command {{mvn -f bigtop-tests/test-artifacts/pom.xml clean install}}
gave me the following error on 0.3.1 trunk. I tried a clean build of
{{bigtop-test-framework}} before but that didn't help either.
{code}
ERROR] Failed to execute goal on project bigtop-smokes: Could not resolve
dependencies for project
org.apache.bigtop.itest:bigtop-smokes:pom:0.3.1-incubating-SNAPSHOT: Failed to
collect dependencies for
[org.apache.bigtop.itest:itest-common:jar:0.3.1-incubating-SNAPSHOT (compile)]:
Failed to read artifact descriptor for
org.apache.bigtop.itest:itest-common:jar:0.3.1-incubating-SNAPSHOT: Failure to
find org.apache.bigtop:bigtop:pom:0.3.1-incubating-SNAPSHOT in
http://repository.apache.org/snapshots was cached in the local repository,
resolution will not be reattempted until the update interval of
apache.snapshots has elapsed or updates are forced -> [Help 1]
{code}
In any case, the point is that I wasn't able to test much on 0.3.1; however,
this patch is very similar to the trunk patch so this would be a very good
starting point when 0.3.1 stabilizes.
> Add HCatalog tests
> ------------------
>
> Key: BIGTOP-920
> URL: https://issues.apache.org/jira/browse/BIGTOP-920
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.5.0
> Reporter: Konstantin Boudnik
> Assignee: Mark Grover
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: BIGTOP-920.1.patch, BIGTOP-920.1.patch-0.3.1
>
>
> Let's have some tests for HCatalog
--
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
