February 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2841) MongoDB: Wrong results returned with MERGE in ONE-1-ONE relation

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2841: ----------------------------------- Summary: MongoDB: Wrong results returned with MERGE in ONE-1-ONE relation Key: TEIID-2841 URL: https://issues.jboss.org/browse/TEIID-2841 Project: Teiid Issue Type: Bug Affects Versions: 8.4 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7 If Schema is like {code} CREATE FOREIGN TABLE Customer ( CustomerId integer PRIMARY KEY, FirstName varchar(25), LastName varchar(25) ) OPTIONS(UPDATABLE 'TRUE'); CREATE FOREIGN TABLE Address ( CustomerId integer PRIMARY KEY, Street varchar(50), City varchar(25), State varchar(25), Zipcode varchar(6), FOREIGN KEY (CustomerId) REFERENCES Customer (CustomerId) ) OPTIONS(UPDATABLE 'TRUE', "teiid_mongo:MERGE" 'Customer'); {code} and we did inserts like {code} insert into Customer (customerId ,firstname,lastname) values ('1002','Syed','Iqbal'); insert into Address (customerId,street,city,state,zipcode) values ('1002','123 Main St','Chicago','IL','60659'); insert into Customer (customerId ,firstname,lastname) values ('1000','Ramesh','Reddy'); {code} the data in mongo is in form {code} { "Address" : { "Street" : "123 Main St", "City" : "Chicago", "State" : "IL", "Zipcode" : "60659", "_id" : DBRef("Customer", 1002) }, "FirstName" : "Syed", "LastName" : "Iqbal", "Notes" : [ ], "_id" : 1002 } { "_id" : 1000, "FirstName" : "Ramesh", "LastName" : "Reddy" } {code} and if you issue {code} SELECT * FROM Address {code} you will see ||CustomerId||Street||City||State|| |1002|123 Main St|Chicago|IL| |<null>|<null>|<null>|<null>| -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2839) Selection of nested document based on non primary key does not work on MongoDB Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2839?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2839: ------------------------------------- This only applicable in MERGE case as EMBEDDABLE scenario the data is stored in top level collection as well as nested document. But the selection happens on top level document. Testing the same in JOIN scenario is another usecase needs validating. > Selection of nested document based on non primary key does not work on MongoDB Translator > ----------------------------------------------------------------------------------------- > > Key: TEIID-2839 > URL: https://issues.jboss.org/browse/TEIID-2839 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7 > > > When a table is either EMBEDDED or MERGED into a parent table, issuing a "SELECT" query using WHERE clause that uses a NON primary key results in empty result. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2840) TTL Snapshot Refresh may need to be a blocking load

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2840?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2840: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1061803 > TTL Snapshot Refresh may need to be a blocking load > --------------------------------------------------- > > Key: TEIID-2840 > URL: https://issues.jboss.org/browse/TEIID-2840 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > > An asynch load may happen under a current request and when that request/session is closed, then the asynch load is killed. > The ttl load to may need to be changed to a blocking load or some configuration options provided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2840) TTL Snapshot Refresh may need to be a blocking load

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2840: ------------------------------------ Summary: TTL Snapshot Refresh may need to be a blocking load Key: TEIID-2840 URL: https://issues.jboss.org/browse/TEIID-2840 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.7.8 Reporter: Johnathon Lee Assignee: Steven Hawkins An asynch load may happen under a current request and when that request/session is closed, then the asynch load is killed. The ttl load to may need to be changed to a blocking load or some configuration options provided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2839) Selection of nested document based on non primary key does not work on MongoDB Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2839?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2839: -------------------------------- Summary: Selection of nested document based on non primary key does not work on MongoDB Translator (was: Selection of nested document based on non primary key does not work.) > Selection of nested document based on non primary key does not work on MongoDB Translator > ----------------------------------------------------------------------------------------- > > Key: TEIID-2839 > URL: https://issues.jboss.org/browse/TEIID-2839 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7 > > > When a table is either EMBEDDED or MERGED into a parent table, issuing a "SELECT" query using WHERE clause that uses a NON primary key results in empty result. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2839) Selection of nested document based on non primary key does not work.

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2839: ----------------------------------- Summary: Selection of nested document based on non primary key does not work. Key: TEIID-2839 URL: https://issues.jboss.org/browse/TEIID-2839 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.4 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7 When a table is either EMBEDDED or MERGED into a parent table, issuing a "SELECT" query using WHERE clause that uses a NON primary key results in empty result. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2804) Aggregate empty filter too broad and may inappropriately filter results

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2804?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2804: ---------------------------------- Fix Version/s: 8.4.2 > Aggregate empty filter too broad and may inappropriately filter results > ----------------------------------------------------------------------- > > Key: TEIID-2804 > URL: https://issues.jboss.org/browse/TEIID-2804 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.2, 8.7 > > > This is a regression from TEIID-2253 which consolidated logic in RulePushAggregates to handle multi-source planning. It also inappropriately expanded an empty test (which should only be applied to grouping without a group by) to some cases with group by clauses and in an attempt to broaden pushdown support utilized is not null tests. However the is not null tests are not generally valid as the aggregate could be computed against all null values for example. Depending upon this situations this could result in invalid filtering of results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2800) Teiid Login Issue with special characters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2800?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2800: ---------------------------------- Fix Version/s: 8.4.2 > Teiid Login Issue with special characters > ----------------------------------------- > > Key: TEIID-2800 > URL: https://issues.jboss.org/browse/TEIID-2800 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.1 > Environment: Mainframe Jboss 7.1.1 > Reporter: Gautam Banerjee > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4.2, 8.7 > > > When we try to login to teiid programmatically through datasource, we are having problem with username having special characters. > We are encoding the special character as per url encoding > eg : username %xyz is encoded as %25xyz but teiid does not decode the special character while passing username. So the username passed by teiid is %25xyz which fails authentication as the actual username is %xyz -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2766) OData large batch size does not allow all results to be returned to the client in a single batch

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2766?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2766: ---------------------------------- Fix Version/s: 8.4.2 > OData large batch size does not allow all results to be returned to the client in a single batch > ------------------------------------------------------------------------------------------------ > > Key: TEIID-2766 > URL: https://issues.jboss.org/browse/TEIID-2766 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Environment: OData client connecting to Teiid > Reporter: Marc Shirley > Assignee: Steven Hawkins > Labels: final > Fix For: 8.6, 8.4.2 > > > OData large batch-size, for example -1 to get all results in 1 response, doesn't work. Largest tested value that does work 51210. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2757) XML 1.0 invalid characters not supported in Odata Atom feed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2757: ---------------------------------- Fix Version/s: 8.4.2 > XML 1.0 invalid characters not supported in Odata Atom feed > ----------------------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7 > > Attachments: List of invalid XML characters.docx, TEIID-2757-Webservices-Stacktrace.txt > > > The odata framework sometimes has problems with transforming characters (invalid in XML 1.0) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2014