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

[Bug]: Enhanced JSON Output transform seems to miss options, generates different results when #2817

Closed
bamaer opened this issue Apr 11, 2023 · 1 comment · Fixed by #2873
Closed

Comments

@bamaer
Copy link
Contributor

bamaer commented Apr 11, 2023

Apache Hop version?

SNAPSHOT-20230411

Java version?

openjdk version "11.0.18" 2023-01-17

Operating system

Linux

What happened?

the results for the included sample transform are different for output value and generated files and don't match the options described in the doc page

also: add an IT for this transform, add the sample in the documentation as a pipeline in the samples project and update the documentation to point to the sample instead of describing the options.

enhanced-json-output.hpl.txt

Issue Priority

Priority: 2

Issue Component

Component: Documentation, Component: Integration Testing, Component: Samples, Component: Transforms

@bamaer
Copy link
Contributor Author

bamaer commented Apr 11, 2023

update: the group key doesn't seem to be used. field output returns 3 rows instead of 1, the contents of the file output is the json generated in the third row

@sramazzina sramazzina self-assigned this Apr 18, 2023
@sramazzina sramazzina added this to the 2.5 milestone Apr 20, 2023
sramazzina added a commit to sramazzina/hop that referenced this issue Apr 26, 2023
@sramazzina sramazzina mentioned this issue Apr 27, 2023
5 tasks
sramazzina added a commit to sramazzina/hop that referenced this issue Apr 27, 2023
hansva added a commit that referenced this issue Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants