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 3F53F200C2A for ; Wed, 1 Mar 2017 10:59:42 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3DEAD160B70; Wed, 1 Mar 2017 09:59:42 +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 7DB55160B5E for ; Wed, 1 Mar 2017 10:59:41 +0100 (CET) Received: (qmail 73440 invoked by uid 500); 1 Mar 2017 09:59:40 -0000 Mailing-List: contact reviews-help@bahir.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: reviews@bahir.apache.org Delivered-To: mailing list reviews@bahir.apache.org Received: (qmail 73425 invoked by uid 99); 1 Mar 2017 09:59:40 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2017 09:59:40 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 4CC52DFCA1; Wed, 1 Mar 2017 09:59:40 +0000 (UTC) From: rmetzger To: reviews@bahir.apache.org Reply-To: reviews@bahir.apache.org References: In-Reply-To: Subject: [GitHub] bahir-flink issue #11: [BAHIR-91] Upgrade Flink version to 1.2.0 Content-Type: text/plain Message-Id: <20170301095940.4CC52DFCA1@git1-us-west.apache.org> Date: Wed, 1 Mar 2017 09:59:40 +0000 (UTC) archived-at: Wed, 01 Mar 2017 09:59:42 -0000 Github user rmetzger commented on the issue: https://github.com/apache/bahir-flink/pull/11 I think the travis tests will fail because they are overwriting the Flink version. I have a constant there for the Flink version. My initial plan was to support multiple Flink versions at the same time. Do you think there is an easy way to still support 1.1. and 1.2 with the Bahir connectors? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---