Version-specific resource references
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 134
- Forks
- 24
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 8
Description
It is valid to have a reference from a resource to a specific technical version of another resource (see Literal References).
This change will recognise references of this form, and add the necessary conditions to the join to match the versionId within the meta element of the target resources.
This functionality will be turned off by default for performance reasons, and will need to be enabled via configuration. The following will be added to the default configuration:
pathling:
query:
versionSpecificReferencesEnabled: false
This may also relate to #162, if we choose to store historical versions of updated resources.
See also: #217
Contributor guide
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
No implementation file or test is named. Start by reviewing the query configuration and resource-join entry points, then read related issues #162 and #217. Done means version-specific references match the target resource's meta.versionId, while the behavior remains disabled by default and can be enabled with the documented YAML setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100