GitHub user pnowojski opened a pull request:

    https://github.com/apache/flink/pull/5007

    [FLINK-7845] Make NettyMessage public

    This a walkaround strange javaassist bug. The issue should go away
    once we upgrade netty dependency.
    
    Please check the [ticket](https://issues.apache.org/jira/browse/FLINK-7845) 
for more information.
    
    This change was manually tested on this example: 
https://github.com/okkam-it/flink-memory-leak
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (yes / **no**)
      - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
      - The serializers: (yes / **no** / don't know)
      - The runtime per-record code paths (performance sensitive): (yes / 
**no** / don't know)
      - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
      - The S3 file system connector: (yes / **no** / don't know)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (yes / **no**)
      - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)


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

    $ git pull https://github.com/pnowojski/flink f7845

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

    https://github.com/apache/flink/pull/5007.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 #5007
    
----
commit 99b88881bd240e16f6c461893f2cc93a0e5e3db3
Author: Piotr Nowojski <[email protected]>
Date:   2017-11-13T15:51:18Z

    [FLINK-7845] Make NettyMessage public
    
    This a walkaround strange javaassist bug. The issue should go away
    once we upgrade netty dependency.
    
    Please check the ticket for more information.

----


---

Reply via email to