flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zentol <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-2609] [streaming] auto-register types
Date Wed, 23 Mar 2016 10:13:55 GMT
GitHub user zentol opened a pull request:


    [FLINK-2609] [streaming] auto-register types

    This PR attempts to register all streaming operator output types at kryo.
    In contrast to the Batch API
    * the registration is done when an operation is defined, opposed to after all operations
are defined
     * autoRegistration must be disabled before an operation is created to have an effect
    * the deduplicator HashSet is a protected field of the DataStream class opposed to a local
     * still not visible to users
     * accessible by all DataStream's
     * accessible by Non-DataStream streams (KeyedStream etc) as long as they are in the same
       * a separate superclass for all Streams is a good idea in the long run
    Most operations use DataStream#transform(), as such most registrations will take place
here. One exception are key-selectors, which aremysteriously hidden in the Keyed-/Joined-/CoGroupedStreams
where()/equalTo() methods, where their registration takes place.

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

    $ git pull https://github.com/zentol/flink 2609_register_types

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


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1833
commit 286a588464b18654eed342ba0d9cc2e92646eef7
Author: zentol <chesnay@apache.org>
Date:   2016-03-23T09:58:25Z

    [FLINK-2609] [streaming] auto-register types


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.

View raw message