ArcadeDB uses JVector internally, but the JVector addHierarchy (hierarchical graph on/off) flag is not exposed in ArcadeDB’s vector index configuration.

This flag materially affects latency and scalability and is useful for:

• controlled benchmarking,
• comparing hierarchical vs non-hierarchical graphs,
• reproducing JVector baseline results.

JVector already supports this internally; exposing it would be a non-breaking config option (default can remain true).

Example (illustrative):

PARAMETERS {
  "addHierarchy": true
}

This would significantly improve benchmarking and tuning without changing defaults.