Nixon Rodrigues created ATLAS-1890:
--------------------------------------
Summary: IntegrationTest cases failing in
BaseResourceIT.waitForNotification method
Key: ATLAS-1890
URL: https://issues.apache.org/jira/browse/ATLAS-1890
Project: Atlas
Issue Type: Bug
Reporter: Nixon Rodrigues
Problem:-
This test cases are failing in BaseResourceIT.waitForNotification method.
In waitForNotification method it waits for certain Time for Kafka notification
of the entity created/update/deleted etc to read from KafkaTopic.
Currently for Integration tests in Atlas, a metadata server is running on port
31000 along berkely-db store and kafka/zookeeper for notifitication.
This Atlas services is used by All Integration tests that are running from
maven test suite.
Since testcases run independent of eachother and if they access shared like
kafka notification via consumer, the consumer will results different type of
results and also with some IO and timing issues.
{code}
testEntityDeduping(org.apache.atlas.web.integration.EntityJerseyResourceIT)
Time elapsed: 61.463 sec <<< FAILURE!
java.lang.Exception: Waiting timed out after 6000 msec
at
org.apache.atlas.web.integration.EntityJerseyResourceIT.testEntityDeduping(EntityJerseyResourceIT.java:221)
EntityV2JerseyResourceIT.testEntityDeduping:170->BaseResourceIT.waitForNotification:633->BaseResourceIT.waitFor:625
»
EntityNotificationIT.testDeleteEntity:108->BaseResourceIT.waitForNotification:633->BaseResourceIT.waitFor:625
»
{code}
The purpose of waitForNotification method is to valid if notifications reach
the Kafka topic.
I propose to remove this dependeny to check the entity created notification on
kafka topic from the above IntegrationTest.
The validation of created/update/deleted notification of entity into kafka
topic can be done seperate UT/IT.
Let me know your thoughts.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
