[ 
https://issues.apache.org/jira/browse/TAJO-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584546#comment-14584546
 ] 

Hudson commented on TAJO-1636:
------------------------------

ABORTED: Integrated in Tajo-master-CODEGEN-build #368 (See 
[https://builds.apache.org/job/Tajo-master-CODEGEN-build/368/])
TAJO-1636: query rest api uri should change from 
/databases/{database_name}/queies to /queries. (blrunner: rev 
dc4904987dc16164dca4ff37c1178698537201c6)
* 
tajo-core/src/main/java/org/apache/tajo/ws/rs/resources/QueryResultResource.java
* tajo-core/src/main/java/org/apache/tajo/ws/rs/resources/QueryResource.java
* 
tajo-core/src/test/java/org/apache/tajo/ws/rs/resources/TestQueryResultResource.java
* CHANGES
* tajo-core/src/test/java/org/apache/tajo/ws/rs/resources/TestQueryResource.java


> query rest api uri should change from /databases/{database_name}/queies to 
> /queries
> -----------------------------------------------------------------------------------
>
>                 Key: TAJO-1636
>                 URL: https://issues.apache.org/jira/browse/TAJO-1636
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: DaeMyung Kang
>            Assignee: DaeMyung Kang
>             Fix For: 0.11.0
>
>
> currently, "databases" Rest Api uri has too many meaning.
> 1. for query
> 2. to manage databases info
> and databases/
> {database_name}/queries is not proper for queries 
> so I suggest change from "/databases/{database_name}
> /queries" to
> "/queries/", it is more clear to understand.
> below apis will changed.
> POST /databases/{databaseName}/queries -> POST /queries
> GET /databases/{databaseName}/queries -> GET /queries
> GET /databases/{databaseName}/queries/{queryId} -> GET /queries/{queryId}
> GET /databases/{databaseName}/queries/{queryId}/result -> GET 
> /queries/{queryId}/result
> GET /databases/{databaseName}/queries/{queryId}/result/{cacheId} -> GET 
> /queries/{queryId}/result/{cacheId}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to