-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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(mutation): validate mutation before applying it #8623
Conversation
89a6bc2
to
f03394b
Compare
f03394b
to
7c1883e
Compare
7c1883e
to
5885e5d
Compare
e5fb320
to
bb0be52
Compare
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.
We need to look at what happens when indexing fails, as we can't just skip the transcation anymore.
@harshil-goel indexing request comes as part of the Alter request and it is not a transaction. Today, it is acceptable that the indexing could fail. We don't have a good way of letting the user know yet and we should build one. The nice thing here is that the schema remains consistent either way. |
This change ensures that the value in the mutation is not too big. The challenge here is that the keys in badger have a limitation on their size (< 2<<16). We need to ensure that no key, either primary or secondary index, is bigger than that. Fixes dgraph-io/projects-internal#73
397bac0
bb0be52
to
397bac0
Compare
This change ensures that the value in the mutation is not too big. The challenge here is that the keys in badger have a limitation on their size (< 2<<16). We need to ensure that no key, either primary or secondary index key is bigger than that. Fixes https://github.com/dgraph-io/projects/issues/73
This change ensures that the value in the mutation is not too big. The challenge here is that the keys in badger have a limitation on their size (< 2<<16). We need to ensure that no key, either primary or secondary index key is bigger than that. Fixes https://github.com/dgraph-io/projects/issues/73
This change ensures that the value in the mutation is not too big. The challenge here is that the keys in badger have a limitation on their size (< 2<<16). We need to ensure that no key, either primary or secondary index key is bigger than that.
Fixes https://github.com/dgraph-io/projects/issues/73