Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
We have simple pipeline as shown in the picture below
The Database Join contains a simple query (tables independent as you can see) that works (in my case I configured it to work with a postgres database). On the other side, the Filter in error contains a filter on a field that do not exists in the input rowset.
If we start the pipeline, it immediately hangs and we don't have any possibility to look at in the log's view of Hop GUI. If we look at the console window we get the log and it is like this
If we comment the Database Join, we substitute it with a write to log (for example) and we run it the pipeline goes in error but it closes correctly without hanging as before
Attached the sample to try it out. Remember to configure the connection before running the sample. The query is independent from any table contained in the database.
Attachments
Attachments
Issue Links
- links to