GitHub user XuMingmin opened a pull request:

    https://github.com/apache/beam/pull/3602

    Revert "[BEAM-2610] This closes #3553"

    This reverts commit ec494f675aa73fbdc7929f9592f33951941962b0, reversing
    changes made to d89d1ee1a3085269cdf44ec50e29a95c8f43757b.
    
    Follow this checklist to help us incorporate your contribution quickly and 
easily:
    
     - [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the 
change (usually before you start working on it).  Trivial changes like typos do 
not require a JIRA issue.  Your pull request should address just this issue, 
without pulling in other changes.
     - [ ] Each commit in the pull request should have a meaningful subject 
line and body.
     - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA 
issue.
     - [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
     - [ ] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will be performed on your pull request automatically.
     - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
    
    ---


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/XuMingmin/beam revert_3553

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/3602.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 #3602
    
----
commit c1b2b96a438b86a8b0023f6943dcf0a4f238ba39
Author: mingmxu <[email protected]>
Date:   2017-07-19T21:26:11Z

    Revert "[BEAM-2610] This closes #3553"
    
    This reverts commit ec494f675aa73fbdc7929f9592f33951941962b0, reversing
    changes made to d89d1ee1a3085269cdf44ec50e29a95c8f43757b.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to