You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/02/28 16:02:00 UTC

[jira] [Closed] (FLINK-2623) Extend API completeness check to check signatures

     [ https://issues.apache.org/jira/browse/FLINK-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-2623.
--------------------------------
    Resolution: Won't Do

Closed for inactivity

> Extend API completeness check to check signatures
> -------------------------------------------------
>
>                 Key: FLINK-2623
>                 URL: https://issues.apache.org/jira/browse/FLINK-2623
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Till Rohrmann
>            Priority: Major
>
> Currently, the API completeness check only verifies that the Java and Scala API both have the same API methods based on their name. This, however, does not guarantee that both API's cover the same functionality. 
> The Scala Streaming API, for example, supports the {{writeAsText}} method. However, it does not let you specify the {{WriteMode}}, which is supported by the Java Streaming API. Maybe it is possible to extend the API completeness check to also verify the signatures or parts of the signatures of the API methods to avoid a divergence in functionality.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)