Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Hop 2.8.0 - When running a workflow using Hop remote workflow engine, with pipelines containing the "Combination lookup-update" step when building the dispatch zip, the connection properties disappear. #3699

Closed
Raul-rp opened this issue Mar 6, 2024 · 9 comments
Assignees
Milestone

Comments

@Raul-rp
Copy link

Raul-rp commented Mar 6, 2024

Apache Hop version?

2.8.0, 2.7.0

Java version?

11

Operating system

Windows

What happened?

When running a workflow using Hop remote workflow engine, with pipelines containing the "Combination lookup-update" step when building the dispatch zip, the connection properties disappear.

ORIGINAL (Local) :

Combination lookup/update CombinationLookup Y 1 none 9999 100 **FE0VSQL218** N hashcode AGENT AGENT tablemax AGENT_ID N N N dm_honda_me dim_agent
576 224

ZIP in Hop server :

Combination lookup/update CombinationLookup Y 1 none 0 0 N N N N 576 224

Issue Priority

Priority: 1

Issue Component

Component: Hop Gui, Component: Hop Server

@Raul-rp
Copy link
Author

Raul-rp commented Mar 6, 2024

test.zip
Attached is an example of ETL to be sent to the Hop server that reproduces the bug.

@Raul-rp
Copy link
Author

Raul-rp commented Mar 6, 2024

Message
error.zip
issue_analysis.zip

@Raul-rp Raul-rp changed the title [Bug]: When running a workflow using Hop remote workflow engine, with pipelines containing the "Combination lookup-update" step when building the dispatch zip, the connection properties disappear. [Bug]: Hop 2.8.0 - When running a workflow using Hop remote workflow engine, with pipelines containing the "Combination lookup-update" step when building the dispatch zip, the connection properties disappear. Mar 14, 2024
@Raul-rp
Copy link
Author

Raul-rp commented Mar 14, 2024

Same issue in Hop 2.8.0 version

@RaulBSC
Copy link

RaulBSC commented Oct 14, 2024

Same issue in Hop 2.10.0 version

@NicoDupont
Copy link

NicoDupont commented Nov 7, 2024

I have the same error with 2.10.0.
The workflow works well with hop gui local run config and docker with local run config.
Not tested with Hop-Run.
I got the same error when I start the workflow from hop-gui with the remote execution configuration or from a docker with the remote execution configuration.

Error from the server log :

Initialisation of pipeline failed: 2024/11/07 13:24:02 - HopServer - Installing timer to purge stale objects after 2880 minutes.2024/11/07 13:24:02 - HopServer - Created listener for webserver @ address : svetltest:81812024/11/07 13:52:00 - fait_pointage - Executing this pipeline using the Local Pipeline Engine with run configuration 'local'2024/11/07 13:52:00 - fait_pointage - Execution started for pipeline [fait_pointage]2024/11/07 13:52:00 - RechercheSalarie.0 - ERROR: Database connection is missing for transform [RechercheSalarie]!2024/11/07 13:52:00 - RechercheSalarie.0 - ERROR: Error initializing transform [RechercheSalarie]2024/11/07 13:52:00 - fait_pointage - ERROR: Transform [RechercheSalarie.0] failed to initialize!2024/11/07 13:52:00 - R?cuperation Donn?es Visor.0 - Finished reading query, closing connection.HopException: We failed to initialize at least one transform. Execution can not begin!Root cause: HopException: We failed to initialize at least one transform. Execution can not begin!org.apache.hop.core.exception.HopException: We failed to initialize at least one transform. Execution can not begin!

image

@hansva
Copy link
Contributor

hansva commented Nov 8, 2024

.take-issue

@github-actions github-actions bot added this to the 2.11 milestone Nov 8, 2024
@hansva hansva closed this as completed in ef3a097 Nov 8, 2024
hansva added a commit that referenced this issue Nov 8, 2024
@NicoDupont
Copy link

The problem seems to persist in 2.11
just testing this morning

25/01/17 11:56:29 - Recherche dans base de donn�es.0 - ERROR: Database connection is missing for transform [Recherche dans base de donn�es]!2025/01/17 11:56:29 - Recherche dans base de donn�es.0 - ERROR: Error initializing transform [Recherche dans base de donn�es]2025/01/17 11:56:29 - Insertion dans table PAIE_ABSENCE_LONGUE_MALADIE.0 - Connected to database [Data Warehouse] (commit=1000)2025/01/17 11:56:29 - calcul_longue_absence - ERROR: Transform [Recherche dans base de donn�es.0] failed to initialize!2025/01/17 11:56:29 - Extraction depuis table DIM_DATE.0 - Finished reading query, closing connection.2025/01/17 11:56:29 - Extraction Absences Type Maladie.0 - Finished reading query, closing connection.2025/01/17 11:56:29 - Extraction depuis table DIM_DATE 2.0 - Finished reading query, closing connection.2025/01/17 11:56:29 - Extraction depuis table FAIT_INDICATEURS_STATS_SOCIALES.0 - Finished reading query, closing connection.HopException: We failed to initialize at least one transform. Execution can not begin!Root cause: HopException: We failed to initialize at least one transform. Execution can not begin!org.apache.hop.core.exception.HopException: We failed to initialize at least one transform. Execution can not begin!

@hansva
Copy link
Contributor

hansva commented Jan 17, 2025

The original issue talked about the combination lookup/update and not the Database lookup. So that was the only thing that got fixed here.

@NicoDupont
Copy link

oh yes confusion. i can make a ticket ? for database lookup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants