[
https://issues.apache.org/jira/browse/NIFI-16537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136790#comment-18136790
]
ASF subversion and git services commented on NIFI-16537:
--------------------------------------------------------
Commit eee7824b3e3b81b9db6cd6c0e3480356c46727f5 in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=eee7824b3e3 ]
NIFI-16537 Fixed BitbucketFlowRegistryClient failing to commit large flow to
Bitbucket Cloud (#11876)
Signed-off-by: David Handermann <[email protected]>
> BitbucketFlowRegistryClient fails to commit large flow to Bitbucket Cloud
> -------------------------------------------------------------------------
>
> Key: NIFI-16537
> URL: https://issues.apache.org/jira/browse/NIFI-16537
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions, Flow Versioning
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Committing a versioned process group through BitbucketFlowRegistryClient
> against Bitbucket Cloud fails once the flow JSON is larger than about 2.5 MB:
>
> {code:java}
> Failed to register flow with Flow Registry due to Could not parse response
> from Bitbucket API
> Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected
> character ('<' (code 60)) ... line: 2, column: 1{code}
>
> Bitbucket Cloud answers POST /2.0/repositories/\{workspace}/\{repo}/src with
> HTTP 400 and a generic HTML "Bad Request (400)" page. The client sends the
> flow content as a multipart part without a filename, so Bitbucket handles it
> as a plain form field rather than a file upload. That field is subject to a
> request size limit, apparently around 2.5 MB. Smaller flows commit without
> problems.
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
