Skip to content

Conversation

@Lojjs
Copy link
Contributor

@Lojjs Lojjs commented Jan 14, 2026

No description provided.

@Lojjs Lojjs added the 2026.01 label Jan 14, 2026
Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @Lojjs. I pushed some editorial updates, but I also left some suggestions that I am not sure are correct. Please take a look.

Copy link
Contributor

@dogofbrian dogofbrian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice. Just some typos and a couple of suggestions.

@Lojjs Lojjs force-pushed the document-metadata-filtering-error-codes branch from bdde4e8 to 7522df0 Compare January 19, 2026 08:27
= 22ND3

== Status description
error: data exception - wrong property for vector search filtering. The property `{ <<propKey>> }` is not an additional property of the vector index `{ <<idx>> }`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may not be clear what an "additional" property is, depending on how we called this in the original docs (I have not seen that).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I asked @Hunterness about this in another comment thread. She is writing those docs today so we will update this if she ends up calling them something else, additional property is what the concept is called in her CIP

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have just added a PR for my bits, currently using 'additional property' but we'll see what reviewers say

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question for both of you @Hunterness and @arnefischereit: I noticed we ended up using "additional property for filtering" consistently in the docs. Do you think adding the "for filtering" to the error text as well would be an improvement?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know I've called them both (usually dropping the "for filtering" when I want a short hand/already said that further up the page)

error: data exception - wrong property for vector search filtering. The property { <<propKey>> } is not an additional property for filtering of the vector index { <<idx>> }.

that sounds a bit repetitive and hard to read though

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I think I do agree with @Hunterness that this sound rather redundant, I found a lot of the error messages structured {subCondition}. {message} to be repetitive.

In this case, I think that maybe that should be the case and we should make it even more so:

The property ... is not an additional property on ... for vector search filtering.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@arnefischereit @Hunterness Coming back to this PR now when the general Cypher SEARCH docs are finished.

In the last suggestion, where you thinking it should say

error: data exception - wrong property for vector search filtering. The property is not an additional property on for vector search filtering.

I think that is sounds a bit weird with a property on an index

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or is this what Arne is after? (not having the on and filling in the ... with the original bits of the message)

error: data exception - wrong property for vector search filtering. The property { <<propKey>> } is not an additional property of the vector index { <<idx>> } for vector search filtering.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that sound better, I will go with that unless Arne protest

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did the above but changed "vector search filtering" to "vector search with filters" which was what we ended up deciding on with David Pond.

@renetapopova renetapopova self-assigned this Jan 26, 2026
@renetapopova renetapopova force-pushed the document-metadata-filtering-error-codes branch from d2142d2 to a1be14e Compare January 26, 2026 12:18
@renetapopova renetapopova force-pushed the document-metadata-filtering-error-codes branch from 0a3695f to 56ac423 Compare January 27, 2026 10:24
@renetapopova renetapopova force-pushed the document-metadata-filtering-error-codes branch from c2e90d5 to 4920db4 Compare January 28, 2026 12:46
Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments from me.

@renetapopova renetapopova force-pushed the document-metadata-filtering-error-codes branch from 4920db4 to 62c3eca Compare February 4, 2026 10:39
@renetapopova
Copy link
Collaborator

@Lojjs, is this ready for merging? Shall I take a final look?

Copy link
Collaborator

@renetapopova renetapopova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a couple of questions.

@renetapopova renetapopova force-pushed the document-metadata-filtering-error-codes branch from efe4e6c to 92e26d3 Compare February 6, 2026 09:11
@neo4j-docops-agent
Copy link
Collaborator

neo4j-docops-agent commented Feb 6, 2026

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@renetapopova renetapopova merged commit cd6ab77 into neo4j:dev Feb 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants