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 B68CC200BD1 for ; Mon, 28 Nov 2016 22:09:03 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B2978160B0D; Mon, 28 Nov 2016 21:09:03 +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 08D71160B00 for ; Mon, 28 Nov 2016 22:09:02 +0100 (CET) Received: (qmail 27027 invoked by uid 500); 28 Nov 2016 21:09:02 -0000 Mailing-List: contact commits-help@beam.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.incubator.apache.org Delivered-To: mailing list commits@beam.incubator.apache.org Received: (qmail 27017 invoked by uid 99); 28 Nov 2016 21:09:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Nov 2016 21:09:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D35A21AB868 for ; Mon, 28 Nov 2016 21:09:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -7.018 X-Spam-Level: X-Spam-Status: No, score=-7.018 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id yIBdlXirrOvV for ; Mon, 28 Nov 2016 21:09:01 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id A57D95FD0A for ; Mon, 28 Nov 2016 21:09:00 +0000 (UTC) Received: (qmail 22102 invoked by uid 99); 28 Nov 2016 21:08:10 -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; Mon, 28 Nov 2016 21:08:10 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0345EE04BB; Mon, 28 Nov 2016 21:08:10 +0000 (UTC) From: pabloem To: commits@beam.incubator.apache.org Reply-To: commits@beam.incubator.apache.org Message-ID: Subject: [GitHub] incubator-beam pull request #1443: [BEAM-1055] Display Data keys on Python a... Content-Type: text/plain Date: Mon, 28 Nov 2016 21:08:10 +0000 (UTC) archived-at: Mon, 28 Nov 2016 21:09:03 -0000 GitHub user pabloem opened a pull request: https://github.com/apache/incubator-beam/pull/1443 [BEAM-1055] Display Data keys on Python are inconsistent Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [x] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [x] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/pabloem/incubator-beam beam-1000smth Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-beam/pull/1443.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1443 ---- commit e620b07afd10439c29401726161cb7139185ec38 Author: Pablo Date: 2016-11-28T21:05:47Z Standardizing display data keys ---- --- 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. ---