#1268: Error when store a big data to cache #1272
Closed
Conversation
This file contains hidden or 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
…t because when the schema reach out certain size it couse unserialization issues breaking the schema caching
Contributor
|
Should be fixed by #1364, so I think we don't need this. Please test! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ISSUE: #1268 Error when store a big data to cache.
This PR Fixes the schema cache issue when your schema reach out certain size.
DocumentNode) becomes unmanageable by the unserialize function, leading to not loading the right cached schema data .How to do a basic a test:
drush cr)admin/config/graphql/servers/manage/[SERVER-ID]/explorer