Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4E28E200B4C for ; Fri, 17 Jun 2016 05:01:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4CBD1160A60; Fri, 17 Jun 2016 03:01:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BDEEB160A52 for ; Fri, 17 Jun 2016 05:01:06 +0200 (CEST) Received: (qmail 3973 invoked by uid 500); 17 Jun 2016 03:01:05 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 3936 invoked by uid 99); 17 Jun 2016 03:01:05 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2016 03:01:05 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 507D02C1F62 for ; Fri, 17 Jun 2016 03:01:05 +0000 (UTC) Date: Fri, 17 Jun 2016 03:01:05 +0000 (UTC) From: "Maxim Khutornenko (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AURORA-1711) Allow client to store metadata on Update entity MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 17 Jun 2016 03:01:07 -0000 [ https://issues.apache.org/jira/browse/AURORA-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335286#comment-15335286 ] Maxim Khutornenko commented on AURORA-1711: ------------------------------------------- An alternative approach could be accepting client generated update ID, e.g.: by including {{JobUpdateKey}} into update request. This could be an easier option not requiring any storage changes and would also correlate with the proposed rollback idea: http://markmail.org/thread/l42kwxoi2wtlzzje. The downside, it won't address any future use cases where update tags could still come handy. > Allow client to store metadata on Update entity > ----------------------------------------------- > > Key: AURORA-1711 > URL: https://issues.apache.org/jira/browse/AURORA-1711 > Project: Aurora > Issue Type: Task > Components: Scheduler > Reporter: David McLaughlin > > I have a use case where I'm programmatically starting updates via the Aurora API and sometimes the request to the scheduler times out or fails, even though the update is written to storage and started. > I'd like to be able to store some unique identifier on the update so that we can reconcile this state later. We can make this generic by allowing clients to store arbitrary metadata on an update (similar to how they do it with job configuration). -- This message was sent by Atlassian JIRA (v6.3.4#6332)