You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dong Lin (Jira)" <ji...@apache.org> on 2023/03/01 09:59:00 UTC

[jira] [Commented] (FLINK-31126) Move classes not depending on Flink runtime from flink-ml-core to flink-ml-servable-core

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

Dong Lin commented on FLINK-31126:
----------------------------------

Merged to flink-ml master branch b032ebdb122f32ba04bd21ad03a2f971b471e5bc

> Move classes not depending on Flink runtime from flink-ml-core to flink-ml-servable-core
> ----------------------------------------------------------------------------------------
>
>                 Key: FLINK-31126
>                 URL: https://issues.apache.org/jira/browse/FLINK-31126
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Library / Machine Learning
>            Reporter: Dong Lin
>            Assignee: Dong Lin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: ml-2.2.0
>
>
> We would like to be able to deploy servable classes on edge devices (e.g. phone) with minimal library dependencies and memory footprint. Thus flink-ml-servable-lib module, which contains the servable classes such as KMeansServable, should not depend on Flink runtime modules (e.g. flink-table-runtime).
> We need to do the following to achieve this goal:
> - Keep the classes (e.g. AlgoOperator) whose API depends on Flink runtime classes (e.g. Table, DataStream) in flink-ml-core. Move the remaining classes from flink-ml-core to flink-ml-servable-core.
> - flink-ml-core and all modules that currently depend on flink-ml-core should now depend on flink-ml-servable-core.
> - flink-ml-servable-lib should depend on flink-ml-servable-core but not flink-ml-core.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)