Feature (Light Edges / 6) - feat(flags): add --storage-light-edge flag (default false, inert)#4228
Merged
Merged
Conversation
f67b220 to
c868cff
Compare
6472f56 to
4f86951
Compare
c868cff to
5ee790f
Compare
4f86951 to
2b425cf
Compare
5ee790f to
6aed92d
Compare
2b425cf to
36f6c51
Compare
6aed92d to
4a3ba31
Compare
as51340
approved these changes
Jun 8, 2026
36f6c51 to
8d0c83a
Compare
4a3ba31 to
2ef02fa
Compare
2ef02fa to
c882b1c
Compare
64b1630 to
dd7eadc
Compare
Introduce the opt-in storage_light_edge gflag, its SalientConfig::Items field with back-compat json (de)serialization, and the memgraph.cpp wiring (including the properties_on_edges implication). Default false; no storage code reads the field yet (first reader lands in the light create/find PR), so this is a wholly inert plumbing change that is safe to land mid-stack. A tiny storage_v2_config unit target proves default false, json round-trip, and the missing-key back-compat path.
c882b1c to
d0af0ad
Compare
|
14 tasks
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
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.



Introduce the opt-in storage_light_edge gflag, its SalientConfig::Items field with back-compat json (de)serialization, and the memgraph.cpp wiring (including the properties_on_edges implication). Default false; no storage code reads the field yet (first reader lands in the light create/find PR), so this is a wholly inert plumbing change that is safe to land mid-stack. A tiny storage_v2_config unit target proves default false, json round-trip, and the missing-key back-compat path.