You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "CarlosJuncher03 (via GitHub)" <gi...@apache.org> on 2026/02/03 16:47:18 UTC
[I] [Feature Request]: Execution Information Location: retention policy (by count / by days) (hop)
CarlosJuncher03 opened a new issue, #6497:
URL: https://github.com/apache/hop/issues/6497
### What would you like to happen?
Title
Execution Information Location: add retention policy (keep last N / keep last X days)
Problem
Execution Information Location keeps accumulating execution records (e.g., log_file location) without built-in retention controls. In long-running production usage this increases disk usage and makes later analysis/navigation slower.
Proposal
Add optional retention settings to Execution Information Location metadata:
Retention by count: keep last N executions per pipeline/workflow (or per location), delete older records automatically.
Retention by age: keep executions for last X days, delete older records automatically.
Option to choose scope:
per “location” (global)
per pipeline/workflow name (recommended)
Acceptance criteria
When retention is enabled, older execution records are removed automatically.
Deletion should be safe: remove only records belonging to the configured location.
Works for “local/log_file” execution information location and any other supported backend.
Retention runs:
on write (after storing a new execution), and/or
as a periodic cleanup task (configurable)
Notes / rationale
This supports production hygiene and avoids external scripts for rotation/cleanup.
### Issue Priority
Priority: 3
### Issue Component
Component: Hop Gui, Component: Metadata
--
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: issues-unsubscribe@hop.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Execution Information Location: retention policy (by count / by days) (hop)
Posted by "CarlosJuncher03 (via GitHub)" <gi...@apache.org>.
CarlosJuncher03 commented on issue #6497:
URL: https://github.com/apache/hop/issues/6497#issuecomment-6353774352
I’ll test it, thanks.
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Execution Information Location: retention policy (by count / by days) (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #6497:
URL: https://github.com/apache/hop/issues/6497#issuecomment-3842657809
For this one, I would not run this every time the hop-run triggers, as it will have performance drawbacks.
This should be run only when the GUI is opened or using a separate command via hop-config
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Execution Information Location: retention policy (by count / by days) (hop)
Posted by "mattcasters (via GitHub)" <gi...@apache.org>.
mattcasters commented on issue #6497:
URL: https://github.com/apache/hop/issues/6497#issuecomment-6270893236
Preferable solution: https://hop.apache.org/manual/next/workflow/actions/deleteexecutioninfo.html
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Execution Information Location: retention policy (by count / by days) (hop)
Posted by "CarlosJuncher03 (via GitHub)" <gi...@apache.org>.
CarlosJuncher03 commented on issue #6497:
URL: https://github.com/apache/hop/issues/6497#issuecomment-3842848137
It would be good by command. That way it would stay adjusted in the orchestrator.
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Feature Request]: Execution Information Location: retention policy (by count / by days) (hop)
Posted by "mattcasters (via GitHub)" <gi...@apache.org>.
mattcasters commented on issue #6497:
URL: https://github.com/apache/hop/issues/6497#issuecomment-3935074287
I'm equally torn. In the old database logging variant in the Previous Data Integration variant, automatic cleanup was a real pain.
I personally think that it's easier to just create a workflow or pipeline that removes old files, index entries or nodes/relationships from the execution information location of your choice.
A compromise would be to have a dedicated action that can remove data from an execution information location.
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org