@Arsalan Siddiqi Your observation about the JSON is accurate. The JSON you see in the sample is represented in the old format. We now use the new format referred to as V2. The V2 format is easy to understand as it is a JSON representation of the Java class. This is much easy to code compared to earlier approach. I am attaching atlas-application.properties file that I use on IntelliJ development. atlas-applicationproperties.zip Hope this helps. ... View more

@Arsalan Siddiqi Thanks for reaching out. If you could clarify few items below, it will help: What is the purpose of hook? Hook are one of the ways to get data into Atlas. They are used in cases where the producer of data has well defined mechanism of sending notifications about their data. Atlas leverages that. In your case, does your producer have this in place? If your producer does not have good notification mechanism in place, you could consider writing a small application that would enumerate the data and then use Atlas' REST APIs to update data to Atlas. We use IntelliJ for development. There are few setup steps needed if you need to use integrated debugging via IntelliJ. Let me know if that is the case. Attached are logs for a successful Atlas startup. applicationlog.zip ... View more

Is there a specific exception that is logged over and over again? If yes, can you please let me know what the exception is? ... View more

@Arsalan Siddiqi From the exceptions it appears that the Atlas is having difficulty connecting to Kafka. From the web UI exception, it appears to be a build problem. Can you please confirm which profile have you used for build is it berlekeyDB & elasticSearch or is it hbase & solr. ... View more

@Sarath Subramanian Thanks for the detailed investigation. @Sharmadha Sainath Thanks for your help today! ... View more

@Smart Data This is still puzzling. Would it be possible for you create the entity using REST APIs? That way the debug cycle is quick. I will attempt the same at my end with the entities JSON above. Lets see where that leads us. ... View more

@Smart Data This error typically comes when the new entity while being created tries to reference something that should already exist. 2017-07-25 13:24:58,650 DEBUG - [NotificationHookConsumer thread-0:] ~ ==> AtlasErrorCode.getMessage([null]): ObjectId is not valid null (AtlasErrorCode:132) I would start by checking if the 2 guids referenced exist in Atlas DB before this message gets processed. "d5c27069-d7b6-4b58-8e61-adbdc4b8d208" & "513cd2cd-3139-4baa-a017-16f83ca2b383" ... View more

@Arsalan Siddiqi The quick_start sample aims to demonstrate use of type system, entity creation, creation of lineage and then search. Though Atlas provides out-of-box types for hive, falcon, etc. It also allows for you to create your own types. Once types are created entities of those types can be created. Think of entities as instances of types. Specifically to quick_start, the entities depend on each other, thereby showing how lineage can be used (see sales_fact). One key highlight is the use of tags. This allows grouping entities that are semantically relevant. See how the PII tag is used. See how all the load operations show up once ETL tag is selected. Hope this helps! ... View more

This worked fine: curl -g -X GET -u admin:admin "http://localhost:21000/api/atlas/v2/entity/bulk?guid=4762daa1-ac15-4b57-afbc-2ddfa063e1f5" -H 'Content-Type: application/json' The guid belongs to the newly created entity. Which means the entity was created successfully. Now to retrieve the entity with uniqueAttribute it needs additional information. This call does the trick: curl -g -X GET -u admin:admin "http://localhost:21000/api/atlas/v2/entity/uniqueAttribute/type/test_entity_15?attr:qualifiedName=test_entity_15@Sandbox" -H 'Content-Type: application/json ... View more