November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3717) Enable SNI (Server Name Indication) support

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3717?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3717: ------------------------------------ TLS vs SSL https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515%28v=vs.... > Enable SNI (Server Name Indication) support > ------------------------------------------- > > Key: TEIID-3717 > URL: https://issues.jboss.org/browse/TEIID-3717 > Project: Teiid > Issue Type: Feature Request > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12.2 > > > Enable SNI support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3375) Support Kerberos handshake for mutual auth

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3375?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3375: --------------------------------- Fix Version/s: 8.7.2.6_2 > Support Kerberos handshake for mutual auth > ------------------------------------------ > > Key: TEIID-3375 > URL: https://issues.jboss.org/browse/TEIID-3375 > Project: Teiid > Issue Type: Feature Request > Components: Embedded, ODBC > Affects Versions: 8.9.1 > Environment: Postgres JDBC 9.4-1201 client on Windows 7, Teiid server on either Windows 7 or RHEL Linux 2.6 (behaved same on both platforms). > Reporter: Ben Kibler > Assignee: Ramesh Reddy > Fix For: 8.11, 8.7.2.6_2 > > > When using Teiid Embedded with Kerberos, the GSS handshake with the Postgres JDBC client is failing while trying to establish mutual authentication. > The ODBCRemoteServerImpl.login() method should send both an AuthenticationGSSContinue and AuthenticationOk message when the client is requesting mutual authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3666: --------------------------------- Fix Version/s: 8.7.2.6_2 > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3, 8.7.2.6_2 > > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3666: ---------------------------------- > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3 > > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3564) float field gets converted to scientific notation when query is submitted to source

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3564?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3564. -------------------------------- Resolution: Done > float field gets converted to scientific notation when query is submitted to source > ----------------------------------------------------------------------------------- > > Key: TEIID-3564 > URL: https://issues.jboss.org/browse/TEIID-3564 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS Virtual Machine, salesforce.com soap api 23.0,JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Fix For: 8.7.2.6_2, 8.11.5, 8.12 > > > When submitting the following query: > SELECT COUNT(*) FROM salesforce_sales.salesforce.Opportunity where amount > 100000000; > to a salesforce instance with the shown filter it returns the following error: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 SalesForce_Sales: com.sforce.soap.partner.MalformedQueryFault: MALFORMED_QUERY: > Opportunity WHERE Opportunity.Amount > 1.0E8 > ^ > ERROR at Row:1:Column:64 > unexpected token: 'E8' > Elapsed Time: 0 hr, 0 min, 1 sec, 109 ms. > why is the quantity modified when the field is declared as float? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3658) VDBs may start before transport service

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3658: ---------------------------------- > VDBs may start before transport service > --------------------------------------- > > Key: TEIID-3658 > URL: https://issues.jboss.org/browse/TEIID-3658 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Critical > Labels: Beta2 > Fix For: 8.12, 8.7.5 > > > VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3658) VDBs may start before transport service

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3658: --------------------------------- Fix Version/s: 8.7.2.6_2 > VDBs may start before transport service > --------------------------------------- > > Key: TEIID-3658 > URL: https://issues.jboss.org/browse/TEIID-3658 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Critical > Labels: Beta2 > Fix For: 8.12, 8.7.5, 8.7.2.6_2 > > > VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3658) VDBs may start before transport service

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3658. -------------------------------- Resolution: Done > VDBs may start before transport service > --------------------------------------- > > Key: TEIID-3658 > URL: https://issues.jboss.org/browse/TEIID-3658 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Critical > Labels: Beta2 > Fix For: 8.7.5, 8.7.2.6_2, 8.12 > > > VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3564) float field gets converted to scientific notation when query is submitted to source

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3564?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3564: ---------------------------------- > float field gets converted to scientific notation when query is submitted to source > ----------------------------------------------------------------------------------- > > Key: TEIID-3564 > URL: https://issues.jboss.org/browse/TEIID-3564 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS Virtual Machine, salesforce.com soap api 23.0,JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.5 > > > When submitting the following query: > SELECT COUNT(*) FROM salesforce_sales.salesforce.Opportunity where amount > 100000000; > to a salesforce instance with the shown filter it returns the following error: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 SalesForce_Sales: com.sforce.soap.partner.MalformedQueryFault: MALFORMED_QUERY: > Opportunity WHERE Opportunity.Amount > 1.0E8 > ^ > ERROR at Row:1:Column:64 > unexpected token: 'E8' > Elapsed Time: 0 hr, 0 min, 1 sec, 109 ms. > why is the quantity modified when the field is declared as float? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3564) float field gets converted to scientific notation when query is submitted to source

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3564?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3564: --------------------------------- Fix Version/s: 8.7.2.6_2 > float field gets converted to scientific notation when query is submitted to source > ----------------------------------------------------------------------------------- > > Key: TEIID-3564 > URL: https://issues.jboss.org/browse/TEIID-3564 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: RHEL 6, AWS Virtual Machine, salesforce.com soap api 23.0,JBoss EAP (standalone) 6.3.2.GA > JBoss Data Virtualization 6.1.0.ER4 > Reporter: Jorge Herrera > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.5, 8.7.2.6_2 > > > When submitting the following query: > SELECT COUNT(*) FROM salesforce_sales.salesforce.Opportunity where amount > 100000000; > to a salesforce instance with the shown filter it returns the following error: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 SalesForce_Sales: com.sforce.soap.partner.MalformedQueryFault: MALFORMED_QUERY: > Opportunity WHERE Opportunity.Amount > 1.0E8 > ^ > ERROR at Row:1:Column:64 > unexpected token: 'E8' > Elapsed Time: 0 hr, 0 min, 1 sec, 109 ms. > why is the quantity modified when the field is declared as float? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2015