During Fluent find operations the default renderer is used to render parts of the cypher query, thus ignoring any and all configuration #2927
Assignees
Labels
type: bug
A general bug
Comments
spring-projects-issues
added
the
status: waiting-for-triage
michael-simons
added
type: bug
|
Great catch, @THE-ORONCO A fix is on the way. |
michael-simons
added a commit
that referenced
this issue
Jul 19, 2024
… in various Cypher-DSL based query extension. Fixes #2927. # Conflicts: # src/main/java/org/springframework/data/neo4j/core/ReactiveNeo4jTemplate.java
michael-simons
added a commit
that referenced
this issue
Jul 19, 2024
… in various Cypher-DSL based query extension. Fixes #2927.
michael-simons
added a commit
that referenced
this issue
Jul 19, 2024
… in various Cypher-DSL based query extension. Fixes #2927.
michael-simons
added a commit
that referenced
this issue
Jul 19, 2024
… in various Cypher-DSL based query extension. Fixes #2927.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the
org.springframework.data.neo4j.core.FluentFindOperation.FindWithQuery#matching(org.neo4j.cypherdsl.core.Statement, java.util.Map)method (for example when using the Neo4jTemplate) the given statement is rendered using the default renderer. This means any configuration provided via aConfiguration-Bean is lost / ignored for this particular statement.I found this bug because the generated Cypher statements were always rendered with
idinstead ofelementIdeven though I explicitly defined them via the Cypher-DSL and also set the Neo4J-Version to v5 in theConfiguration-Bean.A possible solution could be to not render the match-statement in place and instead delay the rendering until the configuration is in scope to get the actual renderer.
A minimal example showing the issue is provided here.
The text was updated successfully, but these errors were encountered: