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

["Jing Chen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544710#comment-15544710 ] 

Jing Chen commented on AURORA-655:
----------------------------------

Hi Bill, in this ticket, can you explain more about 'brittle'.

As far as i am concerned, if the system time changes, jobs' schedule time won't be consistent, which leads to unordered returned result. Can you tell me if i am right or not?

What else would happen if the system time changes? Thanks a lot.

> 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)