GitHub user tgroh opened a pull request:

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

    Remove verifyDeterministic from StructuredCoder

    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`.
     - [ ] 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.pdf).
    
    ---
    This is replaced within all uses in the Core SDK by
    Coder.verifyDeterministic(Coder, String, List<Coder>), which is a
    general utility.
    
    I believe that this change was already authored but lost in a merge.
    
    @kennknowles @lukecwik @davorbonaci 
    
    This is opened against the release branch to determine if it's worth 
merging. It cherry-picks cleanly into master, and I can create the appropriate 
PR if desired.

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

    $ git pull https://github.com/tgroh/beam coder_arguments

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

    https://github.com/apache/beam/pull/3029.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 #3029
    
----
commit 68875b48894fa5d3743ebb0696266e9600c64ef3
Author: Thomas Groh <[email protected]>
Date:   2017-05-10T01:09:37Z

    Remove verifyDeterministic from StructuredCoder
    
    This is replaced within all uses in the Core SDK by
    Coder.verifyDeterministic(Coder, String, List<Coder>), which is a
    general utility.

----


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