[
https://issues.jboss.org/browse/TEIID-5495?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5495:
-------------------------------------
agree. I think we can do two levels of support.
1) Basic, supply json and get json back. Current WS translator should suffice that. Need
to show some examples.
2) Going custom translator route, we will get a JSON document that has One-2-Many based
relationships (mostly). Where this becomes challenging is as you mention input parameter
mapping. As these parameters could be just criteria on field or implicit paging techniques
or something completely random. The last one is troublesome, but if we take an approach as
in the procedure to relational where parameters are added to response (entity) then these
can be treated similarly to the criteria.
Add support for graphql sources
-------------------------------
Key: TEIID-5495
URL:
https://issues.jboss.org/browse/TEIID-5495
Project: Teiid
Issue Type: Feature Request
Components: Connector API
Reporter: Steven Hawkins
Assignee: Van Halbert
Priority: Major
Fix For: 12.x
We should create translator support for graphql, which will also help us evaluate
supporting graphql as a front end as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)