beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaltay <...@git.apache.org>
Subject [GitHub] beam pull request #1889: [BEAM-1319] Add conflict resolution to the Pipeline...
Date Wed, 01 Feb 2017 18:41:30 GMT
GitHub user aaltay opened a pull request:

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

    [BEAM-1319] Add conflict resolution to the PipelineOptions internal argparse.

    In some instances where a PipelineOptions subclass was defined in the
    main session and save_main_session option is enabled, that subclass may
    appear multiple times in the PipelineOptions.__subclassess__() list.
    This is causing problems with the argparse because options are not
    unique any more.
    
    This change filters the subclasses by name, and pick the last unique
    instance of each subclass.


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

    $ git pull https://github.com/aaltay/beam opt

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

    https://github.com/apache/beam/pull/1889.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 #1889
    
----
commit 86c173eb7991594168a53c609747ec6a91651133
Author: Ahmet Altay <altay@google.com>
Date:   2017-02-01T18:39:59Z

    In some instances where a PipelineOptions subclass was defined in the
    main session and save_main_session option is enabled, that subclass may
    appear multiple times in the PipelineOptions.__subclassess__() list.
    This is causing problems with the argparse because options are not
    unique any more.
    
    This changes filter the subclasses by name, and pick the last unique
    instance of each subclass.

----


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