-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Incidental functionality improvements from Next Gen Modulestore work #269
Changes from all commits
26aa085
97c2e9e
e9bd1c5
115b214
c7046df
2ef4d82
1c5706f
3188bb0
274f1d1
db59aca
7892fd7
ddfbe59
a2524c5
2fc7d33
ef9c299
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,7 +27,7 @@ | |
|
||
MODULESTORE = { | ||
'default': { | ||
'ENGINE': 'xmodule.modulestore.mongo.DraftMongoModuleStore', | ||
'ENGINE': 'xmodule.modulestore.draft.DraftModuleStore', | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Am I missing something. I don't see a similar edit to aws.py - the production configuration. Also, I presume these configuration changes can go out ahead of a code deploy. If we're going to avoid downtime, we need to test/verify that deploying this config change against the previous codebase. I don't know if Edge sandbox is still functional, but I'd suggest just hopping on the machine and manually tweeking the auth.json file and making sure it still works. |
||
'OPTIONS': modulestore_options | ||
}, | ||
'direct': { | ||
|
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.
You're changing the return type here. Have all callers been updated as well? Sorry - I don't have spare time to check all the call sites.
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.
Also, assuming this change remains, the documentation needs to be updated.
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 updated it. I find it very confusing that we use 'location' to mean almost any non-interchangable encoding (convertible but not usable in the same contexts). Location is the most generally useful; so, I wanted to try to reduce the usages of any other encoding (e.g., string 'i4x://org/course/category/name', array ['i4x','course',...], and dict {'org'...}) by moving the coercion closer to the creation of the off-repr.