You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/28 10:58:00 UTC

[jira] [Commented] (DRILL-8253) Support the limit results in kafka scan

|  ![](cid:jira-generated-image-avatar-867cdd7c-21ab-4d03-a6ac-7261a5257fb6) |
[ASF GitHub
Bot](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=githubbot)
**commented** on [![Improvement](cid:jira-generated-image-
avatar-23979328-485b-4504-a6ab-9c947370b8a4)
DRILL-8253](https://issues.apache.org/jira/browse/DRILL-8253)  
---|---  
|  
---  
|  [Re: Support the limit results in kafka
scan](https://issues.apache.org/jira/browse/DRILL-8253)  
---  
|

luocooong opened a new pull request, #2580:  
URL: <https://github.com/apache/drill/pull/2580>

  1. [DRILL-8253](https://issues.apache.org/jira/browse/DRILL-8253 "Support the limit results in kafka scan")(<https://issues.apache.org/jira/browse/DRILL-8253):> Support the limit results in kafka scan

  1.     1. Description  
In the current implementation of the kafka storage, although we use the limit
detection method in the result loader, but the actual `maxRecords` is always
-1.

The mechanism for this revision is to get limit (SQL parsing from the
execution plan stage) from the group scan, then pass it to the sub-scan, and
finally process it in the result loader.

  1.     1. Documentation  
N/A

  1.     1. Testing  
Added the unit test. KafkaQueriesTest#testResultLimit()

  
---  
|  |  [ ![Add Comment](cid:jira-generated-image-static-comment-
icon-35ce2daa-f786-477c-b8bc-225b679e10e3)
](https://issues.apache.org/jira/browse/DRILL-8253#add-comment "Add Comment")
|  [Add Comment](https://issues.apache.org/jira/browse/DRILL-8253#add-comment
"Add Comment")  
---|---  
  
|  This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9) |  |
![Atlassian logo](https://issues.apache.org/jira/images/mail/atlassian-email-
logo.png)  
---