Daewon Jeong commented on S2GRAPH-248:


Thank you for your suggestion.

I think that all five things you presented are important.

I just removed the http dependency from the s2graphql project and integrated it 
into the s2http project.

I will modify the startup script so that s2http will work in place of 
s2rest_play when we package the project and we will close the issue.




> HTTP interface integration.
> ---------------------------
>                 Key: S2GRAPH-248
>                 URL: https://issues.apache.org/jira/browse/S2GRAPH-248
>             Project: S2Graph
>          Issue Type: Task
>          Components: s2core, s2rest_netty, s2rest_play
>            Reporter: Daewon Jeong
>            Priority: Minor
> The current HTTP interface in S2Graph has the following problems.
>  known issues:
>    1. The `s2rest_netty` project is experimental and supports only `graph 
> traverse` API.
>    2. `s2rest_play` based on Play! Framework. 
>       - Play! Framework is full stack framework, so it has a lot of 
> dependencies that s2graph does not need. 
>       - There is also a conflict with byte buddy for patching asynchbase.
>    3. `GraphQL` is still in the experimental phase and does not yet provide 
> all the functionality.
> The discussion below is written on the link below.
> discussions: 
> [https://lists.apache.org/thread.html/56379268a12ed5e64a2d7497a8741b09cdf2194bf7a3c303000420b6@%3Cdev.s2graph.apache.org%3E]
> Based on this issue, the following work should be done.
>  * Create an HTTP interface project(without play!)
>  * Remove s2rest_netty
>  * API documentation (GraphQL, Rest)
>  * GraphQL and Rest HTTP interface integration

This message was sent by Atlassian JIRA

Reply via email to