You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Dmitry Lychagin (JIRA)" <ji...@apache.org> on 2018/08/06 20:35:00 UTC
[jira] [Updated] (ASTERIXDB-2434) Ensure operator execution mode
right before invoking EnforceStructuralPropertiesRule
[ https://issues.apache.org/jira/browse/ASTERIXDB-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Lychagin updated ASTERIXDB-2434:
---------------------------------------
Summary: Ensure operator execution mode right before invoking EnforceStructuralPropertiesRule (was: Set operator execution mode right before invoking EnforceStructuralPropertiesRule)
> Ensure operator execution mode right before invoking EnforceStructuralPropertiesRule
> ------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-2434
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2434
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: COMP - Compiler
> Reporter: Dmitry Lychagin
> Assignee: Dmitry Lychagin
> Priority: Minor
>
> Computation of required child properties for some operators (UnionAll, for example) depends on the execution mode of its children (OperatorPropertiesUtil.checkUnpartitionedAndGetPropertiesVector()). Therefore it's important to have correct execution mode for all operators at that time.
> We invoke SetExecutionModeRule during logical rewrites, but by the time EnforceStructuralPropertiesRule is invoked there might be new operators in the plan. We need to invoke SetExecutionModeRule right before EnforceStructuralPropertiesRule to guarantee that execution mode is properly set for all operators.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)