Support "RpcHttpBodyOnly"capability

[yojagad]

Host has a "RpcHttpBodyOnly" capability where it does not send duplicated data through gRPC. It only sends the "body" property which is either bytes or string.

Reference PR: Azure/azure-functions-host#4660

Java needs to make modifications on the worker side accordingly in order to decode it whenever necessary.

Also need to support RpcHttpTriggerMetadataRemoved Reference https://github.com/Azure/azure-functions-nodejs-worker/pull/238/files

[pragnagopa]

cc @mathewc @amamounelsayed / @anirudhgarg - Is it possible to address this issue this sprint? this fix is critical to the perf improvement that @mathewc is working on and specifically he has chosen java worker for making out-of-proc improvements

[anirudhgarg]

Thanks @pragnagopa for flagging this. @TsuyoshiUshio will be helping on this with @amamounelsayed's help.

[amamounelsayed]

@pragnagopa @anirudhgarg I talked to @mathewc this fix we do our best to have it in this sprint or next one. Thank you so much!

[TsuyoshiUshio]

Hi @yojagad , Let me understand the context for the RpcHttpTriggerMetadataRemoved. I read the code on this https://github.com/Azure/azure-functions-nodejs-worker/pull/238/files Inside of the PR, I found the code set the req and $request in triggerMetadata in case of undefined/null. Why do we need it? I can implement it on Java, however, I want to understand the context.

[TsuyoshiUshio]

@yojagad Self Resolved. :) Never mind. I'll create a PR.

[amamounelsayed]

https://github.com/Azure/azure-functions-java-worker/pull/364

[TsuyoshiUshio]

@pragnagopa @amamounelsayed Can we close this issue? or keep until the functions host is released?

[amamounelsayed]

@TsuyoshiUshio, The reason is not closed it is not released yet. @anirudhgarg point to not create confusion, so we close it after release.

[MadhuraBharadwaj-MSFT]

Hi @amamounelsayed - could you confirm if this issue can be closed?