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

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

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

[ASTERIXDB-2344] LIMIT pushdown for primary index

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

Details:
-Implement LIMIT pushdown for primary index scan/lookup. In case of
a select operator, we also push the select condition to the priamry
search operator to ensure correctness.

Change-Id: I824fcad79995325e12a1a81d629160025294b915
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2541
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Dmitry Lychagin <dmitry.lycha...@couchbase.com>


> Predicate/LIMIT pushdown for primary scans
> ------------------------------------------
>
>                 Key: ASTERIXDB-2344
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2344
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: COMP - Compiler, STO - Storage
>            Reporter: Chen Luo
>            Assignee: Chen Luo
>            Priority: Major
>
> Currently we don't have limit/predicate pushdown for simple select queries, 
> e.g.,
> {code}
> select *
> from ds_tweet
> where friends_count < 10
> limit 5;
> {code}
> It'll be nice to have:
> 1. pushdown predicates to dataset scan operator 
> (IndexSearchOperatorNodePushable) such that only quantified records are 
> returned to the outside;
> 2. pushdown LIMIT to dataset scan operator when possible so that the query 
> can be terminated once enough records are fetched;



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

Reply via email to