forked from openedx/edx-platform
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Store content object collections in search index [FC-0062] #680
Closed
pomegranited
wants to merge
14
commits into
yusuf-musleh/collections-crud-rest-api
from
jill/collection-components-search
Closed
Changes from 4 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
bcc5cbb
fix: pass a ContentKey to the search doc handlers
pomegranited 0e32451
feat: add tags.collections to content object search index
pomegranited 3c6617e
temp: use openedx-events temporary branch
pomegranited 0c29552
feat: emit CONTENT_OBJECT_ASSOCIATIONS_CHANGED
pomegranited e20ee24
temp: use WIP openedx-events branch
pomegranited 9619341
test: fix test failing after changes to openedx-learning
pomegranited 1764e87
fix: emit both CONTENT_OBJECT_ASSOCIATIONS_CHANGED and CONTENT_OBJECT…
pomegranited ae7926f
docs: minor comment update
pomegranited 436822e
docs: replaces CONTENT_OBJECT_TAGS_CHANGED with CONTENT_OBJECT_ASSOCI…
pomegranited d517d80
refactor: store collections outside of tags index
pomegranited 9a94316
Merge branch 'yusuf-musleh/collections-crud-rest-api' into jill/colle…
pomegranited 66b2aa8
fix: missing import
pomegranited 4bc7c22
Merge branch 'yusuf-musleh/collections-crud-rest-api' into jill/colle…
pomegranited bd44874
test: fixed failing test after refactor
pomegranited File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still not thrilled with storing collections together with tags. If we store it in the same property, I think we couldn't use the
reason
field to do partial updates inside this doc property (although we can do partial updates at the doc level).Despite being synchronous, I will not object because these operations are cheap. I'm just failing to see any advantage in this approach. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rpenido Noted..
@bradenmacdonald What do you think? Should we be storing
collections
in thetags
index structure, or should it be its own field?I'm pretty sure it's asynchronous outside of the devstack -- events are handled by the "worker" processes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would make it it's own field, unless that's a difficult change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do, it's not difficult at all.