GH-2749 Include Namespaces in Statement imports from NamespaceAware collections #4262
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.
Signed-off-by: Dzerom Dzenkins dzeri96@proton.me
GitHub issue resolved: #2749
Briefly describe the changes proposed in this PR:
As suggested by @jeenbroekstra, I've added a call to
setNamespace
for all new namespaces coming from the importedStatement
s, and I've removed the appropriate overrides in the SPARQL repository, as it seems like the code was almost identical. Please correct me if I'm wrong.Since this is a WIP, there are some things to clear up:
Iteration
overload of theadd
method? I suspect this might get removed with the next release so I haven't added any changes there.remove
method? Should we prune unusedNamespace
s?As soon as these questions are cleared up, and the flaky tests are fixed, I'll continue working on this PR!
PR Author Checklist (see the contributor guidelines for more details):
mvn process-resources
to format from the command line)