feat: add pgstac settings for use_queue and update_collection_extent#241
Open
feat: add pgstac settings for use_queue and update_collection_extent#241
Conversation
hrodmn
force-pushed
the
feat/pgstac-update-collection-extent
branch
from
a1fdecf to
673356f
Compare
bitner
reviewed
Mar 23, 2026
bitner
reviewed
Mar 23, 2026
bitner
approved these changes
Mar 23, 2026
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
2 participants
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.
https://github.com/developmentseed/eoapi-cdk/actions/runs/23444262491/job/68203481014
Merge request description
This adds the ability to switch on
pgstac.update_collection_extentwhich updates collection extents based on the items contained within the collection. The best way to use this for catalogs that have a lot of transactions is to use pg_cron with a queue so I added that as an option for the the database bootstrapper also.This might be considered a breaking change because the database boostrapper API changes a bit, but I'm still thinking about that.This is not a breaking change because the default behavior has not changed, if a user has a custom bootstrap runtime these change will not affect them.