[JBoss JIRA] (TEIID-5774) Javadoc cleanup
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5774?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5774.
-----------------------------------
Resolution: Done
Added javadoc generation to the default profile, but left it out of the travis builds - for some reason it causes things to fail with java 11. All errors have been addressed, but there are a lot of warnings still.
> Javadoc cleanup
> ---------------
>
> Key: TEIID-5774
> URL: https://issues.jboss.org/browse/TEIID-5774
> Project: Teiid
> Issue Type: Sub-task
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> An open ended jira to cleanup the java doc to the point where the plugin can run with fail on error.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (TEIID-5745) Reduce memory overhead of ddl vdbs
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5745?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5745.
-----------------------------------
Fix Version/s: (was: 12.3)
Resolution: Deferred
This issue largely exists in the memory footprint for xml as well - as we'll have the ddl in source metadata objects. For DDL there's more duplication of structural metadata, but we'll live with that for now.
> Reduce memory overhead of ddl vdbs
> ----------------------------------
>
> Key: TEIID-5745
> URL: https://issues.jboss.org/browse/TEIID-5745
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
>
> Due to mapping to the existing vdb metadata structure we are holding a memory reference to the full ddl. At a minimum that could be replaced with a file reference.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (TEIID-5802) Row based security and column masking don't work correctly for materialized tables (views)
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5802?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5802:
----------------------------------
Priority: Major (was: Blocker)
> Row based security and column masking don't work correctly for materialized tables (views)
> ------------------------------------------------------------------------------------------
>
> Key: TEIID-5802
> URL: https://issues.jboss.org/browse/TEIID-5802
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 12.0
> Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core 6.0.2.Final)
> Reporter: Dmitrii Pogorelov
> Assignee: Steven Hawkins
> Priority: Major
>
> Row based security doesn't work for materialized tables (views). For example, having the following permissions for materialized views.test_view1 and views.test_view2 views according to query plan Teiid applies ApplySecurity rule only for views.test_view2 view but should also apply for views.test_view1 view:
> {code:xml}
> <data-role name="role1" any-authenticated="true" allow-create-temporary-tables="true">
> <description>Allow read only</description>
> <permission>
> <resource-name>dsp</resource-name>
> <allow-read>true</allow-read>
> </permission>
> <permission>
> <resource-name>views.test_view1</resource-name>
> <allow-read>true</allow-read>
> <condition constraint="false">col2 > 1</condition>
> </permission>
> <permission>
> <resource-name>views.test_view2</resource-name>
> <allow-read>true</allow-read>
> <condition constraint="false">col0 = 'sa'</condition>
> </permission>
> </data-role>
> {code}
> The same situation is for column masking feature, see below.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (TEIIDSB-4) Provide rest access with SpringBoot
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-4?page=com.atlassian.jira.plugin.... ]
Ramesh Reddy commented on TEIIDSB-4:
------------------------------------
After working through the complete example, I am looking at retiring the `REST:` metadata semantics for VDB as to keep supporting to make a complete OpenAPI document with return types and various other features as those are extensive and changing. The current implementation will only support an external OpenAPI document that matches with procedure names to `OperationId`. Any requirement for `REST:` need to be reconsidered on user request.
> Provide rest access with SpringBoot
> -----------------------------------
>
> Key: TEIIDSB-4
> URL: https://issues.jboss.org/browse/TEIIDSB-4
> Project: Teiid Spring Boot
> Issue Type: Feature Request
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.2.0
>
>
> The current rest access layer is based upon the generation of a war with deployment hooks in wildfly. There should be a build-time or similar mechanism to expose rest with spring boot.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months