[jira] [Commented] (HAWQ-55) System admin cannot set optimizer_release_mdcache (OFF) when gp_metadata_versioning is (OFF)

["Caleb Welton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HAWQ-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109111#comment-15109111 ] 

Caleb Welton commented on HAWQ-55:
----------------------------------

It looks like https://github.com/apache/incubator-hawq/pull/41 addressed this issue, is there a reason the jira is still open?

> System admin cannot set optimizer_release_mdcache (OFF) when gp_metadata_versioning is (OFF)
> --------------------------------------------------------------------------------------------
>
>                 Key: HAWQ-55
>                 URL: https://issues.apache.org/jira/browse/HAWQ-55
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Metadata Versioning
>            Reporter: George Caragea
>            Assignee: George Caragea
>
> As a system admin, I should not be able to set optimizer_release_mdcache (OFF) when gp_metadata_versioning is (OFF) so that I cannot get into a incorrect state with unexpected behavior from the host system.
> *Acceptance Criteria*
> GIVEN I am a system
> AND gp_metadata_versioning is OFF
> WHEN I try to set optimizer_release_mdcache (OFF)
> THEN I should see a warning message stating that if optimizer_release_mdcache is to be turned OFF, set gp_metadata_versioning should be turned ON
> *Context*
> Default:
> optimizer_release_mdcache (ON)
> gp_metadata_versioning (OFF)
> Bad state: We don't want the user to be able to do this
> optimizer_release_mdcache (OFF)
> gp_metadata_versioning (OFF)
> If a user turns optimizer_release_mdcache (OFF), then gp_metadata_versioning should be turned (ON). Otherwise, the optimizer can end up using stale data in the metadata cache, generating unexpected behavior. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)