You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/17 12:13:18 UTC

[jira] [Commented] (FLINK-3430) Remove "no POJO" warning in TypeAnalyzer

    [ https://issues.apache.org/jira/browse/FLINK-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150314#comment-15150314 ] 

ASF GitHub Bot commented on FLINK-3430:
---------------------------------------

GitHub user aljoscha opened a pull request:

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

    [FLINK-3430] Remove "no POJO" warning in TypeAnalyzer

    

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

    $ git pull https://github.com/aljoscha/flink scala-remove-pojo-warning

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

    https://github.com/apache/flink/pull/1655.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 #1655
    
----
commit 018f6cd46e649bded67d31855c26937654f66dd5
Author: Aljoscha Krettek <al...@gmail.com>
Date:   2016-02-17T11:12:23Z

    [FLINK-3430] Remove "no POJO" warning in TypeAnalyzer

----


> Remove "no POJO" warning in TypeAnalyzer
> ----------------------------------------
>
>                 Key: FLINK-3430
>                 URL: https://issues.apache.org/jira/browse/FLINK-3430
>             Project: Flink
>          Issue Type: Improvement
>          Components: Scala API
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>
> Right now, the TypeAnalyzer creates compilation warnings when a type cannot be analyzed as a POJO. This could confuse some users so we should remove it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)