Hello, your error seems to be raised from the Select Values transform rather than Table Input, and is a known issue (see https://github.com/apache/hop/issues/2312).
The issue regards only the "auditing" process in Hop, and not the actual data flow: despite the error, you should have your fields correctly converted after the Select Values transform and that's why you don't see any error flag in Hop GUI. Hope this helps :) Il giorno mar 25 mar 2025 alle ore 13:41 AndersonCode42 < [email protected]> ha scritto: > Hello everyone, I'm a guy who is migrating from Pentaho Kettle to Apache > Hop and I've already faced my first obstacle. > > *Background*: > OS: Lubuntu 24.10 > Java: Temurin - 21.0.6+7 - LTS - JRE > Apache Hop: apache-hop-client-2.12.0.zip > > > I have a simple pipeline that basically should copy data from a table, > then use "Select values" (*hop.SelectValues.jpg*) to convert the field > types, and finally write it to another database table. > > However, when processing the rows, there is a row with a specific value > that throws an error in the log (*logging.txt*) and stops processing the > remaining rows. Strange fact: despite interrupting the processing, the > pipeline visually appears to have run successfully, since all components > have the green symbol (*hop.error.visual.is.ok.but.logging.is.error.jpg*) > > The field that caused the error, "cpf", in the source table is a > numeric(15) and in the destination table it is of type "text", that is, at > some point the type conversion is necessary. > > In Pentaho Data Integration (aka kettle) I didn't get this type of error. > The only difference is that in it, the "table input" component has the > "Enable Lazy Conversion" option, which I enabled. In Apache Hop, however, > this option doesn't exist, but it is listed in the official documentation ( > *hop.table.input.where.is.enable.lazy.conversion.jpg*) > > *Questions*: > - Does the "Enable Lazy Conversion" option exist or not in "Table Input"? > If it doesn't exist, how would I perform the type conversion. And if it > does, why doesn't it appear in my window? Could it be a bug? > - Is it normal for this error to be thrown in the logging and not > reflected in the visual part of the components? > > > >
