decouple the function definition and function executor. #645
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue describing the changes in this PR
This PR mainly decoupled function definition (build at function load request processing) and function executor (build at invocation request process). It includes updates as below
FunctionLoadRequest
, now updated the logic to build the executor atInvocationRequest
.ExecutionContextDataSource
class topublic
, as this class is only used internal in java worker, it should cause any issue on changing it's scope topublic
.ExecutionContextDataSource
to use builder pattern as it has to many arguments in old constructor.dataStore
,methodBindInfo
,containingClass
toExecutionContextDataSource
, since decoupled the function definition and function executor, now function executor relies onExecutionContextDataSource
to get all required objects.MethodBindInfo
,ParamBindInfo
from nested class to top class as they are used by other class besides their parent class.Tried best to minimize the changes in this PR, all changes are necessary for the feature completeness.
Pull request checklist
release_notes.md
Additional information
Additional PR information