Skip to content

bindings docs: known issue for upstream #9018 and #9019, GraphBatch edges with declared properties #104

Closed

Description

@tae898

GraphBatch edges written with properties skip the engine's conversion and constraint checks, and through the Python bindings both GraphBatch.new_edge(..., **properties) and GraphBatch.new_edges(..., properties=[...]) reach that path. On a 26.10.1 snapshot with an edge type that declares weight INTEGER and small SHORT, weight=None is stored as -1, and small=40000 is stored as -25536, where Vertex.new_edge(...) stores null and refuses 40000.

ArcadeDB filed these as ArcadeData#9018 (a null in a declared edge property) and ArcadeData#9019 (no conversion or constraint checks on GraphBatch edges). The Java reproductions show both on 26.10.1 main, on the benchmark's pin 417314c18, and on 26.9.1.

This issue adds a known-issues entry with a workaround checked through the bindings, a caution on the GraphBatch API page, and tests: the workaround must keep working, and an expected-failure test marks the bug so a fixed engine shows up as an unexpected pass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions