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

Posted to issues@flink.apache.org by rmetzger <gi...@git.apache.org> on 2017/01/23 15:38:57 UTC

[GitHub] flink pull request #3195: [FLINK-5617] API stability check for Flink 1.2

GitHub user rmetzger opened a pull request:

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

    [FLINK-5617] API stability check for Flink 1.2

    With this PR, I'm marking some of the new methods in Flink 1.2 as public evolving / internal, instead of public.
    
    There are the reports for the covered modules:
    http://people.apache.org/~rmetzger/rel-1.2-japicmp/
    
    @aljoscha and @kl0u: Are the `fold()` and `reduce()` methods intentionally in the `@Public` scope? http://people.apache.org/~rmetzger/rel-1.2-japicmp/flink-streaming-java.html

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

    $ git pull https://github.com/rmetzger/flink flink5617

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

    https://github.com/apache/flink/pull/3195.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 #3195
    
----
commit 12d9d631455af2c4b6af1024a8865b534f4db9c8
Author: Robert Metzger <rm...@apache.org>
Date:   2017-01-23T13:31:27Z

    [FLINK-5617] Change reference version for API stability checks to 1.1.4

commit f7323c2e72e24da3a55fd70d6d27ae33026ecc86
Author: Robert Metzger <rm...@apache.org>
Date:   2017-01-23T15:28:48Z

    [FLINK-5617] Mark some methods as PublicEvolving or Internal

----


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

[GitHub] flink issue #3195: [FLINK-5617] API stability check for Flink 1.2

Posted by aljoscha <gi...@git.apache.org>.

Github user aljoscha commented on the issue:

    https://github.com/apache/flink/pull/3195
  
    @rmetzger I think they should be `@PublicEvolging`, can you change it in this PR?


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

[GitHub] flink pull request #3195: [FLINK-5617] API stability check for Flink 1.2

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

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


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

[GitHub] flink issue #3195: [FLINK-5617] API stability check for Flink 1.2

Posted by rmetzger <gi...@git.apache.org>.

Github user rmetzger commented on the issue:

    https://github.com/apache/flink/pull/3195
  
    Yes, I'll mark them as such while merging. Thank you for taking a look.


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