Ignore unknown Properties from config file when parsing #2336
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.
Motivation
As Functions evolve, we will be adding new properties/fields to the FunctionConfig. There will be fields present in the config files that won't make sense for previous admin tool installation. This especially happens when submitting pulsar functions using newer client to run over kubernetes with an older installation of pulsar. This pr will mark the unknown fields to be ignored to get over that problem
Modifications
Describe the modifications you've done.
Result
After your change, what will change.