[JBoss JIRA] (TEIID-4780) Clone TEIID-4734 (Backwards compatible solution)
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4780?page=com.atlassian.jira.plugin... ]
Jan Stastny reopened TEIID-4780:
--------------------------------
The problem still exists in 8.12.x
When I have any datasource (used oracle12 db) and I restart the server while there is 'LOADING' state in the statustable for a materialized view, even the SYSADMIN.loadMatView procedure can't trigger the materialization procedure.
We're checking this via BEFORE_LOAD_SCRIPT where we are incrementing a value to get a count of materialization cycles performed. After restart the count doesn't change, unless we delete the 'LOADING' row from the statustable after restart.
> Clone TEIID-4734 (Backwards compatible solution)
> ------------------------------------------------
>
> Key: TEIID-4780
> URL: https://issues.jboss.org/browse/TEIID-4780
> Project: Teiid
> Issue Type: Sub-task
> Components: Common
> Affects Versions: 9.1.2
> Reporter: Pedro Inácio
> Assignee: Ramesh Reddy
> Fix For: 9.2.1, 9.1.4, 8.12.10.6_3
>
>
> This is clone of TEIID-4734, however the solution provided through it is a breaking change. This JIRA is logged to provide a non-breaking change for released Teiid versions based on comments from TEIID-4734
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4813) Basic support for joins in OData v2
by Damien B (JIRA)
[ https://issues.jboss.org/browse/TEIID-4813?page=com.atlassian.jira.plugin... ]
Damien B resolved TEIID-4813.
-----------------------------
Resolution: Rejected
> Basic support for joins in OData v2
> -----------------------------------
>
> Key: TEIID-4813
> URL: https://issues.jboss.org/browse/TEIID-4813
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Damien B
> Assignee: Steven Hawkins
>
> It's half a bug, half a feature request :-)
> We deal with a perticular OData almost v2 server that uses system functions disguised as entitities. Basically, "/A('b')/C" works but not "/C?$filter=foo eq 'b'". In order to have that, we've enabled the joins support on the ODataTranslator, but we still haven't the right query generated. We've traced back the origin to the optimizer:
> * SELECT * FROM a join b ON a.x=b.y WHERE a.x='v'
> * is optimized as SELECT <columns> FROM a join b ON a.x=b.y WHERE a.x='v' AND b.y='v'
> The extra induced condition "b.y = 'v'" messes up with the URL construction. Any idea about how to proceed from there?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4813) Basic support for joins in OData v2
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4813?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4813:
-------------------------------------
If you extended the ODataTranslator what you do with the extra predicate is up to you in your code, as long as you are returning the right results then everything else should work fine.
Also, please open any forum discussion before opening a JIRA, as we would like to use JIRA only for bugs and features, and it will be better for searching. thanks.
> Basic support for joins in OData v2
> -----------------------------------
>
> Key: TEIID-4813
> URL: https://issues.jboss.org/browse/TEIID-4813
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Reporter: Damien B
> Assignee: Steven Hawkins
>
> It's half a bug, half a feature request :-)
> We deal with a perticular OData almost v2 server that uses system functions disguised as entitities. Basically, "/A('b')/C" works but not "/C?$filter=foo eq 'b'". In order to have that, we've enabled the joins support on the ODataTranslator, but we still haven't the right query generated. We've traced back the origin to the optimizer:
> * SELECT * FROM a join b ON a.x=b.y WHERE a.x='v'
> * is optimized as SELECT <columns> FROM a join b ON a.x=b.y WHERE a.x='v' AND b.y='v'
> The extra induced condition "b.y = 'v'" messes up with the URL construction. Any idea about how to proceed from there?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4534) Querying 1-to-many relationship in JDG data source may return the wrong results
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4534?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4534:
------------------------------------
To ensure the correct number of rows are returned, the logic will be changed so that the criteria is applied twice, first used in the DSL query to JDG, and then the second time the criteria will be applied on the child objects before the rows are created for the resultset.
> Querying 1-to-many relationship in JDG data source may return the wrong results
> -------------------------------------------------------------------------------
>
> Key: TEIID-4534
> URL: https://issues.jboss.org/browse/TEIID-4534
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.x, 9.2
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Critical
>
> When there is a 1-to-many relationship defined in a JDG schema, the results from querying the "many" relationship may return the wrong results.
> Example:
> Person --> Phone Numbers
> INSERT INTO Person(id,name,email) VALUES (1,'name1','email1')
> INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567');
> INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568');
> SELECT p.name, p.id, pn.number FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 and number = '001234568'
> or
> Select * from PhoneNumber where number = '001234568'
> return 2 rows, 1 for each phonenumber.
> Why? Because JDG returns the Person object that meets those conditions. It doesn't filter the internal data to the Person object. Therefore, all phonenumbers are returned for the same person, generating a row for each.
> This doesn't happen with 1-to-1 relationships because there's only ever 1 child object.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4813) Basic support for joins in OData v2
by Damien B (JIRA)
Damien B created TEIID-4813:
-------------------------------
Summary: Basic support for joins in OData v2
Key: TEIID-4813
URL: https://issues.jboss.org/browse/TEIID-4813
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Damien B
Assignee: Steven Hawkins
It's half a bug, half a feature request :-)
We deal with a perticular OData almost v2 server that uses system functions disguised as entitities. Basically, "/A('b')/C" works but not "/C?$filter=foo eq 'b'". In order to have that, we've enabled the joins support on the ODataTranslator, but we still haven't the right query generated. We've traced back the origin to the optimizer:
* SELECT * FROM a join b ON a.x=b.y WHERE a.x='v'
* is optimized as SELECT <columns> FROM a join b ON a.x=b.y WHERE a.x='v' AND b.y='v'
The extra induced condition "b.y = 'v'" messes up with the URL construction. Any idea about how to proceed from there?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months
[JBoss JIRA] (TEIID-4578) Create SqlAlchemy Dialect for Teiid
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4578?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4578:
---------------------------------------
The sqlalchemy wrapper is just adjusting the version detection. If we move past that issue for now, then there are issues depending upon what functionality of sqlalchemy is accessed. Here's a list of methods with missing server side functionality:
has_table
-pg_table_is_visible
has_type
-pg_type_is_visible
get_foreign_keys
-pg_get_constraintdef
_load_domains
-format_type
With that, most of the usage that I can see would then be error free - but of course sequences and other concepts that we don't directly support won't work.
> Create SqlAlchemy Dialect for Teiid
> -----------------------------------
>
> Key: TEIID-4578
> URL: https://issues.jboss.org/browse/TEIID-4578
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors, Tooling
> Affects Versions: 9.1.1
> Reporter: Salvatore Incandela
> Assignee: Steven Hawkins
> Fix For: Open To Community, 9.3
>
>
> Create SqlAlchemy Dialect for Teiid
> http://www.sqlalchemy.org/
> http://docs.sqlalchemy.org/en/latest/dialects/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 10 months