You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lisa Owen (JIRA)" <ji...@apache.org> on 2017/01/26 00:26:26 UTC
[jira] [Updated] (HAWQ-1295) verify GUCs in DEVELOPER_OPTIONS
config group
[ https://issues.apache.org/jira/browse/HAWQ-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lisa Owen updated HAWQ-1295:
----------------------------
Priority: Minor (was: Major)
> verify GUCs in DEVELOPER_OPTIONS config group
> ---------------------------------------------
>
> Key: HAWQ-1295
> URL: https://issues.apache.org/jira/browse/HAWQ-1295
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Core, Documentation
> Reporter: Lisa Owen
> Assignee: David Yozie
> Priority: Minor
>
> refer to an attachment to this jira for a list of GUCs that are identified in src/backend/utils/misc/guc.c as members of the DEVELOPER_OPTIONS config group. there is some inconsistency with respect to documenting GUCs of this type and/or whether or not the GUC shows up in hawq config output.
> from [~huor] via hawq dev mailing list: "DEVELOPER GUC: should not in doc; should not show in hawq config"
> need to:
> 1. identify if each GUC in the list is correctly classified as a developer option
> 2. for each GUC identified as a "real" developer option, ensure that the GUC_NO_SHOW_ALL flag is set in the GUC table in guc.c
> 3. for each GUC identified as a "real" developer option, identify how to deal with those that are currently documented
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)