xcube-dev / xcube-dev/xcengine
Implement better control over staged-out datasets
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 8
Description
Currently, every dataset in the namespace is staged out (or served in xcube, if the container is run in server mode). The simplest workaround is to del any datasets that should be ignored, but this can get awkward if there are too many of them. xcengine should offer an alternative output selection to let the user explicitly choose which datasets are to be exported. A collection with a reserved name (xce_output_datasets or similar) would be easy, but would require reading documentation to use. Maybe there is some more discoverable alternative.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how xcengine currently stages every namespace dataset and how server mode serves them. Decide on a discoverable way for users to select output datasets, then verify that non-selected datasets are neither staged out nor served. The issue names no files or tests, so the relevant entry points must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100