Apache Hop version?
2.18-SNAPSHOT
Java version?
21
Operating system
Windows
What happened?
There appears to be a change in behavior in the TextFileOutput transform regarding default values.
When loading an existing pipeline where a field (e.g., enclosure) is explicitly set to an empty string (""), the value is not preserved. Instead, upon reopening the pipeline, the field is automatically populated with the default value.
This behavior differs from previous versions (e.g., 2.17), where empty string values were retained correctly when reloading a pipeline.
Steps to Reproduce:
Create or open a pipeline with a TextFileOutput transform.
Set a field such as enclosure to an empty string.
Save the pipeline.
Close and reopen the pipeline.
Expected Behavior:
The field should remain as an empty string ("") after reopening.
Actual Behavior:
The field is replaced with the default value.
Version:
Observed in current version (please specify if needed).
Not present in version 2.17.
Additional Context:
This may impact pipelines that rely on explicitly empty values rather than defaults.
We have a lot of pipelines using the TextFileOutput to write a single field as Json/Xml files
Issue Priority
Priority: 3
Issue Component
Component: Transforms
Apache Hop version?
2.18-SNAPSHOT
Java version?
21
Operating system
Windows
What happened?
There appears to be a change in behavior in the TextFileOutput transform regarding default values.
When loading an existing pipeline where a field (e.g., enclosure) is explicitly set to an empty string (""), the value is not preserved. Instead, upon reopening the pipeline, the field is automatically populated with the default value.
This behavior differs from previous versions (e.g., 2.17), where empty string values were retained correctly when reloading a pipeline.
Steps to Reproduce:
Create or open a pipeline with a TextFileOutput transform.
Set a field such as enclosure to an empty string.
Save the pipeline.
Close and reopen the pipeline.
Expected Behavior:
The field should remain as an empty string ("") after reopening.
Actual Behavior:
The field is replaced with the default value.
Version:
Observed in current version (please specify if needed).
Not present in version 2.17.
Additional Context:
This may impact pipelines that rely on explicitly empty values rather than defaults.
We have a lot of pipelines using the TextFileOutput to write a single field as Json/Xml files
Issue Priority
Priority: 3
Issue Component
Component: Transforms