[JBoss JIRA] (TEIID-4382) array_agg does not properly handle array values
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4382:
-------------------------------------
Summary: array_agg does not properly handle array values
Key: TEIID-4382
URL: https://issues.jboss.org/browse/TEIID-4382
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.12
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1
array_agg(array value) - will fail to create the expected multi-dimensional array value as the ArrayAgg logic does not properly unnest the ArrayImpl values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4100) Full odata expand support
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4100?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4100:
---------------------------------------
The approach that seems simplest here is to fetch the expanded entities inline using subqueries of the form:
select parent cols ... (select array_agg((child cols)) [order by] from child ...), (select array_agg ...) ...
This will create a tree of arrays that can be walked similar to the parent result set. This will not be as performant as the join approach for a single expand child, so there may need to be some thought put into converting a single subquery into a join (which we currently do for subqueries in the where clause).
> Full odata expand support
> -------------------------
>
> Key: TEIID-4100
> URL: https://issues.jboss.org/browse/TEIID-4100
> Project: Teiid
> Issue Type: Feature Request
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> To move TEIID-3039 we need to have xml document model style processing for expand support. That is top down generation that supports arbitrary descendants - with targeted optimizations for projection minimization and dependent joins.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-2578) add/remove schema elements
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2578:
-------------------------------------
The revised syntax would be
{code}
#create a data role
CREATE DATA ROLE <data-role> [WITH JAAS ROLE <string>(,<string>)*]
#assign grants to data role
GRANT ( SELECT | INSERT | UPDATE | DELETE | EXECUTE | LANGUAGE | ALTER | DROP | ALL PRIVILEGES | TEMP TABLES )
ON
(
DATABASE
TABLE <schema-name>.<table-name>
PROCEDURE <schema-name>.<proc-name>
SCHEMA <schema-name>
COLUMN <schema-name>.<table-name>.<col-name> [MASK [ORDER \d] <string-val> ] [CONDITION [CONSTRAINT] <string-val>]
)
TO <data-role-name>
{code}
> add/remove schema elements
> --------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-4380) ODatat 4 deep insert works for only a single expand level
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4380:
-------------------------------------
Summary: ODatat 4 deep insert works for only a single expand level
Key: TEIID-4380
URL: https://issues.jboss.org/browse/TEIID-4380
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1
Inserting an entity with a graph more complicated than a single expand won't work as expected - in most cases an exception will be thrown after the inserts are performed / committed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months