[JBoss JIRA] (TEIID-4724) Allow support for vdb.ddl in the .vdb files
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4724?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-4724.
---------------------------------
Resolution: Done
Labels: Alpaha1 (was: )
Added support for deploying the .vdb files with embedded vdb.ddl and supporting embedded ddl files inside the .vdb archive
> Allow support for vdb.ddl in the .vdb files
> -------------------------------------------
>
> Key: TEIID-4724
> URL: https://issues.jboss.org/browse/TEIID-4724
> Project: Teiid
> Issue Type: Enhancement
> Components: VDB
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: Alpaha1
> Fix For: 9.3
>
>
> With the DDL based metadata, ".vdb" file archive should allow to contain a "vdb.ddl" file that can be deployed. Based on TEIID-4719 this needs to allow to load metadata from INDEX and DDL-FILE metadata repositories.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4801) Allow support for vdb.ddl in the .vdb files
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-4801:
-----------------------------------
Summary: Allow support for vdb.ddl in the .vdb files
Key: TEIID-4801
URL: https://issues.jboss.org/browse/TEIID-4801
Project: Teiid
Issue Type: Enhancement
Components: VDB
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 9.3
With the DDL based metadata, ".vdb" file archive should allow to contain a "vdb.ddl" file that can be deployed. Based on TEIID-4719 this needs to allow to load metadata from INDEX and DDL-FILE metadata repositories.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4537) Store ddl as fully qualified
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4537?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4537:
----------------------------------
Fix Version/s: 10.0
(was: 9.3)
Moving to 10 as we've limited the ddl work for 9.3 and these are applicable to the larger changes to allow interactive ddl processing.
> Store ddl as fully qualified
> ----------------------------
>
> Key: TEIID-4537
> URL: https://issues.jboss.org/browse/TEIID-4537
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> To prevent later statements (in particular create) from causing issues with existing objects, the original sql will need to be stored fully qualified.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4538) Enforce authorizations
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4538?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4538:
----------------------------------
Fix Version/s: 10.0
(was: 9.3)
Moving to 10 as we've limited the ddl work for 9.3 and these are applicable to the larger changes to allow interactive ddl processing.
> Enforce authorizations
> ----------------------
>
> Key: TEIID-4538
> URL: https://issues.jboss.org/browse/TEIID-4538
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> For the new ddl statement types, they are executed without checking authorizations. We have talked about several strategies including allowing vdb edit only if authorizing with an admin security domain.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4539) Reduce memory footprint of DatabaseStore
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4539?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4539:
----------------------------------
Fix Version/s: 10.0
(was: 9.3)
Moving to 10 as we've limited the ddl work for 9.3 and these are applicable to the larger changes to allow interactive ddl processing.
> Reduce memory footprint of DatabaseStore
> ----------------------------------------
>
> Key: TEIID-4539
> URL: https://issues.jboss.org/browse/TEIID-4539
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> The DatabaseStore holds an in-memory copy of Databases and there is the functional VDBRepository copy as well. String canonicalization in the metadata objects should help with reducing the memory footprint, but it may be good to go further and use clones of the functional metadata on demand.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-2167) Permissions should also specify object type
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2167?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2167.
-----------------------------------
Resolution: Done
Added the ability to track the resource type as well. Since this value is optional for backwards compatibility no additional runtime validation was added for the property, but if converted to ddl we'll enforce the validity of the resource.
> Permissions should also specify object type
> -------------------------------------------
>
> Key: TEIID-2167
> URL: https://issues.jboss.org/browse/TEIID-2167
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.3
>
>
> Teiid permissions only specify a resource name. However it is possible to have to have conflicting schema/table (since we are using non-sql safe unquoted names) or table/procedure names.
> Ideally we would use proper sql names (this is true everywhere, not just in permissions) and specify the object type (TABLE, PROCEDURE, SCHEMA, LANGUAGE, FUNCTION, etc.). This would also allow us to have a more standard USAGE permission, rather than something like LANGUAGE, which is used to convey the permission and object type.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4800) Permissions should also specify object type
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4800?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4800:
----------------------------------
Component/s: (was: Query Engine)
Description: Starting with TEIID 9 and TEIID-2167 the permission xml definition may optionally specify the resource type as well in a resource-type element. (was: Teiid permissions only specify a resource name. However it is possible to have to have conflicting schema/table (since we are using non-sql safe unquoted names) or table/procedure names.
Ideally we would use proper sql names (this is true everywhere, not just in permissions) and specify the object type (TABLE, PROCEDURE, SCHEMA, LANGUAGE, FUNCTION, etc.). This would also allow us to have a more standard USAGE permission, rather than something like LANGUAGE, which is used to convey the permission and object type.)
Fix Version/s: (was: 9.3)
> Permissions should also specify object type
> -------------------------------------------
>
> Key: TEIID-4800
> URL: https://issues.jboss.org/browse/TEIID-4800
> Project: Teiid
> Issue Type: Quality Risk
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> Starting with TEIID 9 and TEIID-2167 the permission xml definition may optionally specify the resource type as well in a resource-type element.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years