[JBoss JIRA] (TEIIDSB-102) Update legacy terminology
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIIDSB-102?page=com.atlassian.jira.plugi... ]
Work on TEIIDSB-102 started by Steven Hawkins.
----------------------------------------------
> 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-5759) DDL grant with condition defaults to not a constraint
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5759:
-------------------------------------
Summary: 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
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 updated TEIIDSB-102:
-----------------------------------
Description:
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.
was:
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?
Others should be captured here as well.
> 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-5670) Create ddl only examples
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5670?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5670:
---------------------------------------
A first pass has been done that cleaned up any references to vdb.xml. Associated vdb examples were converted to ddl as well.
Another pass is still needed for and vdb fragments that didn't specifically reference the .xml file.
> Create ddl only examples
> ------------------------
>
> Key: TEIID-5670
> URL: https://issues.jboss.org/browse/TEIID-5670
> Project: Teiid
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> xml examples should have ddl analogs, and omitted for the spring docs.
--
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)
Steven Hawkins created TEIIDSB-102:
--------------------------------------
Summary: 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
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?
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-5481) Evaluate JSONPATH as expression language for Json payload to table
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5481?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5481:
---------------------------------------
Looked at switching to jackson, but unless static methods are used, it appears that the minidev dependency is still required. The wildfly kit has been updated. Will take another pass through to see about missing tests and docs, then resolve this.
> Evaluate JSONPATH as expression language for Json payload to table
> ------------------------------------------------------------------
>
> Key: TEIID-5481
> URL: https://issues.jboss.org/browse/TEIID-5481
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> Currently in Teiid in order to turn a JSON document to a relational structure, JSONTOXML function is used then XPATH used on it to retrieve data using XMLTABLE.
> Investigate the feasibility of using JSONPATH [1] directly on JSON document to build a JSONTABLE construct.
> [1] https://code.google.com/archive/p/json-path/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months