[ https://issues.apache.org/jira/browse/ASTERIXDB-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467776#comment-16467776 ]
ASF subversion and git services commented on ASTERIXDB-2373: ------------------------------------------------------------ Commit 70a14b5bb4affd3e6711f95bf5118d07e5317a4d in asterixdb's branch refs/heads/master from [~sjaco002] [ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=70a14b5 ] [ASTERIXDB-2373][HYR,CLUS] Allow upsert of JobSpecs for Deployed Jobs - user model changes: none - storage format changes: none - interface changes: new methods added This change adds the upsertDeployedJobSpec method, enabling a Deployed Job to update its Job Specification. Added call in test. Removed DeployedJobService (moved methods to BAD codebase). Change-Id: I01fd5d43896d520fe75e1007d7bd39324f6f6e4b Reviewed-on: https://asterix-gerrit.ics.uci.edu/2619 Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Reviewed-by: Xikui Wang <xkk...@gmail.com> > Allow Deployed Jobs to receive new Job Specifications > ----------------------------------------------------- > > Key: ASTERIXDB-2373 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2373 > Project: Apache AsterixDB > Issue Type: Improvement > Reporter: Steven Jacobs > Assignee: Steven Jacobs > Priority: Major > > It may be desirable to create a new Job Specification for a Deployed Job. We > need some way to handle this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)