[
https://issues.apache.org/jira/browse/DRILL-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491341#comment-16491341
]
ASF GitHub Bot commented on DRILL-5977:
---------------------------------------
kkhatua commented on issue #1272: DRILL-5977: Filter Pushdown in Drill-Kafka
plugin
URL: https://github.com/apache/drill/pull/1272#issuecomment-392204078
@akumarb2010 I haven't gone through @aravi5 's PR in detail, but I did see
an interactive demo where we tried out quite a few of the scenarios.
Semantically, it might not make much sense define offsets without specifying
partitions, but it doesn't hurt to have the capability. We were trying to do
exploration of stream data during the demo, and offsets might prove to be a
good way to just explore data in a topic on the assumption that the offsets for
all the partitions are not wildly different for a similar time range (that is
not granular).
Only if there is a benefit of adding to the complexity of the code, such as
performance (or even debugging issues), it _might_ be worth pursuing the
additional changes.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> predicate pushdown support kafkaMsgOffset
> -----------------------------------------
>
> Key: DRILL-5977
> URL: https://issues.apache.org/jira/browse/DRILL-5977
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: B Anil Kumar
> Assignee: Abhishek Ravi
> Priority: Major
> Fix For: 1.14.0
>
>
> As part of Kafka storage plugin review, below is the suggestion from Paul.
> {noformat}
> Does it make sense to provide a way to select a range of messages: a starting
> point or a count? Perhaps I want to run my query every five minutes, scanning
> only those messages since the previous scan. Or, I want to limit my take to,
> say, the next 1000 messages. Could we use a pseudo-column such as
> "kafkaMsgOffset" for that purpose? Maybe
> SELECT * FROM <some topic> WHERE kafkaMsgOffset > 12345
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
