flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8064) Extend dependecy section to list flink-core
Date Tue, 14 Nov 2017 11:13:00 GMT

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

Chesnay Schepler commented on FLINK-8064:

that's true; thing is that the client module is in this weird place where it is included in
flink-dist, but also used in applications that don't run on a flink cluster.

Personally i think the module setup of the queryable state is a bit weird. The QS runtime
is a separate jar that has to be added to /lib, but the QS _client_ is always in dist. Why
is the client in flink-dist anyway?

My impression is that the QS module should've been split into 3 parts:
* qs-common, containing shared classes, not part of flink-dist
* qs-runtime, containing the proxy/server, part of flink-dist as an optional jar, depends
on qs-common and pulls it into flink-dist
* qs-client, containing only the client, never in flink-dist, depends on flink-core and qs-common

> Extend dependecy section to list flink-core
> -------------------------------------------
>                 Key: FLINK-8064
>                 URL: https://issues.apache.org/jira/browse/FLINK-8064
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Queryable State
>    Affects Versions: 1.4.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
> The dependency section of the Queryable State documentation should also list flink-core
as it is inherently required when working with the client. (Which has flink-core set to provided)

This message was sent by Atlassian JIRA

View raw message