-
Notifications
You must be signed in to change notification settings - Fork 357
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
Comments
test.zip |
Message |
Same issue in Hop 2.8.0 version |
Same issue in Hop 2.10.0 version |
I have the same error with 2.10.0. 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! |
.take-issue |
The problem seems to persist in 2.11 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! |
The original issue talked about the combination lookup/update and not the Database lookup. So that was the only thing that got fixed here. |
oh yes confusion. i can make a ticket ? for database lookup |
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_agentZIP in Hop server :
Combination lookup/update CombinationLookup Y 1 none 0 0 N N N N 576 224Issue Priority
Priority: 1
Issue Component
Component: Hop Gui, Component: Hop Server
The text was updated successfully, but these errors were encountered: