Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Event store requires timestamps in UTC #335

Closed
abuijze opened this issue Apr 24, 2017 · 0 comments
Closed

Event store requires timestamps in UTC #335

abuijze opened this issue Apr 24, 2017 · 0 comments
Assignees
@abuijze
Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
Milestone
Release 3.0.5

Comments

@abuijze
Copy link
Member

abuijze commented Apr 24, 2017

Currently, any timestamp other than UTC will not be accepted by the EventStore implementations. The reason is that Axon uses Instant.parse(...) to parse the timestamp. Instant.parse(...) only accepts ISO8601 timestamps in the UTC timezone.
@abuijze abuijze added this to the Release 3.1 milestone Apr 24, 2017
@abuijze abuijze added Type: Bug Use to signal issues that describe a bug within the system. Type: Enhancement Use to signal an issue enhances an already existing feature of the project. and removed Type: Bug Use to signal issues that describe a bug within the system. labels Apr 24, 2017
abuijze added a commit that referenced this issue Apr 24, 2017
@abuijze
Parsing timestamps with ISO8601 format instead of Instant.parse()
e8f5a64 
Instant.parse() only accepts the UTC timezone. In certain event stores,
timestamps are stored in another timezone.

Fixes issue #335
abuijze added a commit that referenced this issue May 10, 2017
@abuijze
Parsing timestamps with ISO8601 format instead of Instant.parse()
0c65dba 
Instant.parse() only accepts the UTC timezone. In certain event stores,
timestamps are stored in another timezone.

Fixes issue #335

(cherry picked from commit e8f5a64)
@abuijze abuijze modified the milestones: Release 3.0.5, Release 3.1 Jun 8, 2017
@abuijze abuijze closed this as completed Jun 8, 2017
@martijnvanderwoud martijnvanderwoud mentioned this issue Sep 21, 2017
Closed
@smcvb smcvb added Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. labels Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abuijze abuijze

Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
Projects
None yet
Milestone
Release 3.0.5
Development

No branches or pull requests
2 participants
@abuijze @smcvb