vitorsantos-commits commented on issue #7841:
URL: https://github.com/apache/hop/issues/7841#issuecomment-5219604080

   Hi @hansva, 
   
   Here is the full stacktrace from the logs during the execution attempt:
   
   ```text
   HopRowException: 
   We detected rows with varying number of fields, this is not allowed in a 
pipeline. The first row contained 24 fields, another one contained 0 : 
   
   Root cause: HopRowException: 
   We detected rows with varying number of fields, this is not allowed in a 
pipeline. The first row contained 24 fields, another one contained 0 : 
   2026/08/07 12:21:28 [Error]    RAW - 9 SolicitacaoItemOpme - Transform [Sel. 
Insert.0] failed to initialize!
   2026/08/07 12:21:28 [Error]    RAW - 9 SolicitacaoItemOpme - Transform 
[Insert.0] failed to initialize!
   2026/08/07 12:21:28 [Error]    RAW - 9 SolicitacaoItemOpme - Transform 
[Iniciar.0] failed to initialize!
   2026/08/07 12:21:28 [Error]    RAW - 9 SolicitacaoItemOpme - Transform 
[Gravar Log.0] failed to initialize!
   2026/08/07 12:21:28 [Error]    RAW - 9 SolicitacaoItemOpme - Transform [Sel. 
Dados.0] failed to initialize!
   2026/08/07 12:21:28 [Error]    Hop - RAW - 9 SolicitacaoItemOpme: preparing 
pipeline execution failed
   2026/08/07 12:21:28 [Error]    Hop - 
org.apache.hop.core.exception.HopException: 
   2026/08/07 12:21:28 [Error]    Hop - We failed to initialize at least one 
transform.  Execution can not begin!
   2026/08/07 12:21:28 [Error]    Hop -         at 
org.apache.hop.pipeline.Pipeline.prepareExecution(Pipeline.java:1120)
   2026/08/07 12:21:28 [Error]    Hop -         at 
org.apache.hop.pipeline.engines.local.LocalPipelineEngine.prepareExecution(LocalPipelineEngine.java:232)
   2026/08/07 12:21:28 [Error]    Hop -         at 
org.apache.hop.ui.hopgui.file.pipeline.HopGuiPipelineGraph.lambda$preparePipeline$18(HopGuiPipelineGraph.java:4733)
   2026/08/07 12:21:28 [Error]    Hop -         at 
java.base/java.lang.Thread.run(Thread.java:840)


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to