[jira] [Commented] (ATLAS-455) Build failure in Hive integration tests
[ https://issues.apache.org/jira/browse/ATLAS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114764#comment-15114764 ] Shwetha G S commented on ATLAS-455: --- Can you attach the application.log. It should be in webapp/target/logs or addons/hive-bridge/target/logs > Build failure in Hive integration tests > --- > > Key: ATLAS-455 > URL: https://issues.apache.org/jira/browse/ATLAS-455 > Project: Atlas > Issue Type: Bug >Affects Versions: trunk >Reporter: Nigel Jones > > With a latest git pull from ~1400 UTC , plus the ATLAS-439 patch to fix a > webapp build failure, I am now seeing the Hive integration tests fail. This > is in a pretty clean environment, centos 7.1 > Tests run: 12, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 177.625 sec > <<< FAILURE! - in org.apache.atlas.hive.hook > .HiveHookIT > testAlterTableRename(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed: > 27.741 sec <<< FAILURE! > java.lang.Exception: Waiting timed out after 2000 msec > at org.apache.atlas.hive.hook.HiveHookIT.waitFor(HiveHookIT.java:427) > at > org.apache.atlas.hive.hook.HiveHookIT.assertEntityIsRegistered(HiveHookIT.java:342) > at > org.apache.atlas.hive.hook.HiveHookIT.assertTableIsRegistered(HiveHookIT.java:320) > at > org.apache.atlas.hive.hook.HiveHookIT.testAlterTableRename(HiveHookIT.java:269) > testAlterViewRename(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed: > 10.27 sec <<< FAILURE! > java.lang.Exception: Waiting timed out after 2000 msec > at org.apache.atlas.hive.hook.HiveHookIT.waitFor(HiveHookIT.java:427) > at > org.apache.atlas.hive.hook.HiveHookIT.assertEntityIsRegistered(HiveHookIT.java:342) > at > org.apache.atlas.hive.hook.HiveHookIT.assertTableIsRegistered(HiveHookIT.java:320) > at > org.apache.atlas.hive.hook.HiveHookIT.testAlterViewRename(HiveHookIT.java:284) > testCTAS(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed: 13.085 sec > <<< FAILURE! > java.lang.Exception: Waiting timed out after 2000 msec > at org.apache.atlas.hive.hook.HiveHookIT.waitFor(HiveHookIT.java:427) > at > org.apache.atlas.hive.hook.HiveHookIT.assertEntityIsRegistered(HiveHookIT.java:342) > at > org.apache.atlas.hive.hook.HiveHookIT.assertProcessIsRegistered(HiveHookIT.java:297) > at org.apache.atlas.hive.hook.HiveHookIT.testCTAS(HiveHookIT.java:171) > testCreateView(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed: 4.736 > sec <<< FAILURE! > java.lang.Exception: Waiting timed out after 2000 msec > at org.apache.atlas.hive.hook.HiveHookIT.waitFor(HiveHookIT.java:427) > at > org.apache.atlas.hive.hook.HiveHookIT.assertEntityIsRegistered(HiveHookIT.java:342) > at > org.apache.atlas.hive.hook.HiveHookIT.assertProcessIsRegistered(HiveHookIT.java:297) > at > org.apache.atlas.hive.hook.HiveHookIT.testCreateView(HiveHookIT.java:182) > testInsert(org.apache.atlas.hive.hook.HiveHookIT) Time elapsed: 10.654 sec > <<< FAILURE! > java.lang.Exception: Waiting timed out after 2000 msec > at org.apache.atlas.hive.hook.HiveHookIT.waitFor(HiveHookIT.java:427) > at > org.apache.atlas.hive.hook.HiveHookIT.assertEntityIsRegistered(HiveHookIT.java:342) > at > org.apache.atlas.hive.hook.HiveHookIT.assertProcessIsRegistered(HiveHookIT.java:297) > at > org.apache.atlas.hive.hook.HiveHookIT.testInsert(HiveHookIT.java:206) > Results : > Failed tests: > > HiveHookIT.testAlterTableRename:269->assertTableIsRegistered:320->assertEntityIsRegistered:342->waitFor:427 > > HiveHookIT.testAlterViewRename:284->assertTableIsRegistered:320->assertEntityIsRegistered:342->waitFor:427 > > HiveHookIT.testCTAS:171->assertProcessIsRegistered:297->assertEntityIsRegistered:342->waitFor:427 > > HiveHookIT.testCreateView:182->assertProcessIsRegistered:297->assertEntityIsRegistered:342->waitFor:427 > > HiveHookIT.testInsert:206->assertProcessIsRegistered:297->assertEntityIsRegistered:342->waitFor:427 > Tests run: 12, Failures: 5, Errors: 0, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-388) UI : On creating Tag, the page to be reset for creating new Tag
[ https://issues.apache.org/jira/browse/ATLAS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-388: --- Attachment: ui-red-tag-name.png > UI : On creating Tag, the page to be reset for creating new Tag > --- > > Key: ATLAS-388 > URL: https://issues.apache.org/jira/browse/ATLAS-388 > Project: Atlas > Issue Type: Improvement >Reporter: Anilsg >Assignee: Anilsg > Attachments: ATLAS-388-v1.patch, ATLAS-388.patch, ui-red-tag-name.png > > > On create tag's (Traits) the form fields to be cleared for creating new Tag, > Currently it has to refreshed or navigated from other tab to create new one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-451) Doc: Fix few broken links due to Wiki words in Atlas documentation
[ https://issues.apache.org/jira/browse/ATLAS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114792#comment-15114792 ] Shwetha G S commented on ATLAS-451: --- Whenever we need links, we always specify explicit links. Instead of disabling every wikiword, can we disable wikiword links always. Looks like there are some plugins available for this > Doc: Fix few broken links due to Wiki words in Atlas documentation > -- > > Key: ATLAS-451 > URL: https://issues.apache.org/jira/browse/ATLAS-451 > Project: Atlas > Issue Type: Bug >Reporter: Hemanth Yamijala >Assignee: Sharmadha Sainath >Priority: Trivial > Labels: newbie > Attachments: ATLAS-451-v1.patch > > > There are a few missing links in Atlas documentation created due to not > escaping Wiki words. This is a ticket to clean them up. > http://atlas.incubator.apache.org/SingleQuery.html > http://atlas.incubator.apache.org/JdbcAccess.html > http://atlas.incubator.apache.org/WithPath.html > http://atlas.incubator.apache.org/SingleQueries.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-388) UI : On creating Tag, the page to be reset for creating new Tag
[ https://issues.apache.org/jira/browse/ATLAS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114767#comment-15114767 ] Hemanth Yamijala commented on ATLAS-388: A few comments: * The fields name and super types do get reset as expected. However, the background of the Tag Name text box and label gets highlighted in red as if it is in error. Please refer to ui_red_tag_name.png. This might confuse the end user from a UX perspective. * In the patch, the code to reset the fields is repeated at two places - on initialization and in the $scope.reset function definition. Would be good to extract a method and reuse from both places. This will help if the UI evolution leads to more fields that should be reset, etc. > UI : On creating Tag, the page to be reset for creating new Tag > --- > > Key: ATLAS-388 > URL: https://issues.apache.org/jira/browse/ATLAS-388 > Project: Atlas > Issue Type: Improvement >Reporter: Anilsg >Assignee: Anilsg > Attachments: ATLAS-388-v1.patch, ATLAS-388.patch, ui-red-tag-name.png > > > On create tag's (Traits) the form fields to be cleared for creating new Tag, > Currently it has to refreshed or navigated from other tab to create new one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-439) Investigate apache build failures
[ https://issues.apache.org/jira/browse/ATLAS-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114834#comment-15114834 ] Hemanth Yamijala commented on ATLAS-439: This looks good to me. With master and this patch, mvn clean verify is passing. Of course - there could still be timing related failures depending on environment, machine etc.. > Investigate apache build failures > - > > Key: ATLAS-439 > URL: https://issues.apache.org/jira/browse/ATLAS-439 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Fix For: trunk > > Attachments: ATLAS-439.patch > > > The latest code builds fine on the local machine. However, the builds have > been failing continuously at apache builds - > https://builds.apache.org/job/apache-atlas-nightly/159/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-136) Add trait API to org.apache.atlas.AtlasClient
[
https://issues.apache.org/jira/browse/ATLAS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rishabh Bhardwaj updated ATLAS-136:
---
Attachment: ATLAS-136-v7.patch
Updated the patch after resolving comments in the review request.
https://reviews.apache.org/r/42128/
> Add trait API to org.apache.atlas.AtlasClient
> -
>
> Key: ATLAS-136
> URL: https://issues.apache.org/jira/browse/ATLAS-136
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Vladimir Antonevich`
>Assignee: Rishabh Bhardwaj
> Fix For: trunk
>
> Attachments: ATLAS-136-v3.patch, ATLAS-136-v4.patch,
> ATLAS-136-v5.patch, ATLAS-136-v6.patch, ATLAS-136-v7.patch, ATLAS-136.patch,
> ATLAS-136.v2.patch, atlas.client.patch
>
>
> API to manipulate entity traits must be added to
> org.apache.atlas.AtlasClient. These should include methods to add/remove a
> trait POST/DELETE to /api/atlas/entities/{guid}/traits[/traitName], as
> supported by exposed entities resource
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ATLAS-439) Investigate apache build failures - EntityJerseyResourceIT.
[ https://issues.apache.org/jira/browse/ATLAS-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S updated ATLAS-439: -- Summary: Investigate apache build failures - EntityJerseyResourceIT. (was: Investigate apache build failures - ) > Investigate apache build failures - EntityJerseyResourceIT. > --- > > Key: ATLAS-439 > URL: https://issues.apache.org/jira/browse/ATLAS-439 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Shwetha G S >Assignee: Shwetha G S >Priority: Critical > Fix For: trunk > > Attachments: ATLAS-439.patch > > > The latest code builds fine on the local machine. However, the builds have > been failing continuously at apache builds - > https://builds.apache.org/job/apache-atlas-nightly/159/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-452) Exceptions while running HiveHookIT#testAlterTableRename
[
https://issues.apache.org/jira/browse/ATLAS-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated ATLAS-452:
--
Summary: Exceptions while running HiveHookIT#testAlterTableRename (was:
Exceptions while running HiveHookIT#testRenameTable)
> Exceptions while running HiveHookIT#testAlterTableRename
>
>
> Key: ATLAS-452
> URL: https://issues.apache.org/jira/browse/ATLAS-452
> Project: Atlas
> Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> {noformat}
> 27.0.0.1 - - [22/Jan/2016:06:08:54 +] "OPTIONS
> /api/atlas/discovery/search?query=hive_table+as+t+where+tableName+%3D+'tablehdj2zjk9bz',+db+where+name+%3D+'default'+and+clusterName+%3D+'test'+select+t=sshivalingamurthy
> HTTP/1.1" 200 - "-" "Java/1.7.0_79"
> 2016-01-22 11:38:54.720:WARN:oejs.ServletHandler:qtp127815766-153:
> /api/atlas/entities
> java.lang.IllegalArgumentException: Input String cannot be null cannot be null
> at org.apache.atlas.utils.ParamChecker.notNull(ParamChecker.java:40)
> at
> org.apache.atlas.web.util.Servlets.escapeJsonString(Servlets.java:146)
> at
> org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:125)
> at
> org.apache.atlas.web.util.Servlets.getErrorResponse(Servlets.java:107)
> at
> org.apache.atlas.web.resources.EntityResource.updateEntities(EntityResource.java:177)
> {noformat}
> {noformat}
> 2016-01-22 11:47:08,614 ERROR - [qtp1582368608-323 -
> ddb67cab-8e11-4434-9cb3-53d95fccc10a:] ~ Unable to persist entity instance
> (EntityResource:176)
> java.lang.NullPointerException
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.updateClassEdge(TypedInstanceToGraphMapper.java:567)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.addOrUpdateClassVertex(TypedInstanceToGraphMapper.java:513)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.addOrUpdateCollectionEntry(TypedInstanceToGraphMapper.java:470)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.mapArrayCollectionToVertex(TypedInstanceToGraphMapper.java:370)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.mapAttributesToVertex(TypedInstanceToGraphMapper.java:208)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.mapInstanceToVertex(TypedInstanceToGraphMapper.java:183)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.addOrUpdateAttributesAndTraits(TypedInstanceToGraphMapper.java:163)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.addOrUpdateAttributesAndTraits(TypedInstanceToGraphMapper.java:139)
> at
> org.apache.atlas.repository.graph.TypedInstanceToGraphMapper.mapTypedInstanceToGraph(TypedInstanceToGraphMapper.java:105)
> at
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.updateEntities(GraphBackedMetadataRepository.java:298)
> at
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
> at
> org.apache.atlas.services.DefaultMetadataService.updateEntities(DefaultMetadataService.java:384)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
