October 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1773) Ingres as source - Query with LOCATE causing stackoverflow error

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1773?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3455 to TEIID-1773: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1773 (was: SOA-3455) Affects Version/s: 7.4.1 (was: 5.2.0.ER4) Component/s: Misc. Connectors (was: EDS) Security: (was: Public) > Ingres as source - Query with LOCATE causing stackoverflow error > ---------------------------------------------------------------- > > Key: TEIID-1773 > URL: https://issues.jboss.org/browse/TEIID-1773 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Van Halbert > > EDS Query Testing is getting unexpected results on 16 queries involving LOCATE. A couple examples queries are given below: > SELECT INTKEY, LOCATE(1, STRINGNUM) FROM BQT1.SmallA ORDER BY intkey (Expected 50 records but received only 0) > Remote org.teiid.core.TeiidProcessingException: Source: null > see stackoverflow.log attached > SELECT INTKEY FROM BQT1.SmallA WHERE LOCATE(1, INTKEY) = 1 ORDER BY INTKEY > Remote org.teiid.core.TeiidProcessingException: Source: null > Is also a stackoverflow error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1773) Ingres as source - Query with LOCATE causing stackoverflow error

by Van Halbert (Assigned) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1773?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-1773: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Ingres as source - Query with LOCATE causing stackoverflow error > ---------------------------------------------------------------- > > Key: TEIID-1773 > URL: https://issues.jboss.org/browse/TEIID-1773 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > > EDS Query Testing is getting unexpected results on 16 queries involving LOCATE. A couple examples queries are given below: > SELECT INTKEY, LOCATE(1, STRINGNUM) FROM BQT1.SmallA ORDER BY intkey (Expected 50 records but received only 0) > Remote org.teiid.core.TeiidProcessingException: Source: null > see stackoverflow.log attached > SELECT INTKEY FROM BQT1.SmallA WHERE LOCATE(1, INTKEY) = 1 ORDER BY INTKEY > Remote org.teiid.core.TeiidProcessingException: Source: null > Is also a stackoverflow error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1772) Teiid ports need to have the ability to restrict cipher suites

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1772?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1772: --------------------------------------- Cipher suite negotiation selects the highest precedence (see http://download.oracle.com/javase/6/docs/technotes/guides/security/SunPro... for the supported suites in Oracle Java) mutually supported suite. So modifying the client isn't really necessary as long as the server is restricted. This issue is more to ensure compliance with security policy since all VMs by default support the 128 bit or triple des encryption used by the default enabled cipher suites. You would have attempt a connection with a client that only supports weak encryption to get a weakly encrypted channel. This enhancement would allow us to reject those connections. The workaround is to ensure that clients must support one of the server's enabled strong cipher suites. > Teiid ports need to have the ability to restrict cipher suites > -------------------------------------------------------------- > > Key: TEIID-1772 > URL: https://issues.jboss.org/browse/TEIID-1772 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Van Halbert > > When using either 1-way or 2-way ssl for the EDS/Teiid connections, there is currently no way to restrict connections to 128 bit cipher suites. The capability needs to be added to the product. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1772) Teiid ports need to have the ability to restrict cipher suites

by Van Halbert (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1772?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-1772: ------------------------------------ As to the scope of the fix in Teiid, how broad is the fix? would you consider it invasive or pretty simple, or somewhere in between? Just thinking that this could impact the client and the server side of the code. > Teiid ports need to have the ability to restrict cipher suites > -------------------------------------------------------------- > > Key: TEIID-1772 > URL: https://issues.jboss.org/browse/TEIID-1772 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Van Halbert > > When using either 1-way or 2-way ssl for the EDS/Teiid connections, there is currently no way to restrict connections to 128 bit cipher suites. The capability needs to be added to the product. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1772) Teiid ports need to have the ability to restrict cipher suites

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1772?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-3449 to TEIID-1772: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1772 (was: SOA-3449) Affects Version/s: (was: 5.1.0 GA) Component/s: Server (was: EDS) Security: (was: Public) > Teiid ports need to have the ability to restrict cipher suites > -------------------------------------------------------------- > > Key: TEIID-1772 > URL: https://issues.jboss.org/browse/TEIID-1772 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Debbie Steigner > Assignee: Van Halbert > > When using either 1-way or 2-way ssl for the EDS/Teiid connections, there is currently no way to restrict connections to 128 bit cipher suites. The capability needs to be added to the product. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1772) Teiid ports need to have the ability to restrict cipher suites

by Van Halbert (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1772?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-1772: ------------------------------- Affects Version/s: 7.1.1 > Teiid ports need to have the ability to restrict cipher suites > -------------------------------------------------------------- > > Key: TEIID-1772 > URL: https://issues.jboss.org/browse/TEIID-1772 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Van Halbert > > When using either 1-way or 2-way ssl for the EDS/Teiid connections, there is currently no way to restrict connections to 128 bit cipher suites. The capability needs to be added to the product. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1770) Set Query Timeout at the VDB level

by Van Halbert (Created) (JIRA)

Set Query Timeout at the VDB level ---------------------------------- Key: TEIID-1770 URL: https://issues.jboss.org/browse/TEIID-1770 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 7.3 Environment: Windows Reporter: RAKESH BALGURI Assignee: Steven Hawkins Fix For: 7.6 Hi, We want the configuration of the Query Timeout set on the server side instead of setting it for the Statement Object. Please see this discussion for more information http://community.jboss.org/message/600599#600599 We want the setQueryTimeout to override the default values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1766) EDS ODBC query on a namespace ending in 'e' fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1766?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1766. ----------------------------------- Resolution: Out of Date This was resolved in Teiid 7.4 by adding direct parsing support for pg escaped literals. In 7.1 the issue is caused in ODBCServerRemoteImpl by line 354: modified = modified.replaceAll("E'", "'"); //$NON-NLS-1$ //$NON-NLS-2$ Which is far too generic. ODBCServerRemoteImpl version 3045 contained a fix and related fixes. The specific change would be: modified = modified.replaceAll("E('[^']*')+", "$1"); //$NON-NLS-1$ //$NON-NLS-2$ > EDS ODBC query on a namespace ending in 'e' fails > ------------------------------------------------- > > Key: TEIID-1766 > URL: https://issues.jboss.org/browse/TEIID-1766 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Attachments: Testing.vdb > > > The attached testing vdb contains the following namespaces: > LOOKHERE TestPG LOOKAGAIN > If you run the following query via ODBC (JDBC works ): > select nspname from pg_catalog.pg_namespace where nspname = 'LOOKHERE' > It returns zero rows, but if you run the same query with 'LOOKAGAIN' in your criteria you get the one row, It seems that any namespace ending in an E doesn't match via ODBC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-1763) EDS inner join returns no data, left join does

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1763?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1763. ----------------------------------- Resolution: Out of Date Already resolved. This placeholder JIRA is not needed by GSS. > EDS inner join returns no data, left join does > ----------------------------------------------- > > Key: TEIID-1763 > URL: https://issues.jboss.org/browse/TEIID-1763 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 7.1.1 > > > We've encountered a rather concerning case of the wrong data (no data) being returned on a federated query. We're pretty sure it should return data, and when we change an inner join to a left join it does return the data we expect (complete data, with a value for the column being left joined rather than a null). > This issue has been tested on 5.2 ER3 and is fixed, but the customer needs a CP for the 5.1 release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1767) Hibernate Month Date Extraction

by Johnathon Lee (JIRA)

Hibernate Month Date Extraction ------------------------------- Key: TEIID-1767 URL: https://issues.jboss.org/browse/TEIID-1767 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Reporter: Johnathon Lee Assignee: Steven Hawkins Fix For: 7.4.1, 7.6 When using teiid-hibernate-dialect-7.1.1.GA, the TeiidDialect does not include a function to get the month value of a date object. It includes functions to get other date attributes (year, dayofmonth etc). Without a defined function, attempting to get a month value falls back on the hibernate-core function which attempts to utilize an extract method which is not supported in 7.1.1. Example Query: select d from Data d where month(d.date)='09' HQL Generated: select data0_.Id as Id25_, data0_.DataAmt as DataAmt25_, data0_.Data as Data25_, from Data data0_ where extract(month from data0_.date)='09' Being able to obtain a month value from a date is a critical requirement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2011