Skip to content

CAMEL-23528: document camel-neo4j property name validation in the 4.18 upgrade guide #23295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
oscerd wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −0
Open

CAMEL-23528: document camel-neo4j property name validation in the 4.18 upgrade guide #23295

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,6 +200,16 @@ work without changes. Routes that set the header by its literal string value
(for example `setHeader("SEARCH_QUERY", ...)`) must be updated to use the
new value (`setHeader("CamelElasticsearchSearchQuery", ...)`).

=== camel-neo4j

When using the `RETRIEVE_NODES` or `DELETE_NODE` operations with the `CamelNeo4jMatchProperties`
header, the property names provided in the JSON match map are now validated before the `MATCH` /
`DELETE` `WHERE` clause is built. Property names must be valid identifiers matching
`[A-Za-z_][A-Za-z0-9_]*`. A request whose match map contains a property name that does not match
this pattern now fails fast with an `IllegalArgumentException` (wrapped in a
`Neo4jOperationException`) instead of producing a malformed query. Property values continue to be
passed as bound query parameters and are unaffected.

== Upgrading from 4.18.0 to 4.18.1

=== camel-bom
Expand Down