Return-Path: X-Original-To: apmail-spark-issues-archive@minotaur.apache.org Delivered-To: apmail-spark-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 328FF17A97 for ; Sun, 28 Sep 2014 20:59:34 +0000 (UTC) Received: (qmail 97333 invoked by uid 500); 28 Sep 2014 20:59:34 -0000 Delivered-To: apmail-spark-issues-archive@spark.apache.org Received: (qmail 97300 invoked by uid 500); 28 Sep 2014 20:59:33 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 97290 invoked by uid 99); 28 Sep 2014 20:59:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Sep 2014 20:59:33 +0000 Date: Sun, 28 Sep 2014 20:59:33 +0000 (UTC) From: "Mridul Muralidharan (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SPARK-3714) Spark workflow scheduler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SPARK-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151211#comment-14151211 ] Mridul Muralidharan commented on SPARK-3714: -------------------------------------------- Have you tried using oozie for this ? IIRC Tom has already gotten this working here quite a while back /CC [~tgraves] > Spark workflow scheduler > ------------------------ > > Key: SPARK-3714 > URL: https://issues.apache.org/jira/browse/SPARK-3714 > Project: Spark > Issue Type: New Feature > Components: Project Infra > Reporter: Egor Pakhomov > Priority: Minor > > [Design doc | https://docs.google.com/document/d/1q2Q8Ux-6uAkH7wtLJpc3jz-GfrDEjlbWlXtf20hvguk/edit?usp=sharing] > Spark stack currently hard to use in the production processes due to the lack of next features: > * Scheduling spark jobs > * Retrying failed spark job in big pipeline > * Share context among jobs in pipeline > * Queue jobs > Typical usecase for such platform would be - wait for new data, process new data, learn ML models on new data, compare model with previous one, in case of success - rewrite model in HDFS directory for current production model with new one. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org