0

I am experimenting with Apache HOP to become the successor of the (dead end) SSIS ETL platform. I am very impressed with the quality and the performance of Apache HOP so far.

I am trying to load data from Table Input (jdbc, progress openedge) into postgresql via the PostgreSQL Bulk Loader. I think I found a bug in the process:

If I run a pipeline that uses a table input step and have HOP find some fields are Boolean types it will represent like this:

boolean field

Based on DDL this is correct - this is a boolean field.

enter image description here

My problem now is that if I run this pipeline there seems to be a problem between the "internal data model" of HOP (whatever this may be) and the data handed over to the PostgreSQL Bulk Loader step:

2025/10/24 08:10:01 - PostgreSQL Bulk Loader.0 - ERROR: Error in transform 
2025/10/24 08:10:01 - PostgreSQL Bulk Loader.0 - ERROR: org.postgresql.util.PSQLException: ERROR: invalid input syntax for type boolean: "1.0"   Where: COPY glimsds_order, line 1, column ord_addtobudget: "1.0"

Is this a bug someone can reproduce? I had the same problem with other data sources like salesforce (boolean).

I was able to mitigate this problem (accidentally) by using a formula and have it look for 1.0 and translate it to 1 but this actually never worked as intended. What fixed the problem was casting it to string (by accident) and this then lead to 1 instead of 1.0 what postgresql happily loaded.

Is there a way to further look into the inner data model or system of HOP? Is there a way to tell HOP this is a String (N) not a Boolean? Any other elegant solution?

Thanks! :)

1

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.