You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2017/02/01 07:54:54 UTC

[jira] [Updated] (AURORA-655) Order job update events and instance events by ID rather than timestamp

     [ https://issues.apache.org/jira/browse/AURORA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Erb updated AURORA-655:
-------------------------------
    Fix Version/s: 0.17.0

> 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
>             Fix For: 0.17.0
>
>
> 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.15#6346)