8000 Bug-Fix: getResponsibleShard on Disjoint-Edge-Collections by mchacki · Pull Request #14647 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

Bug-Fix: getResponsibleShard on Disjoint-Edge-Collections #14647

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Aug 17, 2021
Merged

Bug-Fix: getResponsibleShard on Disjoint-Edge-Collections #14647

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,12 @@
devel
-----

* Fixed: getResponsibleShard call on disjoint Smart Graphs
if you asked for the responsible shard on a disjoint edge collection
where the _from and _to differ (invalid), the server would respond with
"DATASOURCE_NOT_FOUND". This is now fixed to "BAD_PARAMETER"
to emphasize that the collection is fine but the input is invalid.

* Fixed: _api/transaction/begin called on edge collections of disjoint
SmartGraphs falsely returned CollectionNotFound errors.

Expand Down
0