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 2021/06/14 04:31:00 UTC
[jira] [Assigned] (ASTERIXDB-2914) Need to see through
object_remove / object_remove_fields functions
[ https://issues.apache.org/jira/browse/ASTERIXDB-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael J. Carey reassigned ASTERIXDB-2914:
-------------------------------------------
Assignee: Dmitry Lychagin
> Need to see through object_remove / object_remove_fields functions
> ------------------------------------------------------------------
>
> Key: ASTERIXDB-2914
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2914
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Michael J. Carey
> Assignee: Dmitry Lychagin
> Priority: Major
>
> Consider the following sequence of steps using the Don C book data:
> _USE DonCData;_
> _CREATE INDEX custidx ON orders(custid: string);_
> _WITH orders2 AS (SELECT VALUE object_remove(o, 'ship_date') FROM orders o)_
> _SELECT VALUE o2 FROM orders2 o2 WHERE o2.custid = 'C41';_
> The query fails to use the index because it doesn't understand object_remove. The optimizer needs to understand the input/output types and properties associated with the field removal functions - as a prerequisite to efficiently supporting negative projections like MongoDB and some other systems do.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)