Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
From: mxm <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
References: <git-pr-685-flink@git.apache.org>
In-Reply-To: <git-pr-685-flink@git.apache.org>
Subject: [GitHub] flink pull request: [FLINK-2025] add support for booleans in
 csv p...
Content-Type: text/plain
Message-Id: <20150518164314.9EC5FE0914@git1-us-west.apache.org>
Date: Mon, 18 May 2015 16:43:14 +0000 (UTC)

Github user mxm commented on the pull request:

    https://github.com/apache/flink/pull/685#issuecomment-103122448
  
    IMHO the current behavior is well-defined. As you said, it's a question of making a choice and sticking to it. I would add a case-insensitive check for `true` but swallowing all other values doesn't seem right to me. However, if that's the common by behavior of parses in the Java world, I'm not going to insist on the current behavior.


---
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.
---