Return-Path: X-Original-To: apmail-flink-dev-archive@www.apache.org Delivered-To: apmail-flink-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98CFB17A01 for ; Mon, 30 Mar 2015 15:22:30 +0000 (UTC) Received: (qmail 17550 invoked by uid 500); 30 Mar 2015 15:22:27 -0000 Delivered-To: apmail-flink-dev-archive@flink.apache.org Received: (qmail 17490 invoked by uid 500); 30 Mar 2015 15:22:27 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 17477 invoked by uid 99); 30 Mar 2015 15:22:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2015 15:22:27 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of amitpawar5388@gmail.com designates 209.85.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-ob0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2015 15:22:21 +0000 Received: by obvd1 with SMTP id d1so60179674obv.0 for ; Mon, 30 Mar 2015 08:22:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=3qDNm5qRz2jCzHKyO3m9pt8qB3HaByOjoCNiD5hBwZU=; b=WS4+oXtD4w4GHU36VRX4UPax28aJ3Y5h2k35iOVYU+Jt4rJ9lpqLtcikaHSntiO24p nZpFBOzniI3rcrod0LDgb81vKRemxN3+FOJNM4BGQ2/SAvfXGCymjTvxGPeTaPkt0cS5 iLUOfclBWeZxG9DboN8Me8mMU8wrumKGEXVC+BaxHxothp+Z4hUxYTnmTOLLjQWGERd5 YdHDxmmn5DjUg/FCfOrqyCErO+9HNpskVJ6rFEut60570Y1Ew5inUxDxX/XtpoIG6n5k WYWLNdMytW5qe7mSWZ4Ao8Ybx91v3PX0YLp6k+9Q9nZCXZmG9HjBSg6/cJiENNotErbT xPPw== MIME-Version: 1.0 X-Received: by 10.182.20.237 with SMTP id q13mr27031644obe.82.1427728921142; Mon, 30 Mar 2015 08:22:01 -0700 (PDT) Received: by 10.182.210.201 with HTTP; Mon, 30 Mar 2015 08:22:01 -0700 (PDT) Date: Mon, 30 Mar 2015 17:22:01 +0200 Message-ID: Subject: Extracting detailed Flink execution plan From: Amit Pawar To: dev@flink.apache.org Content-Type: multipart/alternative; boundary=e89a8f838e092e47fb0512830bda X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f838e092e47fb0512830bda Content-Type: text/plain; charset=UTF-8 Hi I am trying to extract/retrieve the Flink execution plan. I managed to get it as JSON string in following ways: 1. Using JAR - via PackagedProgram using getPreviewPlan() ; or 2. Directly in program - via ExecutionEnvironment's getExecutionPlan() My question is - Is it possible to retrieve directly the Plan object? I tried for this but was not successful as submitting the jar takes us into interactive mode, and in order to use the other mode, programEntryPoint, the main class needs to implement Program interface with getPlan method. Even if we manage to get the execution plan as a Plan object, will it be different from what we have using JSON string? like in terms of - 1. What are the datatypes used in the dataset's tuple 2. On what key is the Join taking place 3. Filtering predicate 4. Field for Distinct and so on (JSON plan does have the operator tree but the contents field points to the line of code in the class, which is not that helpful) If not, is it possible (by some other way) to get the above details just by using the Flink job/jar as an input? Thanks and Regards Amit Pawar --e89a8f838e092e47fb0512830bda--