[GOBBLIN-1981] Renames writer.path.type config name as it has a type conflict with w… #3852
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.
…riter.path
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA
Description
There are some properties in Gobblin that are not typesafe when put in a Config class object, this causes issues with GaaS passing those properties to Gobblin cluster.
To resolve this, we should fix the property names so that there are no conflicts.
The property in particular we want to change is
writer.file.path.type
that conflicts withwriter.file.path
due to sharing the same prefix but expanding the key when there's a value mapped to it (making it not type safe as it can't transform a string value to a map). We can rename this property to writer.file.pathType.Tests
Backwards compatible
Commits