[
https://issues.apache.org/jira/browse/TAJO-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574532#comment-14574532
]
ASF GitHub Bot commented on TAJO-1638:
--------------------------------------
GitHub user charsyam opened a pull request:
https://github.com/apache/tajo/pull/599
TAJO-1638 Remove offset parameter from rest api result/{cacheId}
in result/{cacheId}
rest api.
offset parameter can make user confused.
because offset can't go back.
It's only set forward(not backward)
and add 3 new header for result response.
X-Tajo-Offset : from start offset
X-Tajo-Count: fetch count
X-Tajo-EOS: if there is end stream. it sets EOS true
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/charsyam/tajo feature/rest-api-remove-offset
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/599.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #599
----
commit d58f48fddf8485621d914bcb45cf64cca0285eb7
Author: clark.kang <[email protected]>
Date: 2015-06-05T13:56:42Z
remove-offset
----
> Remove offset parameter from rest api result/{cacheId}
> ------------------------------------------------------
>
> Key: TAJO-1638
> URL: https://issues.apache.org/jira/browse/TAJO-1638
> Project: Tajo
> Issue Type: Improvement
> Reporter: DaeMyung Kang
>
> in result/{cacheId} rest api.
> offset parameter can make user confused.
> because offset can't go back.
> It's only set forward(not backward)
> and add 3 new header for result response.
> X-Tajo-Offset : from start offset
> X-Tajo-Count: fetch count
> X-Tajo-EOS: if there is end stream. it sets EOS true
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
