Skip to content
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

Introduce new reactive session with updated API #1208

Merged
merged 1 commit into from
Apr 20, 2022

Conversation

injectives
Copy link
Contributor

@injectives injectives commented Apr 12, 2022

This update introduces a new reactive session called ReactiveSession and deprecates the existing RxSession.

The new session can be created via reactiveSession methods on Driver.

The ReactiveSession brings reactive API in line with synchronous and asynchronous when it comes to getting an instance on result handle (ReactiveResult). Specifically, run methods return a Publisher<ReactiveResult> that will only emit ReactiveResult instance on successful Bolt message (RUN) exchange and will emit an error on failure. Furthermore, this change allowed simplification of ReactiveResult.keys() method that simply returns a list of strings now.

This update also adds a new reactive backend implementation for Testkit and renames existing implementation to reactive-legacy.

Copy link
Contributor

@michael-simons michael-simons left a comment

Choose a reason for hiding this comment

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

I find everything that we spoke about… Looks great.

@injectives injectives force-pushed the feature/reative-api branch 4 times, most recently from 0c9fe2a to da6fdeb Compare April 19, 2022 08:40
This update introduces a new reactive session called `ReactiveSession` and deprecates the existing `RxSession`.

The new session can be created via `reactiveSession` methods on `Driver`.

The `ReactiveSession` brings reactive API in line with synchronous and asynchronous when it comes to getting an instance on result handle (`ReactiveResult`). Specifically, `run` methods return a `Publisher<ReactiveResult>` that will only emit `ReactiveResult` instance on successful Bolt message (`RUN`) exchange and will emit an error on failure. Furthermore, this change allowed simplification of `ReactiveResult.keys()` method that simply returns a list of strings now.

This update also adds a new reactive backend implementation for Testkit and renames existing implementation to `reactive-legacy`.
@injectives injectives merged commit 8b2d872 into neo4j:5.0 Apr 20, 2022
@injectives injectives deleted the feature/reative-api branch April 20, 2022 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants