-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add support for Stream Transactions #322
Comments
The way I see it, we should be able to update |
For Arango 3.4, filter and exclude the StreamTransaction tests using Xunit Trait. fix ArangoDB-Community#322
For Arango 3.4, filter and exclude the StreamTransaction tests using Xunit Trait. fix ArangoDB-Community#322
Refactored the TransactionApiClient and its test class. Created a new class StreamTransactionResponse. fix ArangoDB-Community#322
Refactored TransactionApiClientTest and StreamTransactionBody class. fix ArangoDB-Community#322
As discussed separately with @DiscJockeyDJ , this work is split in a series of pull requests. The first one added the methods for the stream transaction API endpoints. A subsequent pull request will be opened to allow speciying the transaction ID in other API operations. |
…to the request headers. fix ArangoDB-Community#322
Added a new class HeaderProperties with TransactionId as the property. fix ArangoDB-Community#322
Refactored the method to get HeaderCollection. Added test to verify header properties. fix ArangoDB-Community#322
#325) * Implement changes to Cursor API to include the stream transaction id to the request headers. fix #322 * Removed stream transaction Ids for DeleteCursor and PutCursor APIs. Added a new class HeaderProperties with TransactionId as the property. fix #322 * Reinstated the missed out ConfigureAwait for the end points. fix #322 * Renamed the HeaderProperties to CursorHeaderProperties. Refactored the method to get HeaderCollection. Added test to verify header properties. fix #322
Some methods of the Cursor API were updated to allow specifying a transaction ID. Reopening the issue to address remaining APIs in subsequent pull requests. |
…d to the request headers. fix ArangoDB-Community#322
…d to the request headers. fix ArangoDB-Community#322
Moved the TransactionId header string to a constant class. fix ArangoDB-Community#322
…o skip 3.4 ArangoDB test run. fix ArangoDB-Community#322
We currently have support for js-transactions only, in
TransactionApiClient
. The transactions API of ArangoDB also supports streaming transactions, which are a different kind of transactions from js-transactions.HTTP Interface for Transactions
https://www.arangodb.com/docs/stable/http/transaction.html
HTTP Interface for Stream Transactions
https://www.arangodb.com/docs/stable/http/transaction-stream-transaction.html
The text was updated successfully, but these errors were encountered: