You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
72
71
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
73
72
* <p>
74
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
73
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
75
74
* <p>
76
75
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
77
76
* different thread.
77
+
* <p>
78
+
* The driver uses the provided {@link ReactiveTransactionCallback} to get a publisher and emits its
79
+
* signals via the resulting publisher. If the supplied publisher emits a
80
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
81
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
82
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
83
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
84
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
78
85
*
79
86
* @param callback the callback representing the unit of work.
80
87
* @param <T> the return type of the given unit of work.
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
92
99
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
93
100
* <p>
94
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
101
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
95
102
* <p>
96
103
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
97
104
* different thread.
105
+
* <p>
106
+
* The driver uses the provided {@link ReactiveTransactionCallback} to get a publisher and emits its
107
+
* signals via the resulting publisher. If the supplied publisher emits a
108
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
109
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
110
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
111
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
112
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
98
113
*
99
114
* @param callback the callback representing the unit of work.
100
115
* @param config configuration for all transactions started to execute the unit of work.
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
112
127
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
113
128
* <p>
114
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
129
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
115
130
* <p>
116
131
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
117
132
* different thread.
133
+
* <p>
134
+
* The driver uses the provided {@link ReactiveTransactionCallback} to get a publisher and emits its
135
+
* signals via the resulting publisher. If the supplied publisher emits a
136
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
137
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
138
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
139
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
140
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
118
141
*
119
142
* @param callback the callback representing the unit of work.
120
143
* @param <T> the return type of the given unit of work.
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
132
155
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
133
156
* <p>
134
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
157
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
135
158
* <p>
136
159
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
137
160
* different thread.
161
+
* <p>
162
+
* The driver uses the provided {@link ReactiveTransactionCallback} to get a publisher and emits its
163
+
* signals via the resulting publisher. If the supplied publisher emits a
164
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
165
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
166
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
167
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
168
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
138
169
*
139
170
* @param callback the callback representing the unit of work.
140
171
* @param config configuration for all transactions started to execute the unit of work.
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
72
71
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
73
72
* <p>
74
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
73
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
75
74
* <p>
76
75
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
77
76
* different thread.
77
+
* <p>
78
+
* The driver uses the provided {@link org.neo4j.driver.reactive.ReactiveTransactionCallback} to get a publisher and emits its
79
+
* signals via the resulting publisher. If the supplied publisher emits a
80
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
81
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
82
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
83
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
84
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
78
85
*
79
86
* @param callback the callback representing the unit of work.
80
87
* @param <T> the return type of the given unit of work.
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
92
99
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
93
100
* <p>
94
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
101
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
95
102
* <p>
96
103
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
97
104
* different thread.
105
+
* <p>
106
+
* The driver uses the provided {@link org.neo4j.driver.reactive.ReactiveTransactionCallback} to get a publisher and emits its
107
+
* signals via the resulting publisher. If the supplied publisher emits a
108
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
109
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
110
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
111
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
112
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
98
113
*
99
114
* @param callback the callback representing the unit of work.
100
115
* @param config configuration for all transactions started to execute the unit of work.
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
112
127
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
113
128
* <p>
114
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
129
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
115
130
* <p>
116
131
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
117
132
* different thread.
133
+
* <p>
134
+
* The driver uses the provided {@link org.neo4j.driver.reactive.ReactiveTransactionCallback} to get a publisher and emits its
135
+
* signals via the resulting publisher. If the supplied publisher emits a
136
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
137
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
138
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
139
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
140
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
118
141
*
119
142
* @param callback the callback representing the unit of work.
120
143
* @param <T> the return type of the given unit of work.
* The driver will attempt committing the transaction when the provided unit of work completes successfully. Any exception emitted by the unit of work will
132
155
* result in a rollback attempt and abortion of execution unless exception is considered to be valid for retry attempt by the driver.
133
156
* <p>
134
-
* The provided unit of work should not return {@link Result} object as it won't be valid outside the scope of the transaction.
157
+
* The provided unit of work should not return {@link ReactiveResult} object as it won't be valid outside the scope of the transaction.
135
158
* <p>
136
159
* It is prohibited to block the thread completing the returned {@link CompletionStage}. Please avoid blocking operations or hand processing over to a
137
160
* different thread.
161
+
* <p>
162
+
* The driver uses the provided {@link org.neo4j.driver.reactive.ReactiveTransactionCallback} to get a publisher and emits its
163
+
* signals via the resulting publisher. If the supplied publisher emits a
164
+
* {@link org.neo4j.driver.exceptions.RetryableException} and the driver is in a position to retry, it calls the
165
+
* provided callback again to get a new publisher and attempts to stream its signals. In case of retries, the
166
+
* resulting publisher contains the successfully emitted values from all retry attempts. For instance, if a
167
+
* retryable exception occurs after streaming values [v1, v2, v3] and a successful retry emits values [v1, v2, v3,
168
+
* v4] then the resulting publisher emits the following values: [v1, v2, v3, v1, v2, v3, v4].
138
169
*
139
170
* @param callback the callback representing the unit of work.
140
171
* @param config configuration for all transactions started to execute the unit of work.
0 commit comments