[teiid-issues] [JBoss JIRA] (TEIID-5718) Provide a flag to disable alter statements

[Steven Hawkins (Jira)]

     [ https://issues.jboss.org/browse/TEIID-5718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5718.
-----------------------------------
    Resolution: Done


Added org.teiid.allowAlter to control whether alter (and sysadmin.setproperty) is allowed at runtime.  The rationale for this flag is that it allows for permission grants to be simple - grant all can be used and ephemeral metadata updates will not be allowed.  If permissions are always set in a fine-grained manner, then this property does not need to be set.  If no security is being used, this property can also be of use.

sysadmin set stats procedures are not affected by this property.

It is also possible to implement this at the validator level or through some changes to the default methods for MetadataRepository or ChainingMetadataRepository, but for now it was simplest to consolidate it onto DDLPlan.

> Provide a flag to disable alter statements
> ------------------------------------------
>
>                 Key: TEIID-5718
>                 URL: https://issues.jboss.org/browse/TEIID-5718
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Major
>
> The engine allows alter statements to ephemerally (by default) change view definitions, turn on/off triggers, etc.  For Spring Boot and OpenShift deployment in particular we should consider whether this should be allowable/optional behavior.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)