[
https://issues.apache.org/jira/browse/ASTERIXDB-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724385#comment-17724385
]
ASF subversion and git services commented on ASTERIXDB-3173:
------------------------------------------------------------
Commit 74e09dacaf206f28fd64ef065b405110dbc3ff9a in asterixdb's branch
refs/heads/master from Ian Maxon
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=74e09dacaf ]
[ASTERIXDB-3173][TEST] Disable cbotest
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
Since we have SqlppAnalyzedExecutionTest, we don't need
to enable the cbotest mode for the *ExecutionTest suites.
Change-Id: I4c164cd517315f8ab9ae8df2baf06b4a72fedae5
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17506
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Vijay Sarathy <[email protected]>
> Disable 'cbotest' for SqlppExecutionTest
> ----------------------------------------
>
> Key: ASTERIXDB-3173
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3173
> Project: Apache AsterixDB
> Issue Type: Task
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Priority: Major
> Labels: triaged
>
> Now that SqlppAnalyzedExecutionTest exists, there isn't much of a reason for
> cbotest to be used. It should be disabled so that pure RBO mode is tested.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
