[
https://issues.apache.org/jira/browse/FLINK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161568#comment-16161568
]
ASF GitHub Bot commented on FLINK-7521:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4654
removing the object aggregator will break the remaining pipeline, so that
option is out too.
As for the client upload, that's exactly whats being done right now. The
jar is uploaded to the blob server, and only the blob key is transmitted via
REST. The problem here is that this also requires any client to be written in
java and rely on Flink, whereas we would prefer if any client, written in any
language, can communicate with the REST APIs.
> Remove the 10MB limit from the current REST implementation.
> -----------------------------------------------------------
>
> Key: FLINK-7521
> URL: https://issues.apache.org/jira/browse/FLINK-7521
> Project: Flink
> Issue Type: Bug
> Components: REST
> Affects Versions: 1.4.0
> Reporter: Kostas Kloudas
> Assignee: Fang Yong
> Priority: Blocker
> Fix For: 1.4.0
>
>
> In the current {{AbstractRestServer}} we impose an upper bound of 10MB in the
> states we can transfer. This is in the line {{.addLast(new
> HttpObjectAggregator(1024 * 1024 * 10))}} of the server implementation.
> This limit is restrictive for some of the usecases planned to use this
> implementation (e.g. the job submission client which has to send full jars,
> or the queryable state client which may have to receive states bigger than
> that).
> This issue proposes the elimination of this limit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
