[
https://issues.apache.org/jira/browse/ASTERIXDB-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781564#comment-17781564
]
ASF subversion and git services commented on ASTERIXDB-3246:
------------------------------------------------------------
Commit c20796b932ca07b5201ed8070826ce27bbccfa55 in asterixdb's branch
refs/heads/master from Vijay Sarathy
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=c20796b932 ]
[ASTERIXDB-3246][COMP]: CBO costing of all physical operators in a query plan
Change-Id: I3196f664d716bb5b3806ec9a5a0dd5c1ea51ff62
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17765
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Ian Maxon <[email protected]>
Tested-by: Jenkins <[email protected]>
> CBO costing of all physical operators in a query plan
> -----------------------------------------------------
>
> Key: ASTERIXDB-3246
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3246
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: COMP - Compiler
> Affects Versions: 0.9.6
> Reporter: Vijay Sarathy
> Assignee: Vijay Sarathy
> Priority: Major
> Labels: triaged
>
> In the first version of CBO, the following operators were costed:
> SELECT
> UNNEST_MAP
> DATA_SCAN
> EXCHANGE
> INNER_JOIN
> The costing of these subset of operators provides sufficient information to
> generate good plans for a vast majority of queries.
> The costing of the other operators (like group by, order by, limit, etc.)
> needs to be completed for full coverage of all the operators.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
