-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor pipelines to include contentSources #83
Conversation
…-engine into feature/contentpipelines
...engine-index/src/main/kotlin/org/vitrivr/engine/index/transform/ContentMergingTransformer.kt
Outdated
Show resolved
Hide resolved
…-engine into feature/contentpipelines
…files to be removed at a later stage.
…es' of github.com:vitrivr/vitrivr-engine into feature/contentpipelines
…her than descriptor to content.
…from template rather than given separately.
…-engine into feature/contentpipelines
…-engine into feature/contentpipelines
Hey, this PR is ready to review. We will add the documentation to the wiki once its merged. |
…-engine into feature/contentpipelines
…-engine into feature/contentpipelines
…-engine into feature/contentpipelines
It seems like the two concerns left unchanged in the latest commits are:
I have made the appropriate comments addressing these issues above. |
…-engine into feature/contentpipelines
Preventing naming conflicts e.g. "end"
What is the state of this PR? Have all issues been addressed? Currently, there are two merge-conflicts which ought to be resolved. Also, please make sure that all tests run successfully. |
Me and raphi will merge this today |
We discussed this in person.
This PR addresses the problem of multiple branches in a pipeline getting in each others way, by changing the use of retrievables to be append only. It is still the job of pipeline configurator to avoid race conditions by making sure that only parts of the retrievable are processed that are not being further updated. This is made easier via configurable contentSources which allow the configurator to specify which content should be used for an operator using a white list of other operators. This description is not very complete and the code needs to be cleaned up. Therefore this PR is a draft.