May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2955) Teiid selects incorrect source when conformed table is included in SQL JOIN

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2955?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2955. ----------------------------------- Fix Version/s: 8.7.1 8.8 Resolution: Done Updated the logic to handle setting the conformed tables appropriately regardless of the direction of the join. > 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 > Fix For: 8.7.1, 8.8 > > Attachments: server.log > > > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2958) MongoDB: Put nested JSON documents in one single table

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2958: -------------------------------- Summary: MongoDB: Put nested JSON documents in one single table Key: TEIID-2958 URL: https://issues.jboss.org/browse/TEIID-2958 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.7 Environment: MongoDB with Teiid Reporter: Ivan Chan Assignee: Steven Hawkins Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work. I am thinking the following case. For example I have a JSON object like this: Customer { _id: 1374932, FirstName: "John", LastName: "Doe", Address: { _id: 43839430, Street: "123 Lane", City: "New York", State: "NY", Zipcode: "12345" } } In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema: CREATE FOREIGN TABLE Customer ( CustomerId integer PRIMARY KEY, FirstName varchar(25), LastName varchar(25), address__id integer, address_Street varchar(50), address_City varchar(25), address_State varchar(25), address_Zipcode varchar(6), ) OPTIONS(UPDATABLE 'TRUE'); -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2937. --------------------------------- Resolution: Done CR8 has 3.10-FINAL, so it is updated in 8.7.1 now. > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[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: ------------------------------------- (1) is the way that Steve proposed. Once (1) is available, user can use OBJECTTABLE construct to build (2). It will not be automatically provided by Teiid. > 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

1
0
0 / 0

[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 edited comment on TEIID-2848 at 5/13/14 3:16 PM: -------------------------------------------------------------- (1) is the way that Steve proposed. Once (1) is available, user can use ARRAYTABLE construct to build (2). It will not be automatically provided by Teiid. was (Author: rareddy): (1) is the way that Steve proposed. Once (1) is available, user can use OBJECTTABLE construct to build (2). It will not be automatically provided by Teiid. > 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

1
0
0 / 0

[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: --------------------------------------- There would need to be a product driver to put it there and it has a dependency conflict with EAP. So it's not valid for 8.7.x at this time. > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2956) NullPointerException using webservice translator against a webservice that's missing 'Content-Type' in the response header

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2956?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2956. ----------------------------------- Fix Version/s: 8.7.1 8.8 Resolution: Done We'll use a content-type of application/octet-stream (the recommended default) if the content-type is not in the metadata. Since this is an optionally used value already it doesn't seem necessary to add another parameter. > NullPointerException using webservice translator against a webservice that's missing 'Content-Type' in the response header > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2956 > URL: https://issues.jboss.org/browse/TEIID-2956 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: windows 7, teiid 8.7 > Reporter: gaurav singhal > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > If you deploy a vdb that uses the webservices translator in teiid 8.7, and that webservice doesn't have 'Content-Type' set in the response headers then the web service connector code throws a NullPointerException as it tries to retrieve the Content-Type and use it. This happens in the WSConnectionImpl.java class on these 2 lines specifically: > ArrayList contentTypes = (ArrayList)this.responseContext.get("content-type"); //$NON-NLS-1$ > return new HttpDataSource(url, (InputStream)response.getEntity(), (String)contentTypes.get(0)); > so basically the contentTypes array is null if the response header doesn't containt any 'Content-Type' specified and then 2nd line gets the NullPointerException. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2917) Cassandra: update to cassandra driver to version 2.X

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-2917?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-2917: ---------------------------------- Would you guys consider to put it in 8.7.1? > 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

1
0
0 / 0

[JBoss JIRA] (TEIID-2917) Cassandra: update to cassandra driver to version 2.X

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-2917?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-2917: ---------------------------------- Thanks! > 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

1
0
0 / 0

[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: ---------------------------------- Yes, Object[] is a good solution. And maybe you guys can also consider to provide 2 different ways to handle mongoDB array object. 1. map mongoDB array to java object array 2. flatten the data to create separate column for each array element (similar to unwind): >From the example above: CREATE FOREIGN TABLE Sample ( CustomerId integer PRIMARY KEY, name varchar(25), array_0 varchar(25), array_1 integer, array_2, timestamp, array_3, integer, num varchar(6), ) OPTIONS(UPDATABLE 'TRUE'); > 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2014