-
Notifications
You must be signed in to change notification settings - Fork 362
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]: Execution Information transform fails on LogLevel #2312
Comments
can't reproduce with any execution information data that was generated after 2023-01-20, so I assume this was caused by an issue that has been fixed in the meantime. closing for now. |
closed to soon. this doesn't cause the pipeline to fail (anymore), but the errors are still available in the logs. |
Hello everyone, I'm experiencing the same issue. In a complex workflow involving multiple pipeline executions, each pipeline concludes with a non-fatal error message appearing in the logs. Regrettably, I encountered the same issue with the "Sort by" transformation in one instance. It seems that rows were being stored in temporary files, and upon retrieval, this error message would appear in the logs, causing the transformation to fail. As far as I understand, the issue stems from a String field being parsed as a long by Jackson, resulting in a mismatch with the expected meta type string. While I can tolerate this error at the end of a pipeline execution, a failure during sorting is highly frustrating. I will work on creating a reproducible example with less data and provide it as soon as possible. Thank you.
|
Hello again, so now I stumbled across a similar error message when previewing the result of the attached dataflow. The issue is, in the bigger pipeline, where I need this database join, I can't see with the preview, why the number of rows is not increasing as expected by the database lookup, due to this error message maybe. I'm working on a Mac M1 with Java openjdk version "17.0.3" 2022-04-19 |
Hi, I'm experiencing almost the same issue with the following environment :
I'm having a complex workflow with
Whatever the cast I use in the csv extraction it failed. |
I have taken a look at this a while back and I know where the issue is coming from. We are currently using references to the row data to store the sample data. When changing the datatype (using select values) this causes a mismatch between the object type and the metadata when trying to store the sample rows. The implementation will have to be changed a bit to do a deep copy of the sample data. This will cause a bit more memory usage but the casting errors should go away FYI. these errors are related to the execution information perspective and will not cause a pipeline to fail |
waow.... a great thanks for this answer, |
.take-issue |
Apache Hop version?
SNAPSHOT-20230211
Java version?
openjdk version "11.0.17" 2022-10-18
Operating system
Linux
What happened?
Issue Priority
Priority: 1
Issue Component
Component: Transforms
The text was updated successfully, but these errors were encountered: