Enum Evidence 

pub enum Evidence {
    Shared {
        field: String,
        shared: Vec<Value>,
    },
    Value {
        field: String,
        value: Value,
    },
    Geo {
        field: String,
        a: Value,
        b: Value,
        km: f64,
    },
    Pair {
        field: String,
        a: Option<Value>,
        b: Option<Value>,
        similarity: Option<f64>,
    },
    Parts {
        parts: Vec<Evidence>,
    },
}

What the two nodes actually had in common, per predicate kind.

Naming the rule and the threshold was never the answer to “why are these two related” — the shared values are. Without them an assistant fetches both nodes’ raw property lists and reads them out, which names every value either node holds rather than the ones they share.

Variants

Shared

overlap — the intersection of the two lists, sorted.

Fields

field: String

shared: Vec<Value>

Value

field_equal / key_match — the one value both carry.

Fields

field: String

value: Value

Geo

geo_radius — both points and the distance between them.

Fields

field: String

a: Value

b: Value

km: f64

Pair

numeric_within / vector_similar — the two sides. For vector_similar the vectors themselves are useless to read, so a and b are omitted and only the score stands.

Fields

field: String

a: Option<Value>

b: Option<Value>

similarity: Option<f64>

Parts

all / any — one entry per branch that contributed.

Fields

parts: Vec<Evidence>

Trait Implementations

impl Serialize for Evidence

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.