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 56E91200C00 for ; Wed, 18 Jan 2017 15:57:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 55903160B3A; Wed, 18 Jan 2017 14:57:45 +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 9EF7A160B34 for ; Wed, 18 Jan 2017 15:57:44 +0100 (CET) Received: (qmail 93331 invoked by uid 500); 18 Jan 2017 14:57:43 -0000 Mailing-List: contact issues-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 issues@flink.apache.org Received: (qmail 93322 invoked by uid 99); 18 Jan 2017 14:57:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jan 2017 14:57:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 55F531804B1 for ; Wed, 18 Jan 2017 14:57:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 14bIJksgAYRe for ; Wed, 18 Jan 2017 14:57:42 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 019EF5F2EF for ; Wed, 18 Jan 2017 14:57:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 534AFE0870 for ; Wed, 18 Jan 2017 14:57:28 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C40F025293 for ; Wed, 18 Jan 2017 14:57:26 +0000 (UTC) Date: Wed, 18 Jan 2017 14:57:26 +0000 (UTC) From: "Fabian Hueske (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-5548) Move checks for DataStreamRel validity into constructor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 18 Jan 2017 14:57:45 -0000 [ https://issues.apache.org/jira/browse/FLINK-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828221#comment-15828221 ] Fabian Hueske commented on FLINK-5548: -------------------------------------- Thanks for checking [~jark], I had assumed that some {{DataStreamRel}}s do also have checks in {{translateToPlan()}}. Closing this issue as invalid then. Thanks, Fabian > Move checks for DataStreamRel validity into constructor > ------------------------------------------------------- > > Key: FLINK-5548 > URL: https://issues.apache.org/jira/browse/FLINK-5548 > Project: Flink > Issue Type: Improvement > Components: Table API & SQL > Affects Versions: 1.2.0, 1.3.0 > Reporter: Fabian Hueske > Priority: Minor > > At the moment, most check to verify that a {{DataStreamRel}} is valid are done in the {{translateToPlan()}} method. These checks are for instance validating that a {{DataStreamJoin}} has at least one equality predicate. > Usually, the optimization process (i.e., the translation rules) should take care that no plans with invalid operators can be constructed. However, we should have these validity checks as an additional safety net which catch invalid plans if optimization rules are added or modified. > These checks should be done in the constructor to ensure that invalid operators are identified and not overlooked because this plan alternative was more expensive than a valid one. > This issue is to check all {{DataStreamRel}} nodes and move their validity checks into the constructor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)