Solve issue #2382#2386
Open
francescoingv wants to merge 2 commits into
Open
Conversation
BaseProcessor: added hook remove_resources() to enable derived classes to handle removal of resources PostgreSQLManager and TinyDBManager: modified delete_job() to call processor.remove_resources(job_id) when result files are removed. DummyManager and MongoDBManager: do not modified as not handling result files
Contributor
Author
|
@tomkralidis you may find the Processor class in file in #2388 useful for review and testing. Please note the configuration required: <processor_ID>:
type: process
processor:
name: 'pygeoapi.process.extended_output_only.ExtendedEchoProcessor'
base_reference_url: 'http://<URL_for_results_by_reference>/'
base_reference_dir: <path_to_write_results_accessed_by_reference>/
With the which will create the file to be used for reference: After the command Without this PR: With this PR: |
francescoingv
added a commit
to francescoingv/expose-pygeoapi-plugins
that referenced
this pull request
Jul 13, 2026
Currently the core Manager (PostgreSQLManager) on receiving a delete_job(<job_id>) does not advise the Processor which executed the job. If the Processor created resources (e.g. files) as part of the elaboration, then the Processor is the only entity aware of it, and is necessary to advise the Processor to (possibly, depending on the service policy) remove the resource. The issue (geopython/pygeoapi#2382) was created, and associated PR (geopython/pygeoapi#2386) to solve it. Until the PR will be inserted in the core framework, a temporary custom manager extending PostgreSQLManager will be used.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Enable the Processor to delete resources created when a job DELETE is submitted #2382
Related Issue / discussion
Solve issue #2382
Additional information
BaseProcessor: added hook remove_resources() to enable derived classes to handle removal of resources
PostgreSQLManager and TinyDBManager: modified delete_job() to call processor.remove_resources(job_id) when result files are removed.
DummyManager and MongoDBManager: do not modified as not handling result files
Dependency policy (RFC2)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)