Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
Date: Tue, 4 Oct 2016 08:38:20 +0000 (UTC)
From: "Jing Chen (JIRA)" <jira@apache.org>
To: issues@aurora.apache.org
Message-ID: <JIRA.12734264.1408052733000.728935.1475570300479@Atlassian.JIRA>
In-Reply-To: <JIRA.12734264.1408052733000@Atlassian.JIRA>
References: <JIRA.12734264.1408052733000@Atlassian.JIRA> <JIRA.12734264.1408052733525@arcas>
Subject: [jira] [Commented] (AURORA-655) Order job update events and
 instance events by ID rather than timestamp
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 04 Oct 2016 08:38:22 -0000


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

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

And there is instance update events, should we sort them by id as well?

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