-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Fix][Core] Fix the placeholders cannot pass parameters when using complex config #9800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…s when using multiple tables for reading in JDBC Source
| System.getProperty(placeholder), | ||
| null); | ||
| }); | ||
| } else if (variable instanceof Map) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what if variable is list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I indeed never expected a scenario where a list is nested within another list. If such a case exists, I think I could add another if (variable instanceof List) to recursively call itself
…hen using complex configurations (including List in List)
seatunnel-core/seatunnel-core-starter/src/test/resources/config_complex_nested_variables.conf
Outdated
Show resolved
Hide resolved
...nnel-core-starter/src/test/java/org/apache/seatunnel/core/starter/utils/ConfigShadeTest.java
Show resolved
Hide resolved
Hisoka-X
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @LeonYoah
Carl-Zhou-CN
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Close #9797 where placeholders cannot pass parameters when using multiple tables for reading in JDBC Source
Purpose of this pull request
Does this PR introduce any user-facing change?
How was this patch tested?
Check list
New License Guide