You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "bamaer (via GitHub)" <gi...@apache.org> on 2023/02/11 13:49:42 UTC
[GitHub] [hop] bamaer opened a new issue, #2312: [Bug]: Execution Information transform fails on LogLevel
bamaer opened a new issue, #2312:
URL: https://github.com/apache/hop/issues/2312
### Apache Hop version?
SNAPSHOT-20230211
### Java version?
openjdk version "11.0.17" 2022-10-18
### Operating system
Linux
### What happened?
```
2023/02/11 14:47:40 - exec-info-read - ERROR: Error handling writing final pipeline state to location (non-fatal)
2023/02/11 14:47:40 - exec-info-read - ERROR: org.apache.hop.core.exception.HopException:
2023/02/11 14:47:40 - exec-info-read - Error storing execution data
2023/02/11 14:47:40 - exec-info-read - logLevel String : There was a data type error: the data type of org.apache.hop.core.logging.LogLevel object [BASIC] does not correspond to value meta [String] (through reference chain: org.apache.hop.execution.ExecutionData["rowsBinaryGzipBase64Encoded"])
2023/02/11 14:47:40 - exec-info-read -
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.execution.local.FileExecutionInfoLocation.registerData(FileExecutionInfoLocation.java:256)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.pipeline.engines.local.LocalPipelineEngine.stopTransformExecutionInfoTimer(LocalPipelineEngine.java:486)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.pipeline.engines.local.LocalPipelineEngine.pipelineCompleted(LocalPipelineEngine.java:465)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.pipeline.Pipeline.firePipelineExecutionFinishedListeners(Pipeline.java:1343)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.pipeline.Pipeline.lambda$startThreads$0(Pipeline.java:1142)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.pipeline.transform.BaseTransform.fireTransformFinishedListeners(BaseTransform.java:2779)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.pipeline.transform.BaseTransform.markStop(BaseTransform.java:2768)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.pipeline.transform.RunThread.run(RunThread.java:142)
2023/02/11 14:47:40 - exec-info-read - at java.base/java.lang.Thread.run(Thread.java:829)
2023/02/11 14:47:40 - exec-info-read - Caused by: com.fasterxml.jackson.databind.JsonMappingException: logLevel String : There was a data type error: the data type of org.apache.hop.core.logging.LogLevel object [BASIC] does not correspond to value meta [String] (through reference chain: org.apache.hop.execution.ExecutionData["rowsBinaryGzipBase64Encoded"])
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:402)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:361)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ser.std.StdSerializer.wrapAndThrow(StdSerializer.java:316)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:782)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:178)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ser.DefaultSerializerProvider._serialize(DefaultSerializerProvider.java:480)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:319)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ObjectWriter$Prefetch.serialize(ObjectWriter.java:1572)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ObjectWriter._writeValueAndClose(ObjectWriter.java:1273)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ObjectWriter.writeValue(ObjectWriter.java:1098)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.execution.local.FileExecutionInfoLocation.registerData(FileExecutionInfoLocation.java:253)
2023/02/11 14:47:40 - exec-info-read - ... 8 more
2023/02/11 14:47:40 - exec-info-read - Caused by: java.lang.RuntimeException: logLevel String : There was a data type error: the data type of org.apache.hop.core.logging.LogLevel object [BASIC] does not correspond to value meta [String]
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.core.row.value.ValueMetaBase.writeData(ValueMetaBase.java:3105)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.core.row.RowMeta.writeData(RowMeta.java:717)
2023/02/11 14:47:40 - exec-info-read - at org.apache.hop.execution.ExecutionData.getRowsBinaryGzipBase64Encoded(ExecutionData.java:190)
2023/02/11 14:47:40 - exec-info-read - at jdk.internal.reflect.GeneratedMethodAccessor283.invoke(Unknown Source)
2023/02/11 14:47:40 - exec-info-read - at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2023/02/11 14:47:40 - exec-info-read - at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:689)
2023/02/11 14:47:40 - exec-info-read - at com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:774)
2023/02/11 14:47:40 - exec-info-read - ... 15 more
2023/02/11 14:47:40 - exec-info-read - Execution finished on a local pipeline engine with run configuration 'local'
```
### Issue Priority
Priority: 1
### Issue Component
Component: Actions
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [hop] bamaer closed issue #2312: [Bug]: Execution Information transform fails on LogLevel
Posted by "bamaer (via GitHub)" <gi...@apache.org>.
bamaer closed issue #2312: [Bug]: Execution Information transform fails on LogLevel
URL: https://github.com/apache/hop/issues/2312
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [hop] bamaer commented on issue #2312: [Bug]: Execution Information transform fails on LogLevel
Posted by "bamaer (via GitHub)" <gi...@apache.org>.
bamaer commented on issue #2312:
URL: https://github.com/apache/hop/issues/2312#issuecomment-1434862283
closed to soon. this doesn't cause the pipeline to fail (anymore), but the errors are still available in the logs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [hop] bamaer commented on issue #2312: [Bug]: Execution Information transform fails on LogLevel
Posted by "bamaer (via GitHub)" <gi...@apache.org>.
bamaer commented on issue #2312:
URL: https://github.com/apache/hop/issues/2312#issuecomment-1434848732
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Execution Information transform fails on LogLevel (hop)
Posted by "vdwals (via GitHub)" <gi...@apache.org>.
vdwals commented on issue #2312:
URL: https://github.com/apache/hop/issues/2312#issuecomment-1929224090
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: Execution Information transform fails on LogLevel (hop)
Posted by "vdwals (via GitHub)" <gi...@apache.org>.
vdwals commented on issue #2312:
URL: https://github.com/apache/hop/issues/2312#issuecomment-1943674782
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.
[mini-example-issue-2123.zip](https://github.com/apache/hop/files/14279371/mini-example-issue-2123.zip)
I'm working on a Mac M1 with Java openjdk version "17.0.3" 2022-04-19
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org