CarlosJuncher03 opened a new issue, #8509:
URL: https://github.com/apache/hop/issues/8509

   ### What would you like to happen?
   
   Currently, when using Database as the storage type for Execution 
Information, executions from multiple projects can be stored in the same 
database.
   
   In our environment, we use a single database to store execution history for 
many Apache Hop projects. Creating and maintaining a separate database for each 
project would introduce significant administrative and maintenance overhead.
   
   It would be useful to have a way to identify the project directly in the 
Execution Information connection metadata.
   
   For example, a Project ID field could be added. This identifier could:
   
   Be manually defined, such as a UUID;
   Use an existing Apache Hop project identifier, if one is available;
   Or be automatically generated and managed by Hop.
   
   This identifier would then be stored together with each execution record.
   
   When viewing Execution Information, Hop could identify the currently active 
project and automatically filter the execution history to display only 
executions associated with that project.
   
   Example
   
   A single Execution Information database could be shared by multiple projects:
   
   Project A → project_id = uuid-a
   Project B → project_id = uuid-b
   Project C → project_id = uuid-c
   
   When working with Project B, the Execution Information history would show 
only executions where project_id = uuid-b.
   
   Benefits
   
   This would allow multiple Apache Hop projects to share the same Execution 
Information database while keeping their execution histories logically isolated.
   
   It would also avoid the need to create and maintain a separate database or 
Execution Information storage configuration for every project.
   
   ### Issue Priority
   
   Priority: 3
   
   ### Issue Component
   
   Component: Infrastructure


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to