beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tgroh <...@git.apache.org>
Subject [GitHub] incubator-beam pull request #802: Improve Write Failure Message
Date Tue, 09 Aug 2016 02:16:07 GMT
GitHub user tgroh opened a pull request:

    https://github.com/apache/incubator-beam/pull/802

    Improve Write Failure Message

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` 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).
    
    ---
    
    If provided with an Unbounded PCollection, Write will fail due to
    restriction of calling finalize only once. This error message fails in a
    deep stack trace based on it not being possible to apply a GroupByKey.
    Instead, throw immediately on application with a specific error message.

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

    $ git pull https://github.com/tgroh/incubator-beam write_error_message

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

    https://github.com/apache/incubator-beam/pull/802.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 #802
    
----
commit e50e1d38c31ef6fe36f1510224c04c05a470afff
Author: Thomas Groh <tgroh@google.com>
Date:   2016-08-09T02:09:58Z

    Improve Write Error Message
    
    If provided with an Unbounded PCollection, Write will fail due to
    restriction of calling finalize only once. This error message fails in a
    deep stack trace based on it not being possible to apply a GroupByKey.
    Instead, throw immediately on application with a specific error message.

----


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

Mime
View raw message