[JBoss JIRA] (TEIIDSB-101) OData issues with multiple visible schema
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-101?page=com.atlassian.jira.plugi... ]
Work on TEIIDSB-101 stopped by Steven Hawkins.
----------------------------------------------
> OData issues with multiple visible schema
> -----------------------------------------
>
> Key: TEIIDSB-101
> URL: https://issues.jboss.org/browse/TEIIDSB-101
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.2.0
>
>
> The odata logic accommodates a subcontext specifying the schema to access. Other logic however doesn't allow for this:
> * if multiple visible schema are exposed and have a cross reference, then the metadata links will be invalid as they are created based upon the Teiid Wildfly conventions.
> * The keycloak logic exposes /$metadata as unsecured, but any of the schema/$metadata links would require authentication.
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIIDSB-101) OData issues with multiple visible schema
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-101?page=com.atlassian.jira.plugi... ]
Work on TEIIDSB-101 started by Steven Hawkins.
----------------------------------------------
> OData issues with multiple visible schema
> -----------------------------------------
>
> Key: TEIIDSB-101
> URL: https://issues.jboss.org/browse/TEIIDSB-101
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.2.0
>
>
> The odata logic accommodates a subcontext specifying the schema to access. Other logic however doesn't allow for this:
> * if multiple visible schema are exposed and have a cross reference, then the metadata links will be invalid as they are created based upon the Teiid Wildfly conventions.
> * The keycloak logic exposes /$metadata as unsecured, but any of the schema/$metadata links would require authentication.
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5759) DDL grant with condition defaults to not a constraint
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5759?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5759.
-----------------------------------
Resolution: Done
Implemented the syntax shown above, updated the docs, and added a release note about the backwards compatibility flag.
> DDL grant with condition defaults to not a constraint
> -----------------------------------------------------
>
> Key: TEIID-5759
> URL: https://issues.jboss.org/browse/TEIID-5759
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Converting from an xml vdb to a ddl will not correctly convey the isConstraint flag for permissions as it default to false for ddl vdbs even if it is null in the xml form.
> One solution is a breaking change to the syntax:
> <CONDITION> [[<NOT>] <CONSTRAINT>]
> that will capture null, false, and true values. Such that omitting the clause would mean that the condition is a constraint - which is the opposite of the ddl behavior currently. A switch could be introduced that would allow for the old default, should it be needed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIIDSB-102) Update legacy terminology
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-102?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIIDSB-102:
----------------------------------------
jaas role -> foreign role, and the syntax of create role will simplify - you can create with either "ANY AUTHENTICATED" or with a "FOREIGN ROLE" list.
jndi-name -> resource-name
model update count is just a doc issue. No where in the grammar do we use the term model. We'll need a general issue on deprecating the term model.
> Update legacy terminology
> -------------------------
>
> Key: TEIIDSB-102
> URL: https://issues.jboss.org/browse/TEIIDSB-102
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 1.2.0
>
>
> There are several places where we are using old terminology:
> * updating model count - should not use the term model, and would be better phrased in terms of the transactional requirement.
> * jndi-name - could be bean-name to be more spring specific. Could be source-name, but that's an overloaded term. connection-source?
> * jaas role
> Others should be captured here as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5761) ConvertVDB incorrectly converts older style chained imports
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5761?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5761.
-----------------------------------
Resolution: Done
Updated the logic to tokenize the repo type.
> ConvertVDB incorrectly converts older style chained imports
> -----------------------------------------------------------
>
> Key: TEIID-5761
> URL: https://issues.jboss.org/browse/TEIID-5761
> Project: Teiid
> Issue Type: Quality Risk
> Components: Tooling
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> {code}
> <vdb name="{vdb-name}" version="1">
> <model name="{model-name}" type="PHYSICAL">
> <source name="AccountsDB" translator-name="oracle" connection-jndi-name="java:/oracleDS"/>
> <metadata type="NATIVE,DDL"><![CDATA[
> CREATE FOREIGN FUNCTION SCORE (val integer) RETURNS integer;
> ]]>
> </metadata>
> </model>
> </vdb>
> {code}
> Results in:
> {code}
> CREATE DATABASE "{vdb-name}" VERSION '1';
> USE DATABASE "{vdb-name}" VERSION '1';
> --############ Translators ############
> CREATE FOREIGN DATA WRAPPER oracle;
> --############ Servers ############
> CREATE SERVER AccountsDB FOREIGN DATA WRAPPER oracle OPTIONS ("jndi-name" 'java:/oracleDS');
> --############ Schemas ############
> CREATE SCHEMA "{model-name}" SERVER AccountsDB;
> --############ Schema:{model-name} ############
> SET SCHEMA "{model-name}";
> IMPORT FROM REPOSITORY "NATIVE,DDL" INTO "{model-name}";
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5760) Utilize the isImmutable ExecutionFactory property
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5760?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5760.
-----------------------------------
Resolution: Done
Updated the logic. If isImmutable is true, then the transaction support will be reported as none and no updates will be allowed. This is now reflected in the docs as well.
> Utilize the isImmutable ExecutionFactory property
> -------------------------------------------------
>
> Key: TEIID-5760
> URL: https://issues.jboss.org/browse/TEIID-5760
> Project: Teiid
> Issue Type: Quality Risk
> Components: Connector API
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> We have left the isImmutable method and documentation, but have not wired the method up to any engine logic for quite some time. It should be wired in again.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5761) ConvertVDB incorrectly converts older style chained imports
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5761?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-5761:
-------------------------------------
Assignee: Steven Hawkins (was: Barry LaFond)
> ConvertVDB incorrectly converts older style chained imports
> -----------------------------------------------------------
>
> Key: TEIID-5761
> URL: https://issues.jboss.org/browse/TEIID-5761
> Project: Teiid
> Issue Type: Quality Risk
> Components: Tooling
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> {code}
> <vdb name="{vdb-name}" version="1">
> <model name="{model-name}" type="PHYSICAL">
> <source name="AccountsDB" translator-name="oracle" connection-jndi-name="java:/oracleDS"/>
> <metadata type="NATIVE,DDL"><![CDATA[
> CREATE FOREIGN FUNCTION SCORE (val integer) RETURNS integer;
> ]]>
> </metadata>
> </model>
> </vdb>
> {code}
> Results in:
> {code}
> CREATE DATABASE "{vdb-name}" VERSION '1';
> USE DATABASE "{vdb-name}" VERSION '1';
> --############ Translators ############
> CREATE FOREIGN DATA WRAPPER oracle;
> --############ Servers ############
> CREATE SERVER AccountsDB FOREIGN DATA WRAPPER oracle OPTIONS ("jndi-name" 'java:/oracleDS');
> --############ Schemas ############
> CREATE SCHEMA "{model-name}" SERVER AccountsDB;
> --############ Schema:{model-name} ############
> SET SCHEMA "{model-name}";
> IMPORT FROM REPOSITORY "NATIVE,DDL" INTO "{model-name}";
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5761) ConvertVDB incorrectly converts older style chained imports
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5761:
-------------------------------------
Summary: ConvertVDB incorrectly converts older style chained imports
Key: TEIID-5761
URL: https://issues.jboss.org/browse/TEIID-5761
Project: Teiid
Issue Type: Quality Risk
Components: Tooling
Reporter: Steven Hawkins
Assignee: Barry LaFond
Fix For: 12.3
{code}
<vdb name="{vdb-name}" version="1">
<model name="{model-name}" type="PHYSICAL">
<source name="AccountsDB" translator-name="oracle" connection-jndi-name="java:/oracleDS"/>
<metadata type="NATIVE,DDL"><![CDATA[
CREATE FOREIGN FUNCTION SCORE (val integer) RETURNS integer;
]]>
</metadata>
</model>
</vdb>
{code}
Results in:
{code}
CREATE DATABASE "{vdb-name}" VERSION '1';
USE DATABASE "{vdb-name}" VERSION '1';
--############ Translators ############
CREATE FOREIGN DATA WRAPPER oracle;
--############ Servers ############
CREATE SERVER AccountsDB FOREIGN DATA WRAPPER oracle OPTIONS ("jndi-name" 'java:/oracleDS');
--############ Schemas ############
CREATE SCHEMA "{model-name}" SERVER AccountsDB;
--############ Schema:{model-name} ############
SET SCHEMA "{model-name}";
IMPORT FROM REPOSITORY "NATIVE,DDL" INTO "{model-name}";
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5760) Utilize the isImmutable ExecutionFactory property
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5760:
-------------------------------------
Summary: Utilize the isImmutable ExecutionFactory property
Key: TEIID-5760
URL: https://issues.jboss.org/browse/TEIID-5760
Project: Teiid
Issue Type: Quality Risk
Components: Connector API
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.3
We have left the isImmutable method and documentation, but have not wired the method up to any engine logic for quite some time. It should be wired in again.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months