This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
fix(GraphQL): Ensure that a list of scalars remain sorted #76
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.
If we have a list of strings, currently Outserv stores them sorted by their fingerprints. Instead, as per the GraphQL spec, we need to maintain their order. This PR achieves that outcome with a new ListType. The list values are binary encoded and stored together as one value. This ensures correct ordering. This means a posting list can only have a maximum of one posting for values (UIDs are stored in bitmaps anyway).
This PR also removes the
type
func from DQL. Instead, now we usehas
func for resolving queries with no filters. More work is needed to clean updgraph.type
predicate.chunker interface is now replaced with jsonChunker. That's the only chunker we have after RDF chunker was removed.
This change is![Reviewable](https://camo.githubusercontent.com/23b05f5fb48215c989e92cc44cf6512512d083132bd3daf689867c8d9d386888/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)