[
https://issues.apache.org/jira/browse/CALCITE-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858056#comment-16858056
]
Hongze Zhang commented on CALCITE-3073:
---------------------------------------
A naive question: Then what should be implemented for this issue? By reading
the issue description:
{quote}With support of from/to timestamp/offset, it's more flexible for users
to query a specific range.
{quote}
And the comment in PR:
{quote}Given a query like SELECT * FROM KAFKA_TABLE WHERE KAFKA_TIMESTAMP >
CURRENT_TIMESTAMP-1, KafkaAdapter would take the filter clause KAFKA_TIMESTAMP
> CURRENT_TIMESTAMP-1 directly.
{quote}
Didn't we already support SQL like {{SELECT STREAM * FROM KAFKA_TABLE WHERE
MSG_TIMESTAMP > CURRENT_TIMESTAMP - 1}} in Kafka adaptor (Maybe tweaking on
data types is needed)? Or the topic is more about performance improvement?
> Support to consume from timestamp in KafkaAdapter
> -------------------------------------------------
>
> Key: CALCITE-3073
> URL: https://issues.apache.org/jira/browse/CALCITE-3073
> Project: Calcite
> Issue Type: Improvement
> Components: kafka-adapter
> Reporter: Xu Mingmin
> Assignee: Matt Wang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Currently the KafkaAdapter consumes data from default
> offset(latest/earliest/last_offset) and runs forever. With support of from/to
> timestamp/offset, it's more flexible for users to query a specific range.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
