fixed index cache feature #137
Merged
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
Current coverage is
|
|
+1! |
| !this.indexes._canCreate && | ||
| _.contains(['import', 'create', 'createCollection', 'putMapping', 'createOrUpdate'], requestObject.action) && | ||
| !doesIndexExist(requestObject, indexes)) { | ||
| _.contains(['import', 'create', 'createCollection', 'putMapping', 'createOrUpdate'], requestObject.action)) { |
There was a problem hiding this comment.
Indeed. Good news is: merging this will be easy as in this PR, I only moved the last test to the first position, to make it clearer that it handles the case when an index or a collection doesn't exist.
|
+1 |
Conflicts: test/api/controllers/writeController.test.js
Conflicts: lib/api/controllers/adminController.js lib/api/controllers/writeController.js lib/api/core/models/security/role.js test/api/controllers/adminController.test.js test/services/implementations/elasticsearch.test.js
|
+1 |
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.
Bugfix: the index cache was handled by the elasticsearch service, called both by the server instance and its workers. Problem is: workers didn't have access to the index cache, thus leading to non-catched errors.
indexCachecore componentkuzzle.indexeswithkuzzle.indexCache, using the new core componentwriteandadmincontrollerscleanDbandprepareDbnow use and maintain the index cachecleanDbandprepareDbare now independant to Kuzzle to avoid adding unnecessary objects to the main context