[
https://issues.apache.org/jira/browse/AURORA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zameer Manji resolved AURORA-655.
---------------------------------
Resolution: Fixed
{noformat}
commit 249245db06d266d0f475147b167497ad1bb91a06
Author: Jing Chen <milantr...@gmail.com>
Date: Tue Oct 4 09:14:55 2016 -0500
Order job update events and instance events by ID rather than timestamp
Bugs closed: AURORA-655
Reviewed at https://reviews.apache.org/r/52508/
src/main/resources/org/apache/aurora/scheduler/storage/db/JobUpdateDetailsMapper.xml
| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
{noformat}
Thanks [~jingc]!
> Order job update events and instance events by ID rather than timestamp
> -----------------------------------------------------------------------
>
> Key: AURORA-655
> URL: https://issues.apache.org/jira/browse/AURORA-655
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Bill Farner
> Assignee: Jing Chen
> Priority: Trivial
> Labels: newbie
>
> In {{JobUpdateDetailsMapper.xml}} we order by timestamps, which could be
> brittle if the system time changes. Instead of using the timestamp, use the
> built-in database {{IDENTITY}} for sort order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
