March 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3732) Enable Infinispan-cache translator to negate intNum <> 1 returning true when column is null

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3732?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3732: --------------------------------------- Google spreadsheets had a similar issue. It affected even ordered comparisons there since null was treated as a low value, so that may need to be checked here. Since Teiid does normalize / flatten the predicates prior to pushdown, this is valid workaround. > Enable Infinispan-cache translator to negate intNum <> 1 returning true when column is null > -------------------------------------------------------------------------------------------- > > Key: TEIID-3732 > URL: https://issues.jboss.org/browse/TEIID-3732 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Reporter: Van Halbert > Assignee: Van Halbert > > This is related to TEIID-3573. To add a support option so that when the translator sees criteria like intNum<>1 it would need to produce "intNum<>1 and intNum IS NOT NULL". > This would negate the issue in JDG where it resolves intNum <> 1 to true when the column is null. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2768) XML 1.0 invalid characters not supported in web services

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2768?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2768. ----------------------------------- Resolution: Won't Fix This is handled automatically in the auto generated odata/rest routes. It will need to be handled by the user in any other paths where they are explicitly constructing the xml. > XML 1.0 invalid characters not supported in web services > -------------------------------------------------------- > > Key: TEIID-2768 > URL: https://issues.jboss.org/browse/TEIID-2768 > Project: Teiid > Issue Type: Enhancement > Components: SOAP Services > Affects Versions: 8.4, 8.5 > Reporter: Patrick Deenen > Priority: Minor > > This issue is comparable to TEIID-2757. > The Web service 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: com.ctc.wstx.exc.WstxParsingException: Illegal character entity: expansion character (code 0x1b > at [row,col {unknown-source}]: [11,144589]. See for the complete stacktrace: > https://issues.jboss.org/secure/attachment/12379354/TEIID-2757-Webservice... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2947) Implement ODBC cancel

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2947?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2947: ---------------------------------- Fix Version/s: Open To Community > Implement ODBC cancel > --------------------- > > Key: TEIID-2947 > URL: https://issues.jboss.org/browse/TEIID-2947 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Reporter: Steven Hawkins > Fix For: Open To Community > > > The ODBC cancel logic would take sending a different set of backend key data and recognizing a different set of initial message flow (as the cancel is issued in a separate connection). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2894) Add support for the row lock query(SELECT FOR UPDATE) to the source database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2894?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2894: ---------------------------------- Fix Version/s: 10.0 > Add support for the row lock query(SELECT FOR UPDATE) to the source database > ---------------------------------------------------------------------------- > > Key: TEIID-2894 > URL: https://issues.jboss.org/browse/TEIID-2894 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 10.0 > > > We need support for the row lock query(SELECT FOR UPDATE) in teiid query engine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2711) Better support for Oracle SQLXML values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2711?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2711: ---------------------------------- Fix Version/s: 9.3 > Better support for Oracle SQLXML values > --------------------------------------- > > Key: TEIID-2711 > URL: https://issues.jboss.org/browse/TEIID-2711 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > Attachments: oracle.patch > > > When using a typical driver configuration to read oracle xml values, the driver will return an OPAQUE instance rather than a SQLXML value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2542) Utilize Teiid internal resultset buffering as a materialization mechanism to Infinspan

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2542?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2542: ---------------------------------- Fix Version/s: 10.0 We should be able to assess this further for 10.0. As the previous comment highlights there are a lot of issues with doing this integration at a low level. Instead we'd like to approach it at an entity level, but there are class loading and other issues that remain. > Utilize Teiid internal resultset buffering as a materialization mechanism to Infinspan > -------------------------------------------------------------------------------------- > > Key: TEIID-2542 > URL: https://issues.jboss.org/browse/TEIID-2542 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: 10.0 > > > Add support for materialization to Infinispan by utilizing the Teiid internal buffering mechanism to Infinispan. Suggestion, turn that mechanism into a translator that can read/write to Infinispan. > Pro's: > - distributed data-grid fail-over and HA could be less costly than trying to do this with a database. > - improved performance where each Infinispan instance could placed closer to its' users. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2819) Use Oauth SAML Bearer Assertion Flow

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2819?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2819: --------------------------------------- [~rareddy] can this be resolved? > Use Oauth SAML Bearer Assertion Flow > ------------------------------------ > > Key: TEIID-2819 > URL: https://issues.jboss.org/browse/TEIID-2819 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > > I can secure my mobile and cloud applications? > Consider doing SAML first and Oauth later – the use cases are the same, the implementation is different > Link - https://help.salesforce.com/apex/HTViewHelpDoc?id=remoteaccess_oauth_SAML... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2465) Add additional size limitations

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2465?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2465: ---------------------------------- Fix Version/s: 9.3 > Add additional size limitations > ------------------------------- > > Key: TEIID-2465 > URL: https://issues.jboss.org/browse/TEIID-2465 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > We should introduce a limit to lob (which is currently only correct for up to 2 gigs) and single tuplebuffer results in storage as to prevent too much resource consumption from a single use. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2167) Permissions should also specify object type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2167?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2167: ---------------------------------- Fix Version/s: 9.3 Now that we have this support in DDL it will be good to at least add the information to the xml/runtime format for round tripping purposes. It would still be optional though in the vdb.xml > Permissions should also specify object type > ------------------------------------------- > > Key: TEIID-2167 > URL: https://issues.jboss.org/browse/TEIID-2167 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > Teiid permissions only specify a resource name. However it is possible to have to have conflicting schema/table (since we are using non-sql safe unquoted names) or table/procedure names. > Ideally we would use proper sql names (this is true everywhere, not just in permissions) and specify the object type (TABLE, PROCEDURE, SCHEMA, LANGUAGE, FUNCTION, etc.). This would also allow us to have a more standard USAGE permission, rather than something like LANGUAGE, which is used to convey the permission and object type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2123) Per model getMetadata() timeout

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2123?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2123: ---------------------------------- Component/s: Misc. Connectors > Per model getMetadata() timeout > ------------------------------- > > Key: TEIID-2123 > URL: https://issues.jboss.org/browse/TEIID-2123 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.0 > Reporter: Mark Addleman > Priority: Minor > Fix For: Open To Community > > > A way of specifying, per model, a timeout for the getMetadata() call. The timeout should be processed in such a way that delegating translators have an opportunity to intercept the interruption and, potentially, supply default metadata. I think the normal Thread.interrupt() approach should work. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2017