Add some additional mutually exclusive tags to the collisions list #316
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Documentation preview |
oliverholworthy
approved these changes
May 10, 2023
gabrielspmoreira
approved these changes
May 11, 2023
oliverholworthy
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@gabrielspmoreira pointed out some additional tags that are mutually exclusive with being tagged as an embedding. This adds those mutually exclusive tags to a list of "collisions"—tags that removed from a schema/
TagSetwhen another tag is added. This partially addresses an issue with tag propagation in the dataloader'sEmbeddingOperator.