Ticket #514 (closed Feature Request: wontfix)
new plugin: to support simple graph traversals via REST-Interface
| Reported by: | Malte | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | |
| Component: | 3rd Party Plugins | Version: | |
| Keywords: | Cc: | ||
| Complexity: | 8 | Area: | Application Framework / API |
| Module: |
Description
At the moment, just using the core-webservice functionality, is it a must to perform 2 GET requests for a simple graph-traversal (via 1 intermediate topic using the REST-interface)?
Given that I know the type of the intermediate (Composite-Topic) and the type of the desired ChildTopic?, how can I construct a simple query getting me (from a topic-id) over 1 intermediate topic directly to my desired ChildTopic? with 1 GET-Request (while the response delivers just that ChildTopic? (and not the full surrounding composite/other ChildTopics? with it)?
I would be happy to get to know how this is (currently) intended to be done. Thanks!
Change History
comment:2 Changed 11 years ago by Malte
Ah, yes, I remember that we talkd about this issue already some time ago (offline). I now see the necessity to build a "cherry-picker" enabling (application developers) to construct a query from a given topicID, over:
- the first (= [0]) intermediate related (assoctype) topic (topictype),
- answering with just 1 ChildTopic?-SimpleValue? (of a specific topictype)
while assuming that there is always just one related topic (via edge-type and topictype) as direct neighbor to the topic where my requests originate from (topicId).
This way I could reduce the amount of initial requests to build up my viewmodel from 45 to 30.
But as I see it, in my case now, the (originating) issue is even another one, see #515, cause this would allow me to reduce my initial (AJAX) requests to just 15.
comment:3 Changed 11 years ago by Malte
- Component changed from DeepaMehta Standard Distribution to 3rd Party Plugins
- Module deepamehta-core deleted
- Summary changed from support simple graph traversals via REST-Interface to new plugin: to support simple graph traversals via REST-Interface
- Complexity changed from 3 to 8
- Version 4.1.2 deleted
- Milestone set to Release 4.2
- Type changed from Defect to Feature Request
Ok, so this issue transforms into a specification of a new plugin. Changed title and status accordingly from: "support simple graph traversals via REST-Interface" with the deepamehta-core module to "new plugin: to support simple graph traversals via REST-Interface".
Then let's have a look at other powerful query languages and start to define a few functions to implement in v1.0. Happy for any suggestions.
See #513. Does it help here?
Full fledged graph traversal (like e.g. Neo4j's Cypher language) is not supposed to be part of the DM core. It could be realized on-top by 3rd-party plugins.