-
Notifications
You must be signed in to change notification settings - Fork 617
Feature request: ReactiveCypherdslConditionExecutor #2575
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.
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
Labels
type: new-feature
A completely new feature
Comments
I would happily accept a PR from your branch and polish it up. That's great stuff. |
I'm happy to provide a PR, just one question, should I provide one for main, or 6.3.x? |
So, it's a new feature and technically it shouldn't appear in a patch, so the answer is main. Also, you can use Java 17 there. However, as it will be sometime until the next major release, I'm happy to backport it to 6.3. |
nk-coding
added a commit
to nk-coding/spring-data-neo4j
that referenced
this issue
Aug 2, 2022
Provides a reactive equivalent to CypherdslConditionExecutor. See spring-projects#2575
4 tasks
michael-simons
pushed a commit
that referenced
this issue
Aug 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
in my opinion it would be helpful to have a reactive equivalent to the
CypherdslConditionExecutor
. I sadly was not able to find one, and to my understanding, I cannot useCypherdslConditionExecutor
in a reactive context.If there is already a way to query for nodes by a Cypher DSL condition (without relying on internal functionality) with reactive repositories, I would be glad to hear about it.
To my understanding, a ReactiveCypherdslConditionExecutor could be implemented by basically taking the non-reactive equivalents, and replacing the return types and the injected
Neo4jOperations
with their reactive equivalents - at least for my test implementation, this worked well.The text was updated successfully, but these errors were encountered: