[ https://issues.apache.org/jira/browse/KYLIN-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yerui Sun updated KYLIN-1274: ----------------------------- Attachment: KYLIN-1274-2.x-staging.patch KYLIN-1274-1.x-staging.patch The patches for branch 1.x-staging and 2.x-staging, same in fact. > Query from JDBC is partial results by default > --------------------------------------------- > > Key: KYLIN-1274 > URL: https://issues.apache.org/jira/browse/KYLIN-1274 > Project: Kylin > Issue Type: Bug > Components: Driver - JDBC > Affects Versions: v1.2 > Reporter: Yerui Sun > Assignee: Yerui Sun > Fix For: v2.0, v1.3 > > Attachments: KYLIN-1274-1.x-staging.patch, > KYLIN-1274-2.x-staging.patch > > > How to produce this problem: create a query with the result over 10000 rows, > and query with 'order by desc'. Check the first row, it's not the last row in > all result, but a middle row, maybe the 10000th row. > Checked the query log in kylin server, found 'Accept Partial: false', > indicating it's indeed a partial query. > The reason is, JDBC driver sent the QueryRequest with json encoding, and > parsed into SQLRequest in server side. By default, QueryRequest only has sql > and project parameters, and leave all other attributes as default in > SQLRequest, and in SQLRequest, acceptPartial is true. That's why the query > was processed as a partial query. > The solution to solve this is simple, add acceptPartial as false in > QueryRequest, and update JDBC driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)