[ATLAS-2275] Entity notification serialization results in incorrect format for date attributes in traits

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8-incubating
• Fix Version/s: 0.8.2
• Component/s: atlas-core
• Assignee: Madhan Neethiraj
• Reporter: Madhan Neethiraj
• Created: 23/Nov/17 10:04
• Updated: 22/Dec/17 00:55
• Resolved: 22/Dec/17 00:55

Description

Entity notification object has 3 fields: entity, operationType, traits. Date type attributes in 'traits' are serialized in a different format than the same attributes in entity.traits field, as shown below:

notification.entity.traits:

"traits": {
  "TEST_TAG":{
    "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
    "typeName":"TEST_TAG",
    "values": {
      "createTime":"2017-11-22T08:00:00.000Z"
    }
  }
}

notification.traits:

"traits": [
  {
    "typeName":"TEST_TAG",
    "values": {
      "createTime":"Nov 22, 2017 12:00:00 AM"
    }
  }
]

This needs to be fixed so that the notification consumers will be able read the same value in either fields.