mattcasters opened a new pull request, #7709: URL: https://github.com/apache/hop/pull/7709
## Summary - Adds a **Caching Database** execution information location plugin that stores the same aggregated `CacheEntry` JSON used by Caching File / Elastic / OpenSearch in a single relational table (filter columns + CLOB/TEXT), reusing `BaseCachingExecutionInfoLocation`. - Avoids the old Kettle multi-table 3NF logging schema: one table, dialect-agnostic DDL via Hop’s `Database`/`DatabaseMeta`, and indexes on fields used for filtering (name, type, start date, failed, parent id, status). - GUI: relational connection, optional schema, table name (default `hop_executions`), inherited persistence delay / max cache age, and a **Show table and indexes DDL** button (Neo4j-style, does not execute). ## How it works - One row per top-level pipeline/workflow execution (`id` = log channel id as PK). - Full execution detail (state, children, samples, logging text) stays in the `json` column. - `retrieveIds` pushes `IExecutionSelector` filters into SQL for efficient listing without loading CLOBs. ## Test plan - [x] Unit tests with H2 in-memory (`CachingDatabaseExecutionInfoLocationTest`: round-trip, upsert, filters, DDL, `getExecutionIds` order) - [ ] Create a relational connection in Hop GUI - [ ] Create an Execution Information Location of type **Caching Database location** - [ ] Use **Show table and indexes DDL** and run the statements on the database - [ ] Run a pipeline/workflow with this location and verify entries appear in the Execution Information perspective - [ ] Exercise filters (name, type, failed, date range) in the perspective Fixes #2207 -- 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]
