8000 3.7 getResponsibleShard for disjoint edges by mchacki · Pull Request #14651 · arangodb/arangodb · GitHub
[go: up one dir, main page]
Skip to content

3.7 getResponsibleShard for disjoint edges #14651

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 2 commits into from
Aug 23, 2021
Merged

3.7 getResponsibleShard for disjoint edges #14651

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21cb9e3
Added ChangeLogEntry (#14647)
mchacki Aug 17, 2021
3d436f0
Merge branch '3.7' into bug-fix-3.7/getResponsibleShard-disjoint
KVS85 Aug 23, 2021
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
Next Next commit
Added ChangeLogEntry (#14647)
  • Loading branch information
@mchacki
mchacki committed Aug 17, 2021
commit 21cb9e36a2a8b80f901e1846adfe283b64a5988b
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 @@
v3.7.14 (XXXX-XX-XX)
--------------------

* 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 various problems in GEO_INTERSECTS: wrong results, not implemented cases
and numerically unstable behaviour. In particular, the case of the
intersection of two polygons in which one is an S2LngLatRect is fixed
Expand Down
0