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
Trying to open a transaction to a database that does not exist is a recoverable error. Therefore, we should catch and recover from it instead of exiting.
The text was updated successfully, but these errors were encountered:
…at doesn't exist (#104)
## What is the goal of this PR?
We have fixed an issue that caused console to exit when trying to open transaction to a database that doesn't exist.
## What are the changes implemented in this PR?
- Bump client-java to the version which no longer throws the incorrect exception, causing console to exit improperly
- Fix#98
## What is the goal of this PR?
We introduce modified `infer`, and new `batch_size`, and `explain` options for queries:
The default (undefined setting of the above options) value means that the server will automatically choose the default value for `infer`, `explain`, and `batch_size`. For reference, the server will default to `infer = true`, `explain = true`, and `batch_size = 50`.
** use `explain:true` if you want to retrieve explanations from your query ** This was introduced to ensure correct Explanations, without consuming too much Transaction memory when not required.
## What are the changes implemented in this PR?
* Introduce `explain` query option
* Include `batchSize` query option into the query options, instead of iteration options
* Throw exceptions if the types of parameters are passed in are incorrect.
* Tests for `explain` and `infer` flag
Trying to open a transaction to a database that does not exist is a recoverable error. Therefore, we should catch and recover from it instead of exiting.
The text was updated successfully, but these errors were encountered: