@subash sharma Have taken a look at the Hive Hook code? This should give you a good idea of the approach used. I don't know if that will be sufficient for all your needs, but it should give you a good idea on how to approach the problem. Hope this helps. ... View more

Let me attempt to answer all your questions: 1. Think of composite as composition in object oriented design world. An entity is part of the dependent entity. The lifetime of the child (contained entity) is determined by its parent. Child cannot exist without the parent. 2. I don't think there is a place where all of this is defined. We should definitely improve on our documentation. Here's link to code where this is defined. It is not ideal but better than nothing. 3. Relationships is a new concept. This implementation is only is master now. There is backward compatibility. Here's what the concept is: So far (before relationships) we would define associations between 2 entities as containment just by referencing one entity into another. See hive model in branch 0.8. Relationships merely allow you to capture this more comprehensively by modeling it separately. This will be apparent if you simply compare the hive model in master and branch-0.8. 4. For defining entities with composition, you could useAtlasEntity.AtlasEntityWithExtInfo. Add parent entity to the constructor and define the entities referenced as AtlasObjectIds. The creation API will take care of resolving the references. I am attaching JSON for reference. CURL entity creation is also added for reference. Also see these object diagrams. Hope this helps. @Sarath Subramanian Thanks for your help in drafting this reply. hive-table-sample.zipcreate-hive-table-entity.txt ... View more