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

Posted to notifications@asterixdb.apache.org by "Dmitry Lychagin (JIRA)" <ji...@apache.org> on 2018/07/21 01:16:00 UTC

[jira] [Resolved] (ASTERIXDB-2417) Issues with LIMIT clause

     [ https://issues.apache.org/jira/browse/ASTERIXDB-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lychagin resolved ASTERIXDB-2417.
----------------------------------------
    Resolution: Fixed

> Issues with LIMIT clause
> ------------------------
>
>                 Key: ASTERIXDB-2417
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2417
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: COMP - Compiler
>            Reporter: Dmitry Lychagin
>            Assignee: Dmitry Lychagin
>            Priority: Minor
>
> 1. When limit or offset is a non-integer value the rule that pushes limits fails with NPE.
> 2. We should allow float/double values that are integers to be specified in limit/offset. 
> 3. Make consistent offset/limit types. Currently StreamLimitRuntimeFactory expects limit/offset to be of type integer, but PushLimitIntoOrderByRule/PushLimitIntoPrimarySearchRule assume bigint. We should make those rules consistent with the runtime.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)