Skip to content
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

[Feature Request]: Static schema enhancements #4308

Open
bamaer opened this issue Sep 10, 2024 · 0 comments
Open

[Feature Request]: Static schema enhancements #4308

bamaer opened this issue Sep 10, 2024 · 0 comments
Assignees
Milestone

Comments

@bamaer
Copy link
Contributor

bamaer commented Sep 10, 2024

What would you like to happen?

  1. There is no auto refresh or alerting feature when there is any change in the static schema definition, we can only identify this when a job fails due to schema mismatch. We need to populate the change by manually opening each action which used that schema and select the schema name again from the dropdown. In talend, there is an option to propagate the schema changes to all related jobs once it is changed. This will be particularly useful when the same schema is being used under multiple jobs.

  2. There is no option to segregate the schema definitions under relevant sub folders for ease of use. I have tried placing the schema definitions under sub folders inside config\projects\default\metadata\schema-definition , but after placing them in folders, the schemas are not getting listed in the drop down for usage. This will be helpful to easily fetch the schema names from a huge list while selecting inside actions.

  3. Upon choosing the static schema inside Text file input or output actions, it automatically populates currency as the system default currency symbol, though we are not setting any currency inside static schema configuration.

Issue Priority

Priority: 3

Issue Component

Component: Metadata, Component: Transforms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants