Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release for v0.8.2 #228

Merged
merged 1 commit into from
Nov 14, 2023
Merged

Release for v0.8.2 #228

merged 1 commit into from
Nov 14, 2023

Conversation

bitner
Copy link
Collaborator

@bitner bitner commented Nov 14, 2023

Added

  • Add support functions and tests for Collection Search
  • Add configuration parameter for base_url to be able to generate absolute links
  • With this release, this is only used to create links for paging in collection_search
  • Adds read only mode to allow use of pgstac on read replicas
  • Note: Turning on romode disables any caching (particularly when context is turned on) and does not allow to store q query hash that can be used with geometry_search.
  • Add option to pypgstac loader "--usequeue" that forces use of the query queue for the loading process
  • Add "pypgstac runqueue" command to run any commands that are set in the query queue

Fixed

  • Fix bug with end_datetime constraint management leading to inability to add data outside of constraints
  • Fix bugs dealing with table ownership to ensure that all pgstac tables are owned by the pgstac_admin role
  • Fixes issues with errors/warnings caused when doing index maintenance
  • Fixes issues with errors/warnings caused with partition management
  • Make sure that pgstac_ingest role always has read/write permissions on all tables
  • Remove call to create_table_constraints from check_partition function. create_table_constraints was being called twice as it also gets called from update_partition_stats
  • Add NOT NULL constraint to collections table (FIXES Don't allow Collections without ids to be written #224)
  • Fix issue with indexes not getting created as the pg_admin role using SECURITY DEFINER

Changed

  • Revert pydantic requirement back to '>=1.7' and use basesettings conditionally from pydantic or pydantic.v1 to allow compatibility with pydantic 2 as well as with stac-fastapi that requires pydantic <2

@bitner bitner merged commit 8ef8552 into main Nov 14, 2023
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Don't allow Collections without ids to be written
2 participants