[
https://issues.apache.org/jira/browse/ATLAS-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-2275:
------------------------------------
Attachment: ATLAS-2275.patch
Review board URL: https://reviews.apache.org/r/64048/
> Entity notification serialization results in incorrect format for date
> attributes in traits
> -------------------------------------------------------------------------------------------
>
> Key: ATLAS-2275
> URL: https://issues.apache.org/jira/browse/ATLAS-2275
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 0.8-incubating
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Fix For: 1.0.0, 0.8.2
>
> Attachments: ATLAS-2275.patch
>
>
> 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:
> {noformat}
> "traits": {
> "TEST_TAG":{
>
> "jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
> "typeName":"TEST_TAG",
> "values": {
> "createTime":"2017-11-22T08:00:00.000Z"
> }
> }
> }
> {noformat}
> notification.traits:
> {noformat}
> "traits": [
> {
> "typeName":"TEST_TAG",
> "values": {
> "createTime":"Nov 22, 2017 12:00:00 AM"
> }
> }
> ]
> {noformat}
> This needs to be fixed so that the notification consumers will be able read
> the same value in either fields.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
