Migrate UDF operator transformers based on JSON-infra into transformers based on native Java code #350
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.
In order to migrate all the transformers in which any of
operatorTransformer,operandTransformerandresultTransformeris defined as a JSON string into the transformers which define the transformation rule in native Java code, the following code changes are made in this PR:SignatureBasedConditionSqlCallTransformerand the specific transformation logic is defined as native Java code includingDateDiffOperatorTransformerDateSubOperatorTransformerDateAddOperatorTransformerDecodeOperatorTransformerRegexpExtractOperatorTransformerModOperatorTransformerTruncateOperatorTransformerRandomIntegerOperatorWithTwoOperandsTransformerRandomOperatorWithOneOperandTransformeroperatorTransformer,operandTransformerandresultTransformerdefined as JSON strings out of the class ofSignatureBasedConditionSqlCallTransformerTo be noted that this PR is based on PR #349