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

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

Commit 57577846a75c23d8d247e9f05f76a57d353d400d in asterixdb's branch 
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=5757784 ]

[ASTERIXDB-2933][COMP][EXT] Pushdowns Part1: Expected Schema Node

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

Details:
We want to have a more aggressive pushdown for Parquet. To do so,
we need to compute the expected schema from the expressions in the
query plan. This change introduces the data structure that holds the
expected schema information.

Note:
Moved from asterix-om to asterix-algebra as the expected schema should
not be exposed outside the compiler.

Change-Id: I4b5aef414050a518fe230326e92ed66734b7b1d2
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/12765
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Wael Alkowaileet <wael....@gmail.com>
Reviewed-by: Dmitry Lychagin <dmitry.lycha...@couchbase.com>


> Support more pushdowns when reading Parquet files
> -------------------------------------------------
>
>                 Key: ASTERIXDB-2933
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2933
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: COMP - Compiler, EXT - External data
>    Affects Versions: 0.9.7
>            Reporter: Wail Y. Alkowaileet
>            Assignee: Wail Y. Alkowaileet
>            Priority: Major
>             Fix For: 0.9.7
>
>
> Currently, AsterixDB only supports simple pushdowns for field access. We 
> should allow for more pushdowns including array functions (e.g., array_star).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to