April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3359) Allow more control over odata layer caching

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3359?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3359: ------------------------------------- Looing into commit, I do not I need to do anything special to carry this over to the V4 version. I will carry forward the testcase. > Allow more control over odata layer caching > ------------------------------------------- > > Key: TEIID-3359 > URL: https://issues.jboss.org/browse/TEIID-3359 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.11 > > > The caching is always performed at a user level and for each query. Consumers may need to localize the caching affect only to paging results and scope only to that interaction, rather than for all users. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3359) Allow more control over odata layer caching

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3359?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3359: --------------------------------------- Added an undocumented min rows argument to the cache hint to support selectively not caching things that have too few rows. > Allow more control over odata layer caching > ------------------------------------------- > > Key: TEIID-3359 > URL: https://issues.jboss.org/browse/TEIID-3359 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.11 > > > The caching is always performed at a user level and for each query. Consumers may need to localize the caching affect only to paging results and scope only to that interaction, rather than for all users. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3386) Mixed resutl with (double) full outer join and where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3386?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3386. ----------------------------------- Resolution: Won't Fix Marking as won't fix on our side as it's unclear what the exact parameters of the bug are for oracle, that it has already been addressed in later oracle versions, and there is a workaround, we'll mark this a won't fix on our side. > Mixed resutl with (double) full outer join and where clause > ----------------------------------------------------------- > > Key: TEIID-3386 > URL: https://issues.jboss.org/browse/TEIID-3386 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Attachments: server.log > > > If a query contains double FULL OUTER JOIN and WHERE clause that contains condition on column from last table, teiid returns mixed result (underlying oracle10). > Query: > SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey, BQT2.LargeB.IntKey AS LargeB_IntKey > FROM (BQT1.SmallA FULL OUTER JOIN BQT2.MediumB ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey) FULL OUTER JOIN BQT2.LargeB ON BQT2.MediumB.IntKey = BQT2.LargeB.IntKey > WHERE BQT2.LargeB.IntKey < 1500 ORDER BY LargeB_IntKey, MediumB_IntKey, SmallA_IntKey; > Actual result: > 0 0 0 > 1 1 1 > 2 2 2 > 3 3 3 > ... ... ... > 49 49 49 > 50 50 50 > ... ... ... > 999 999 999 > <null> <null> 1000 > ... ... ... > <null> <null> 1499 > Expected result: > 0 0 0 > 1 1 1 > 2 2 2 > 3 3 3 > ... ... ... > 49 49 49 > <null> 50 50 > ... ... ... > 999 999 999 > <null> <null> 1000 > ... ... ... > <null> <null> 1499 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3390) Improve SQL/XML generation performance and limit disk usage

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3390?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3390: --------------------------------------- Added behavior around the session variable clean_lobs_onclose. For example "select teiid_session_set('clean_lobs_onclose', false)" will disable the auto cleanup. > Improve SQL/XML generation performance and limit disk usage > ----------------------------------------------------------- > > Key: TEIID-3390 > URL: https://issues.jboss.org/browse/TEIID-3390 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Deeply nested large xml documents generated by SQL/XML can create a lot of temporary disk backed objects. These objects can have slow cleanup based upon when their references get cleared. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3412) Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3412?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3412: ------------------------------------ Yes, that's it. > Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8 > ------------------------------------------------------------------------------ > > Key: TEIID-3412 > URL: https://issues.jboss.org/browse/TEIID-3412 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > > In JDK 1.8, the ODBC-JDBC bridge is removed, so accessing MS Access using this method will not be available. An alternative, open source, driver that can be used is: http://jackcess.sourceforge.net > In nexus: > <dependency> > <groupId>com.healthmarketscience.jackcess</groupId> > <artifactId>jackcess</artifactId> > <version>2.0.9</version> > </dependency> > This may require a new translator, but won't be know until a deeper look is done. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3413) Support multiple metadata tags

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3413: ------------------------------------- Summary: Support multiple metadata tags Key: TEIID-3413 URL: https://issues.jboss.org/browse/TEIID-3413 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 To allow for a more flexible configuration, we should support multiple metadata tags under a model, rather than relying on comma separated values. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3411) LDAP translator and multi-valued arrays

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3411: --------------------------------------- Converting to multiple rows only makes sense when there is a single multi-valued attribute. If there is more than one you would get a large cross product. Given that you can use the array option (TEIID-1675) with arrayiterate (TEIID-3362) or other mechanisms to expand the rows is there a need to pursue this? > LDAP translator and multi-valued arrays > --------------------------------------- > > Key: TEIID-3411 > URL: https://issues.jboss.org/browse/TEIID-3411 > Project: Teiid > Issue Type: Feature Request > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > The problem is with how multi-valued attribute from the LDAP response is handled. They don't want to have the data mapped to an array or multivalued-concat and then transformed into another table to get the unique values. There is an issue with the translator as it should handle multivalued attribute, by simply creating multiple rows for each value of the multivalued attribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3412) Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3412?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3412: --------------------------------------- There is http://ucanaccess.sourceforge.net/site.html that uses jackcess underneath and provides JDBC access. > Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8 > ------------------------------------------------------------------------------ > > Key: TEIID-3412 > URL: https://issues.jboss.org/browse/TEIID-3412 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > > In JDK 1.8, the ODBC-JDBC bridge is removed, so accessing MS Access using this method will not be available. An alternative, open source, driver that can be used is: http://jackcess.sourceforge.net > In nexus: > <dependency> > <groupId>com.healthmarketscience.jackcess</groupId> > <artifactId>jackcess</artifactId> > <version>2.0.9</version> > </dependency> > This may require a new translator, but won't be know until a deeper look is done. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3411) LDAP translator and multi-valued arrays

by Debbie Steigner (JIRA)

Debbie Steigner created TEIID-3411: -------------------------------------- Summary: LDAP translator and multi-valued arrays Key: TEIID-3411 URL: https://issues.jboss.org/browse/TEIID-3411 Project: Teiid Issue Type: Feature Request Reporter: Debbie Steigner Assignee: Steven Hawkins The problem is with how multi-valued attribute from the LDAP response is handled. They don't want to have the data mapped to an array or multivalued-concat and then transformed into another table to get the unique values. There is an issue with the translator as it should handle multivalued attribute, by simply creating multiple rows for each value of the multivalued attribute. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3412) Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8

by Van Halbert (JIRA)

Van Halbert created TEIID-3412: ---------------------------------- Summary: Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8 Key: TEIID-3412 URL: https://issues.jboss.org/browse/TEIID-3412 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 9.x Reporter: Van Halbert Assignee: Steven Hawkins In JDK 1.8, the ODBC-JDBC bridge is removed, so accessing MS Access using this method will not be available. An alternative, open source, driver that can be used is: http://jackcess.sourceforge.net In nexus: <dependency> <groupId>com.healthmarketscience.jackcess</groupId> <artifactId>jackcess</artifactId> <version>2.0.9</version> </dependency> This may require a new translator, but won't be know until a deeper look is done. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015