[JBoss JIRA] (TEIID-2955) Teiid selects incorrect source when conformed table is included in SQL JOIN
by Filip Elias (JIRA)
Filip Elias created TEIID-2955:
----------------------------------
Summary: Teiid selects incorrect source when conformed table is included in SQL JOIN
Key: TEIID-2955
URL: https://issues.jboss.org/browse/TEIID-2955
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.7
Environment: teiid 8.7
Reporter: Filip Elias
Assignee: Steven Hawkins
I have two models. postgres for PostgreSQL and mysql for MySQL. I have table test.conformedTable in the both models
and I have configured conformedTable to be conformed. Table tablepostgre is in the PostgreSQL database. Table tablemysql in the MySQL.
I want to join conformedTable with tablepostgre and tablemysql.
The query
select a.*,b.* from mysql.test.conformedTable as a, tablemysql b where a.id=b.id
is processed OK, but query
select a.*,b.* from mysql.test.conformedTable as a, tablepostgre b where a.id=b.id throws an exception (in the attachment)
It seems that teiid searches tablepostgre in the mysql database, but the table is in the postgresql
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2917) Cassandra: update to cassandra driver to version 2.X
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2917?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2917:
---------------------------------------
With guava being an eap dependency I'll take the approach of packaging it for now, then we can reconcile it later.
> Cassandra: update to cassandra driver to version 2.X
> -----------------------------------------------------
>
> Key: TEIID-2917
> URL: https://issues.jboss.org/browse/TEIID-2917
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: Teiid with Cassandra
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.8
>
>
> The current cassandra driver is 2.X and API has been changed in this new driver. However, Teiid is using Cassandra driver 1.0.4. It will be nice if you guys can upgrade your cassandra driver version 2.X in the next release. Thanks.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2954) support older designer metadata for ws translator invoke
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2954:
-------------------------------------
Summary: support older designer metadata for ws translator invoke
Key: TEIID-2954
URL: https://issues.jboss.org/browse/TEIID-2954
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
Desinger modeled the invoke procedure with the result as an out parameter rather than a return, which was not accounted for with TEIID-2268
The workaround is to modify the invoke procedure metadata so that the result is a return parameter.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2848) MongoDB: Provide Array support
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2848?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2848:
-------------------------------------
Ivan, I do not think that kind of array can be properly represented through metadata in Teiid, so I would say it is not possible. If you have any suggestions please let us know.
> MongoDB: Provide Array support
> -------------------------------
>
> Key: TEIID-2848
> URL: https://issues.jboss.org/browse/TEIID-2848
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> Provide array support for primitive data types in MongoDB translator. The arrays are supported but as embedded documents in the one-2-many situation.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2848) MongoDB: Provide Array support
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-2848?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-2848:
----------------------------------
Would it be possible to support following json sample:
{ "_id": { "$oid" : "52e954dd62db0d0037000004" },
"name": "Frank Fontaine",
"array": [ "String", 6, true, "01/29/2014 16:37 -08:00", 99 ],
"num": "four" }
> MongoDB: Provide Array support
> -------------------------------
>
> Key: TEIID-2848
> URL: https://issues.jboss.org/browse/TEIID-2848
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
>
> Provide array support for primitive data types in MongoDB translator. The arrays are supported but as embedded documents in the one-2-many situation.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2917) Cassandra: update to cassandra driver to version 2.X
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2917?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2917:
---------------------------------------
This seems to clean up a lot of cassandra dependencies, but requires a later version of guava (16.0.1 is referenced by their pom). So we can either recommend changing the AS guava to 16.0.1 or we'll have to package it.
> Cassandra: update to cassandra driver to version 2.X
> -----------------------------------------------------
>
> Key: TEIID-2917
> URL: https://issues.jboss.org/browse/TEIID-2917
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.7
> Environment: Teiid with Cassandra
> Reporter: Ivan Chan
> Assignee: Steven Hawkins
> Labels: teiid
> Fix For: 8.8
>
>
> The current cassandra driver is 2.X and API has been changed in this new driver. However, Teiid is using Cassandra driver 1.0.4. It will be nice if you guys can upgrade your cassandra driver version 2.X in the next release. Thanks.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2929?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2929.
-----------------------------------
Resolution: Done
updated the odbc and vdb documentation to mention the usage of these properties.
> Provide ability define "execution properties" as VDB properties
> ---------------------------------------------------------------
>
> Key: TEIID-2929
> URL: https://issues.jboss.org/browse/TEIID-2929
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method.
> However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties.
> This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months