Skip to content

Docs: an index on a property with no declared type keys an array by its identity on 26.11.1 - #408

Merged
tae898 merged 1 commit into
mainfrom
docs/407-undeclared-index-arrays
Nov 15, 2026
Merged

tae898 merged 1 commit into
mainfrom
docs/407-undeclared-index-arrays

Conversation

@tae898

@tae898 tae898 commented Nov 15, 2026

Copy link
Copy Markdown
Collaborator

What does this PR do?

Adds a short section, "An index on a property with no declared type", to the Values and records page. On ArcadeDB 26.11.1 an index on a property that no CREATE PROPERTY declares (for example CREATE INDEX FOR (n:N) ON (n.k) in openCypher) keys an array by its identity, so a seek by a bytes value or by a float32 NumPy array finds no record. I ran one script on arcadedb and on arcadedb-jvm 26.11.1.post3: both gave the same answers, and a list and an int64 NumPy array are found. The section links ArcadeData/arcadedb#11615, which fixes it, says the fix is in the engine's main and in no release yet (26.11.1 does not contain it), and says nothing on the page was run against an engine that has it. It also repeats what that pull request reports about REBUILD INDEX for an existing index that holds lists of floating-point numbers.

I changed nothing for ArcadeData/arcadedb#11697 (SEARCH_INDEX and SEARCH_FIELDS over a small RID list): the matches and scores are the same as before, no page describes a RID-list target, and I did not measure its speed claim, so there is nothing true to add.

Related issues

Closes #407

Docs

docs/modules/ROOT/pages/how-to/values-and-records.adoc, the new section and the // Sources: comment (the page's tests pin every other statement; this one is a measurement, and the comment now says so). README.md does not describe this.

Checklist

  • A regression test fails on the old code and passes on the new: not applicable. A strict xfail would fail the CI runs that use the latest engine image as soon as it carries the fix, and I cannot run the Python side against the fixed engine yet.
  • The test suite that the change can affect passes: the Antora build of docs/antora-playbook.yml finishes with no warning, and the new section, the link to #11615 and the link to REBUILD INDEX render.
  • uvx pre-commit run --files <changed files> passes

🤖 Generated with Claude Code

…ts identity on 26.11.1

The Values and records page gets a short section on what the engine fix
ArcadeData/arcadedb#11615 means for Python users. On 26.11.1 a seek by a bytes value
or a float32 NumPy array on such an index finds no record, on both packages (one
script on the 26.11.1.post3 wheels). The fix is in the engine's main branch and in
no release yet, and the section says nothing was run against it. A list and an
int64 NumPy array are not affected.

ArcadeData/arcadedb#11697 changes no answer and no page describes a RID-list
target, so no page changes for it.

Refs #407

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
@tae898 tae898 added documentation Improvements or additions to documentation native The arcadedb package (native library build) jvm The arcadedb-jvm package (JPype build) labels Nov 15, 2026
@tae898 tae898 self-assigned this Nov 15, 2026
@tae898
tae898 merged commit 4c95ed1 into main Nov 15, 2026
6 checks passed
@tae898
tae898 deleted the docs/407-undeclared-index-arrays branch November 15, 2026 16:00
@github-actions github-actions Bot added this to the 26.12.1 milestone Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation jvm The arcadedb-jvm package (JPype build) native The arcadedb package (native library build)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: what the engine fixes #11615 and #11697 change for Python users

1 participant