It's not elegant, but this custom masking seems to work. cast(mask(cast(to_date({col}) as date), 'x', 'x', 'x', -1, '1', 1, 0, -1) as timestamp) ... View more

@Laura Ngo, "options" was added to AtlasBaseTypeDef to allow additional metadata properties to be included with the type definition. These properties allow users to specify any key/value property or constraint on the type definition e.g. cluster = test_cluster contains_all_primitive_attributes=true The options map is not being used currently but added for future use cases. ... View more

Hi @Laura Ngo, The documentation for 'Atlas types' is still not updated with v2 types. It should ideally be - "Composite metatypes – Entity, Struct and Classification" Struct Type: You cannot create instances for Struct types as they do not have an identity of their own (it doesn't have a GUID), it always exists with an entity. e.g. entity attribute can be of type struct. Classification type: Each classification instance is associated with an entity. The v2 type name for "trait" is "classification" and it is derived from Struct. e.g. Associate tag/classification to an entity. Checkout Working with Atlas Tags to know more about how you can assign tag/classification to an entity. ... View more

@Laura Ngo I ran your type definition through the REST API for Atlas 0.6. It is valid and does show up as a valid tag in the Atlas UI. From the AtlasUI, I added the tag to a hive table entity successfully and then gave the tag some attributes. It does not look like the UI is able to show or edit the array type attributes for the tags but I was able to call the REST API (the GUID on the end of the URI is the entity id): curl -X GET http://localhost:21000/api/atlas/entities/a6f3e6c8-57f6-45ce-98e7-ea14a1f29211 and get the following result: { "requestId": "qtp1635546341-110 - 8bb20991-84e5-4dc5-a678-3dbe81cb52a2", "GUID": "a6f3e6c8-57f6-45ce-98e7-ea14a1f29211", "definition": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference", "id": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Id", "id": "a6f3e6c8-57f6-45ce-98e7-ea14a1f29211", "version": 0, "typeName": "hive_column" }, "typeName": "hive_column", "values": { "comment": null, "qualifiedName": "hr.employee.location@erietp", "type": "string", "name": "location" }, "traitNames": [ "PII", "api_test_set" ], "traits": { "PII": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "PII", "values": { } }, "api_test_set": { "jsonClass": "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct", "typeName": "api_test_set", "values": { "collection_test": [ "test" ], "set_test": [ "test" ] } } } } } Notice that the collection_test and set_test values show up as arrays denoted by [ ] and they are populated. As stated before, this will not show up in the UI but the value are persisted. I have not tried to add more elements to the arrays within the trait through the REST API but I don't see any reason why that would not work. If you were planning to use the value within the tags for some custom purpose you should be good to go. ... View more