flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fhueske <...@git.apache.org>
Subject [GitHub] flink issue #4263: [FLINK-6075] - Support Limit/Top(Sort) for Stream SQL
Date Mon, 17 Jul 2017 12:40:11 GMT
Github user fhueske commented on the issue:

    https://github.com/apache/flink/pull/4263
  
    Hi @rtudoran, you are right, I said we will need retraction for OFFSET and FETCH. However,
it is only required for the general case and the special case of `ORDER BY *time ASC` without
updates should be implemented without. 
    
    IMO, the semantics of a query are fixed and not really up for discussion. Just imagine
a regular database would execute the same query on a table that holds the same data as the
stream. This defines the result of the streaming query that our operators must produce.
    
    Moving forward, I would modify this PR to support `ORDER BY` with `OFFSET` and `FETCH`
for append-only input by extending the existing operators with counters and open JIRAs for
the other two cases (`ORDER BY *time DESC` and `ORDER BY *`).
    
    Best, Fabian


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message