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.

Sign up for GitHub

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

Jump to bottom

replace-field-action is not adding the renames field to enabled list by default #460

Closed
hguerrero opened this issue Aug 11, 2021 · 2 comments
Closed

replace-field-action is not adding the renames field to enabled list by default #460

hguerrero opened this issue Aug 11, 2021 · 2 comments
Assignees
@oscerd
Milestone
0.7.0

Comments

@hguerrero
Copy link

When using the replace-field-action I would expect that the fields in the renames section will automatically be added to the enabled, and not need to add them manually.
@oscerd
Copy link
Contributor

oscerd commented Aug 11, 2021

What we are doing is similar to Kafka smt. Don't expect the same behavior.

@oscerd oscerd self-assigned this Aug 11, 2021
@oscerd
Copy link
Contributor

oscerd commented Jan 12, 2022

This has been fixed with #697 because the disabled and enabled fields are now not mandatory.

@oscerd oscerd mentioned this issue Jan 12, 2022
Merged
@oscerd oscerd closed this as completed Jan 12, 2022
@oscerd oscerd added this to the 0.7.0 milestone Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oscerd oscerd

Labels
None yet
Projects
None yet
Milestone
0.7.0
Development

No branches or pull requests
2 participants
@hguerrero @oscerd