You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Michael J. Carey (Jira)" <ji...@apache.org> on 2019/11/02 20:42:00 UTC

[jira] [Assigned] (ASTERIXDB-2670) Optimization opportunities for OBJECT_REMOVE_FIELDS

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

Michael J. Carey reassigned ASTERIXDB-2670:
-------------------------------------------

    Assignee: Dmitry Lychagin

> Optimization opportunities for OBJECT_REMOVE_FIELDS
> ---------------------------------------------------
>
>                 Key: ASTERIXDB-2670
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2670
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: SQL - Translator SQL++
>    Affects Versions: 0.9.4.1
>            Reporter: Michael J. Carey
>            Assignee: Dmitry Lychagin
>            Priority: Major
>             Fix For: 0.9.5
>
>
> Consider a query like the following:
> SELECT VALUE OBJECT_REMOVE_FIELDS(t, ["user"]) FROM (SELECT VALUE t FROM TinySocial.ChirpMessages t) t;
> This query will retain all fields in the ChirpMessages except for user, but the SQL++ compiler will currently not understand this (viewing the function call as a black box in all likelihood).  There is a future opportunity to gain performance by pushing the implied projection down lower in the query pipeline, in cases where the query is more complex.



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