Eva Xiao , Messages are processed in the order they are received by Atlas. If message#1 has any error , only then message#2 is processed and action#3 specified by you can happen. ... View more

@Satya Nittala 1. Please use correct port . By default , Atlas in non-SSL environment is configured to use 21000. 2. curl requires "@" for providing files. Example : -d @user/testplace.json 3. To update type , "PUT" (not POST. To create types use POST, to update types use "PUT") the JSON to http://atlashost:21000/api/atlas/v2/types/typedefs 4. As already mentioned , classification/tag best suits your requirement. Its highly recommended to use tags instead of updating types. ... View more

@Satya Nittala yes , POST the JSON body attached in the file to http://localhost:21000/api/atlas/v2/types/typedefs?type=classification In the tag definition , name is the name of the tag , and attributeDefs is an JSON array of attribute definitions. I have added expiry_date attribute of type date in the example. Once the tag is created , the tag can be associated to the hive_table entity by POSTing the attached tag-association.txt to http://localhost:21000/api/atlas/v2/entity/bulk/classification in tag-association.txt , "name" is the name of tag . attribute values can be provided in "attributes". entityGuids is the list of all the GUIDs of entity the tag should be associated to. In this array , you can provide the hive_table GUID. ... View more

@Satya Nittala hive_table is a type and fields you mentioned like aliases ,columns,comment,createTime,db etc., are attributes of hive_table. Type can be updated using PUT (http://atlas.apache.org/api/v2/resource_TypesREST.html#resource_TypesREST_updateAtlasTypeDefs_PUT). This requires fetching the type definition and updating with new attribute. For example , Following GET REST call is used to fetch the hive_table type definition : http://atlashost:21000/api/atlas/v2/types/entitydef/name/hive_table After fetching the type definition , new attribute definition can be added in the attributeDefs array as { name: "new_attribute", typeName: "string", isOptional: true, cardinality: "SINGLE", valuesMinCount: 0, valuesMaxCount: 1, isUnique: false, isIndexable: false } name : name of the new attribute typename : data type of the attribute isOptional : if the entity can be created without providing values for the attribute. (Note : updating a type with new mandatory attribute is not allowed. While updating , provide isOptional as True). and the updated JSON can be PUT to http://atlashost:21000/api/atlas/v2/types/typedefs For example , in the text file attached , I have added new attribute definition . GUID of the hive_table has to be modified based on your Atlas instance. Please let me know if you are stuck somewhere in this procedure. One question : hive_table is a defined type in Atlas.It has all attributes which will be required for maintaining hive meta data. May I know why you want to update it ? What is the new attribute you want to add ? could you please explain the use case behind it ? ... View more

@Satya Nittala I hope you have enabled Atlas Hive hook settings. If yes , all updates to the hive table are captured by Atlas. When column is added in Hive, you can find the newly created hive_column entity in Atlas. ... View more