flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zjureel <...@git.apache.org>
Subject [GitHub] flink pull request #4574: [FLINK-6864] Fix confusing "invalid POJO type" mes...
Date Wed, 23 Aug 2017 03:34:39 GMT
GitHub user zjureel opened a pull request:


    [FLINK-6864] Fix confusing "invalid POJO type" messages from TypeExtractor

    ## What is the purpose of the change
    Fix confusing "invalid POJO type" messages from TypeExtractor
    ## Brief change log
      - *Improve log about pojo in TypeExtractor*
      - *Add notice in types_serialization.cmd about rules-for-pojo-types*
    ## Verifying this change
    This change needs no testing
    ## Does this pull request potentially affect one of the following parts:
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
      - The serializers: (yes / no / don't know)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: (no)
    ## Documentation
      - Does this pull request introduce a new feature? (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/zjureel/flink FLINK-6864

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 #4574
commit 5b3861716404c1d1cce9f18af7ca596a21ecb014
Author: zjureel <zjureel@gmail.com>
Date:   2017-08-23T02:30:31Z

    [FLINK-6864] Fix confusing "invalid POJO type" messages from TypeExtractor


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