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

Francis Chuang commented on CALCITE-1181:
-----------------------------------------

In `prepareAndExecute`, I get 1 row back (the select statement should return 2 
rows) and `done` is false.
When I use `fetch` to fetch the remaining row, `done` is false, but the array 
of rows is empty.

> FetchResponse always return no rows
> -----------------------------------
>
>                 Key: CALCITE-1181
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1181
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>    Affects Versions: avatica-1.7.1
>         Environment: HBase 1.1 and Phoenix 4.7.0
>            Reporter: Francis Chuang
>            Assignee: Julian Hyde
>
> Assuming I have a table called my_table which is created and seeded like so:
> {code:sql}
> CREATE TABLE my_table (k BIGINT PRIMARY KEY, v VARCHAR) TRANSACTIONAL=true
> UPSERT INTO my_table VALUES (1,'A')
> UPSERT INTO my_table VALUES (2,'B')
> {code}
> I have 2 rows in the table. If I query the table using SELECT * FROM 
> my_table, and request a maxRowCount of 1, using FetchRequest to request 
> further rows always returns 0 rows.
> For ease of reproduction, I have included CURL commands (avatica will need to 
> have serialization set to JSON):
> {code}
> curl localhost:8765 -XPOST --data '{"request": 
> "openConnection","connectionId": "my-conn"}'
> curl localhost:8765 -XPOST --data '{"request": 
> "createStatement","connectionId": "my-conn"}'
> curl localhost:8765 -XPOST --data '{"request": 
> "prepareAndExecute","connectionId": "my-conn","statementId": 12345,"sql": 
> "SELECT * FROM my_table","maxRowCount": 1}' # update the statementId
> curl localhost:8765 -XPOST --data '{"request": "fetch","connectionId": 
> "my-conn","statementId": 12345,"offset": 0,"fetchMaxRowCount": 1}' # update 
> the statementId
> {code}



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

Reply via email to