-
Notifications
You must be signed in to change notification settings - Fork 156
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
Feature/540 forward lineage #1091
Conversation
…ct overivew, the rest the same as LineageOverview
… did not publish the final data node (this was probably ok for lineage)
It's up to you. Of course the code quality is important, and I don't think any AQL or FOXX code has any special additions or exceptions related to the common code quality standards. Just use a usual common sense. When you're done mark it as "ready for review" and we'll take a look. |
What is a purpose of the two empty files? |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
After some digging, I have discovered that it was due to file mode being inadvertently changed - probably when sharing between Win-Linux/etc while having git's So I have set |
Closed in favor of #1100 |
Heavily inspired by (backward) Lineage. After the naive implementation, common parts of the foxx service have been moved to
commons.js
for reuse.(Also, there is a similar PR #1092 - let's inspire each other, @vishalag001)
API
Spline service level API
GET /spline/events/$eventId/lineage-overview/$maxDepth
ArangoDB foxx-service level API
GET /events/:eventKey/impact-overview/:maxDepth
persistence
)Test-run
I have hacked the spline-ui to load
.../impact-overview
url instead of.../lineage-overview
to test the graph data in UI to be shown:Implements backed of #540.