-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix: exclude messages field from Datastore index to avoid 1500 bytes limit #37
fix: exclude messages field from Datastore index to avoid 1500 bytes limit #37
Conversation
/gcbrun |
Hi @averikitsch, |
/gcbrun |
@JU-2094 is currently out of office and will review next week. Thanks! |
/gcbrun |
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.
Awesome, lgtm!
@cymarechal-devoteam can you resolve the merge conflicts? |
…astore-unindexed-fields
That should be it! Please let me know if there is anything else. |
/gcbrun |
Hi,
While playing around with DatastoreChatMessageHistory, I noticed that I quickly ran into Datastore's 1,500 bytes limit for indexed string property's UTF-8 encoding (source: https://cloud.google.com/datastore/docs/concepts/limits).
This PR creates a simple test case to demonstrate the issue and solves it by using Datastore's
exclude_from_indexes
parameter.Feedback appreciated!