Skip to content

Remove JsonFormat from AuditEvent #11588

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

joshiste
Copy link
Contributor

@joshiste joshiste commented Jan 10, 2018

In order to align the timestamp format of auditevents with the traces
remove the @JsonFormat annotation. This way the date is serialized using
the object mapper's default configuration (as for the traces).
With the spring boot 2.0 default this results in milliseconds to be
serialized in the json. This allow finer grained querying for events via
http as it may be useful for subsequent requests fetching all new events
after the last knwon timestamp from the previous request.

In order to align the timestamp format of auditevents to the traces
remove the @jsonformat annotation. This way the date is serialized using
the object mapper's default configuration (as for the traces).
With the spring boot 2.0 default this results in milliseconds to be
serialized in the json. This allow finer grained querying for events via
http as it may be useful for subsequent requests fetching all new events
after the last knwon timestamp from the previous request.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 10, 2018
@snicoll
Copy link
Member

snicoll commented Jan 10, 2018

Relates to #10976

@wilkinsona
Copy link
Member

Thanks for the PR, @joshiste. IMO, there isn't much point in making this change in isolation. What's being proposed here is a small piece of what #10976 will do. I'd rather do it all in one place as it'll make the change history cleaner. I'll make a note in #10976 so that the removal of any JSON formatting annotations isn't forgotten.

@wilkinsona wilkinsona closed this Jan 10, 2018
@wilkinsona wilkinsona added status: declined A suggestion or change that we don't feel we should currently apply and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants