[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573511#comment-16573511
 ] 

ASF subversion and git services commented on ASTERIXDB-2438:
------------------------------------------------------------

Commit aeb6e3bc2e7e45e6bfe38b72c4cfdb76d9920b8c in asterixdb's branch 
refs/heads/master from [~dlychagin-cb]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=aeb6e3b ]

[ASTERIXDB-2438][COMP] Allow assigns when pushing limit into data scan

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- Handle assign operators between select and data scan
  when pushing limit into data scan

Change-Id: I3b68890d034dded3db7572462f47161721aa18fa
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2856
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Reviewed-by: Taewoo Kim <[email protected]>


> Consider assigns when pushing limit with condition into data scan
> -----------------------------------------------------------------
>
>                 Key: ASTERIXDB-2438
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2438
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: COMP - Compiler
>            Reporter: Dmitry Lychagin
>            Assignee: Dmitry Lychagin
>            Priority: Minor
>
> Currently PushLimitIntoPrimarySearchRule stops at assign operators and 
> therefore doesn't not push select condition into data-scan if there's an 
> assign in between. We should fix this to allow such conditions be pushed into 
> data scan.
> Here are example queries:
> Q1:
> select substring(dblpid, 0, 21)
> from DBLP1
> where dblpid > "series"
> limit 1;
> Q2:
> select value t.user.lang
> from TweetMessages t
> where t.user.friends_count between 0 and 150
> limit 2
>  



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

Reply via email to