October 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3177) Enforce SSL connections over ODBC when Encryption Mode is enabled

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3177?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3177 at 10/22/14 9:49 AM: ----------------------------------------------------------------- Note that this is the default behavior of a pg server as well (with the distinction that other auth types such as a hash would be supported). You have to additionally configure the hba conf to deny non-ssl client connections - which is what this feature will be analogous to. Also note that http://www.postgresql.org/docs/9.2/static/libpq-ssl.html states that clients must be configured for ssl - see sslmode or else the client can still send information in an non-secure fashion even if the server is in ssl mode regardless of whether it is rejecting connections (this may be because there are versions of the pg client that can send password information in the initialization message or not waiting for the authentication mode response from the server). was (Author: shawkins): Note that this is the default behavior of a pg server as well. You have to additionally configure the hba conf to deny non-ssl client connections - which is what this feature will be analogous to. Also note that http://www.postgresql.org/docs/9.2/static/libpq-ssl.html states that clients must be configured for ssl - see sslmode or else the client can still send information in an non-secure fashion even if the server is in ssl mode regardless of whether it is rejecting connections (this may be because there are versions of the pg client that can send password information in the initialization message or not waiting for the authentication mode response from the server). > Enforce SSL connections over ODBC when Encryption Mode is enabled > ----------------------------------------------------------------- > > Key: TEIID-3177 > URL: https://issues.jboss.org/browse/TEIID-3177 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Affects Versions: 8.8 > Reporter: Cristiano Nicolai > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.9 > > > When connecting via ODBC transport, even if the encryption mode is set to enabled is still possible to establish non ssl connections. This allows clients to connect via insecure method. We would like that the Teiid transport could reject connections if they are not properly set up using SSL transport. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3183) Join sort order altered inappropriately

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3183?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3183. ----------------------------------- Resolution: Done Updated the logic to check to see if a sort order is already defined. A potential enhancement moving forward would be to check the parent join and see if an enhanced sort could be used. This would require forcing using the subquery as the sorted index and updating the join logic to understand semi join and anti-semi join. This would allow the sort order to be persevered. > Join sort order altered inappropriately > --------------------------------------- > > Key: TEIID-3183 > URL: https://issues.jboss.org/browse/TEIID-3183 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1, 8.9 > > > If a merge or other join configuration is chosen and there is a subquery affecting only a side of the join that is to be sorted such that the subquery can be rewritten as a semi/anti-semi join, then the subquery rewrite will alter the intended sort order of the original join. This can result in incorrect results. > An example query: > select pm2.g2.e1 from pm1.g1 inner join pm2.g2 on (pm1.g1.e1 = pm2.g2.e1) where pm2.g2.e2 in /*+ mj */ (select count(e2) FROM pm1.g2 group by e1 having e1 < pm2.g2.e3) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3183) Join sort order altered inappropriately

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3183?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3183: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1155599 > Join sort order altered inappropriately > --------------------------------------- > > Key: TEIID-3183 > URL: https://issues.jboss.org/browse/TEIID-3183 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1, 8.9 > > > If a merge or other join configuration is chosen and there is a subquery affecting only a side of the join that is to be sorted such that the subquery can be rewritten as a semi/anti-semi join, then the subquery rewrite will alter the intended sort order of the original join. This can result in incorrect results. > An example query: > select pm2.g2.e1 from pm1.g1 inner join pm2.g2 on (pm1.g1.e1 = pm2.g2.e1) where pm2.g2.e2 in /*+ mj */ (select count(e2) FROM pm1.g2 group by e1 having e1 < pm2.g2.e3) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3059) Support consuming SOAP based service that is secured by Kerberos authentication

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3059?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3059: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1155299|https://bugzilla.redhat.com/show_bug.cgi?id=1155299] from NEW to ASSIGNED > Support consuming SOAP based service that is secured by Kerberos authentication > ------------------------------------------------------------------------------- > > Key: TEIID-3059 > URL: https://issues.jboss.org/browse/TEIID-3059 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.9 > > > CXF supports Kerberos based authentication in issuing a SOAP based web service call. This needs to be verified authentication scenario and further enhance code to support delegation of kerberos token. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3059) Support consuming SOAP based service that is secured by Kerberos authentication

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3059?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3059: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1155299 > Support consuming SOAP based service that is secured by Kerberos authentication > ------------------------------------------------------------------------------- > > Key: TEIID-3059 > URL: https://issues.jboss.org/browse/TEIID-3059 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.9 > > > CXF supports Kerberos based authentication in issuing a SOAP based web service call. This needs to be verified authentication scenario and further enhance code to support delegation of kerberos token. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3183) Join sort order altered inappropriately

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3183: ------------------------------------- Summary: Join sort order altered inappropriately Key: TEIID-3183 URL: https://issues.jboss.org/browse/TEIID-3183 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.7.1, 8.9 If a merge or other join configuration is chosen and there is a subquery affecting only a side of the join that is to be sorted such that the subquery can be rewritten as a semi/anti-semi join, then the subquery rewrite will alter the intended sort order of the original join. This can result in incorrect results. An example query: select pm2.g2.e1 from pm1.g1 inner join pm2.g2 on (pm1.g1.e1 = pm2.g2.e1) where pm2.g2.e2 in /*+ mj */ (select count(e2) FROM pm1.g2 group by e1 having e1 < pm2.g2.e3) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3059) Support consuming SOAP based service that is secured by Kerberos authentication

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3059?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3059: -------------------------------- Fix Version/s: 8.7.1 8.9 > Support consuming SOAP based service that is secured by Kerberos authentication > ------------------------------------------------------------------------------- > > Key: TEIID-3059 > URL: https://issues.jboss.org/browse/TEIID-3059 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.9 > > > CXF supports Kerberos based authentication in issuing a SOAP based web service call. This needs to be verified authentication scenario and further enhance code to support delegation of kerberos token. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-2973) Switch OData support to Olingo

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2973?page=com.atlassian.jira.plugin... ] Work on TEIID-2973 started by Ramesh Reddy. ------------------------------------------- > Switch OData support to Olingo > ------------------------------ > > Key: TEIID-2973 > URL: https://issues.jboss.org/browse/TEIID-2973 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors, OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.9 > > > Whenever an olingo final is available for odata 3/4 we'll want to switch our support to utilize that. The best guess now is that this will happen in the 8.9 timeframe. Additional support can then be added for later odata features, which will have subtasks as necessary. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3166: -------------------------------- Fix Version/s: 8.9 Component/s: Misc. Connectors > Allow allowDiskUse setting in MongoDB translator > ------------------------------------------------ > > Key: TEIID-3166 > URL: https://issues.jboss.org/browse/TEIID-3166 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Harrison Gentry > Assignee: Ramesh Reddy > Priority: Minor > Labels: CR1 > Fix For: 8.9 > > > When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: > http://docs.mongodb.org/manual/reference/command/aggregate/ > In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3166) Allow allowDiskUse setting in MongoDB translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3166?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3166. --------------------------------- Labels: CR1 (was: ) Resolution: Done Forgot to turn this as resolved. Fixed in 8.9 CR1 > Allow allowDiskUse setting in MongoDB translator > ------------------------------------------------ > > Key: TEIID-3166 > URL: https://issues.jboss.org/browse/TEIID-3166 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Harrison Gentry > Assignee: Ramesh Reddy > Priority: Minor > Labels: CR1 > Fix For: 8.9 > > > When querying a MongoDB, steps of computation are limited to 100MiB. Querying large databases can easily exceed this limit, so usually allowDiskUse:true is passed in the aggregate query: > http://docs.mongodb.org/manual/reference/command/aggregate/ > In Teiid, however, there is currently no way to specify this with SQL. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014