-
Notifications
You must be signed in to change notification settings - Fork 1
GSIP 183
Proposal to add per workspace Stored Queries for WFS 2.0, allowing to store them at workspace resources folder and having same ID on several different Workspace attached Stored Queries.
Fernando Miño
This proposal is for GeoServer 2.17 beta and 2.16.3.
- Setup
- Under Discussion
- In Progress
- Completed
- Rejected
- Deferred
Sometimes we would need to register stored queries with same ID on difference virtual services, having the limit of one id for all virtual services prevents user to use virtual service at its maximum potential.
The core concept is that we will allow the creation of stored queries per workspace:
- when creating a stored query, if a workspace virtual service end-point is used, then the query will belong to that workspace:
- but that query will only be visible \ usable from that workspace virtual end-point
- if no workspace virtual service is used, then the stored query will be global
In terms of stored queries usage (list stored queries, execute a stored query, etc ...):
- When targeting the global GeoServer end-point, only global stored queries will be visible:
- hence two stored queries of different workspaces can have the same id.
- When targeting a workspace virtual service end-point, the workspace stored queries and global stored queries that don't collide (don't have the same id) will be considered:
- Considering also global queries will allow the definition of more generic stored queries, hence removing the need of duplication.
- Considering global queries will be activated by default, but can be deactivated (flag in the WFS workspace configuration).
In terms of backwards compatibility:
- Global stored queries will be stored as they are now, so no data directory migration need
- For backwards compatibility, a flag deactivating per workspace stored queries will be added:
- if an user was using a virtual service end-point for creating stored-queries (we can do that now but the stored query will be global anyway), it can use that global flag to deactivate the new functionality
This proposal is fully backward compatible, users will not be affected by this unless they activate the functionality and start registering Stored Queries inside virtual services scope.
Project Steering Committee:
- Alessio Fabiani: +0
- Andrea Aime: +0
- Ian Turton: +1
- Jody Garnett: +1
- Jukka Rahkonen: +1
- Kevin Smith:
- Simone Giannecchini: +0
- Torben Barsballe
- Nuno Oliveira: +0
- Email Discussion
- Pull Request
- Jira issue
©2020 Open Source Geospatial Foundation