Relative URIs for Resource URLs in SOLR #211
Merged
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.
This is a solution to the Resource URLs in open-data/ckanext-language-domains#1
Basically the absolute URI of a resource is not stored in the database, but the res_url is stored in SOLR with a fully qualified URI for upload types. Instead, we modify code here to not store qualified URIs in SOLR and just add the requesting hostname to upload resource types for their download URI. And just add a
for_indexcontext when indexing packages/resources so that SOLR will always have the relative paths.I imagine this would kind of break other frameworkable parts of CKAN resource uploader...maybe. So not fitting for upstream contrib.