March 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5685) Allow for binding non-ascii strings as varchar

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5685: ------------------------------------- Summary: Allow for binding non-ascii strings as varchar Key: TEIID-5685 URL: https://issues.jboss.org/browse/TEIID-5685 Project: Teiid Issue Type: Quality Risk Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 Related to TEIID-5587, even newer oracle drivers that do support NVARCHAR will throw an exception when the number of bytes in an NVARCHAR string exceeds 4000. In situations, such as insert, where the underlying native type can be detected, we can simply bind as VARCHAR if it's not a multi-byte type - and log that the string will have replacement characters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5684) Show Latest Deployed Date of VDB in metadata tables

by Chandra Akkinepalli (Jira)

Chandra Akkinepalli created TEIID-5684: ------------------------------------------ Summary: Show Latest Deployed Date of VDB in metadata tables Key: TEIID-5684 URL: https://issues.jboss.org/browse/TEIID-5684 Project: Teiid Issue Type: Enhancement Reporter: Chandra Akkinepalli Assignee: Steven Hawkins There is no easy way to tell when a VDB is last deployed on the server without scanning through server.log. This is very useful metadata to have handy. Is it possible to show when a VDB is last deployed on the server via metadata tables. May be show this info along with VDB name and version in SYS.VirtualDatabase table? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5500) Improve OData performance

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5500?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5500: --------------------------------------- Added an initial commit that will have us work over 64 pages at time - rather than the old behavior which was unlimited. Ideally this will affect only a small amount of usage. > Improve OData performance > ------------------------- > > Key: TEIID-5500 > URL: https://issues.jboss.org/browse/TEIID-5500 > Project: Teiid > Issue Type: Enhancement > Components: OData, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > See https://developer.jboss.org/thread/277783 > There is a significant overhead for OData vs. JDBC for a single client especially in terms of latency. > We should investigate pre-building additional batch results and entity caching in general. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5681) Error when trying to sort an expanded data set

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5681?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5681. ----------------------------------- Resolution: Explained > Error when trying to sort an expanded data set > ---------------------------------------------- > > Key: TEIID-5681 > URL: https://issues.jboss.org/browse/TEIID-5681 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > > Hello together, > when using orderby together with an odata expand operation I get and error. The statement I am trying looks as follows: > https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?$select=idDiar... > The error is: > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>null</code> > <message> > TEIID31202 Detected that an already sorted set of values was not in the expected order (typically UTF-16 / UCS-2). Please check the translator settings to ensure character columns used for joining are sorted as expected. > </message> > </error> > Please note, when using orderby without expand, the orderby is working as expected. The attribute which shall be used for ordering has the following type: > <Property Name="MealNumber" Type="Edm.String" Nullable="false" MaxLength="1"> > In the underlaying database it is defined as an ENUM('1','2','3','4','5') -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5681) Error when trying to sort an expanded data set

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5681?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5681: --------------------------------------- Well, from my point of view it is solved then. I assume more than a conversion, like you mentioned, cannot be done if the implementation in Java is signed BIGINT. > Error when trying to sort an expanded data set > ---------------------------------------------- > > Key: TEIID-5681 > URL: https://issues.jboss.org/browse/TEIID-5681 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > > Hello together, > when using orderby together with an odata expand operation I get and error. The statement I am trying looks as follows: > https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?$select=idDiar... > The error is: > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>null</code> > <message> > TEIID31202 Detected that an already sorted set of values was not in the expected order (typically UTF-16 / UCS-2). Please check the translator settings to ensure character columns used for joining are sorted as expected. > </message> > </error> > Please note, when using orderby without expand, the orderby is working as expected. The attribute which shall be used for ordering has the following type: > <Property Name="MealNumber" Type="Edm.String" Nullable="false" MaxLength="1"> > In the underlaying database it is defined as an ENUM('1','2','3','4','5') -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5681) Error when trying to sort an expanded data set

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5681?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5681: --------------------------------------- Can this be marked as resolved then? > Error when trying to sort an expanded data set > ---------------------------------------------- > > Key: TEIID-5681 > URL: https://issues.jboss.org/browse/TEIID-5681 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > > Hello together, > when using orderby together with an odata expand operation I get and error. The statement I am trying looks as follows: > https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?$select=idDiar... > The error is: > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>null</code> > <message> > TEIID31202 Detected that an already sorted set of values was not in the expected order (typically UTF-16 / UCS-2). Please check the translator settings to ensure character columns used for joining are sorted as expected. > </message> > </error> > Please note, when using orderby without expand, the orderby is working as expected. The attribute which shall be used for ordering has the following type: > <Property Name="MealNumber" Type="Edm.String" Nullable="false" MaxLength="1"> > In the underlaying database it is defined as an ENUM('1','2','3','4','5') -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5683) Push or use limit information before dependent join processing

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5683: ------------------------------------- Summary: Push or use limit information before dependent join processing Key: TEIID-5683 URL: https://issues.jboss.org/browse/TEIID-5683 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 12.2 There appear to be some situations (such as a left outer join from TEIID-5680) where the limit could help direct a dependent join, but isn't considered as rule push limit isn't run until later. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5605) widenUnsignedTypes does not account for long/bigint

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5605?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5605: ---------------------------------- Fix Version/s: 11.2.3 > widenUnsignedTypes does not account for long/bigint > --------------------------------------------------- > > Key: TEIID-5605 > URL: https://issues.jboss.org/browse/TEIID-5605 > Project: Teiid > Issue Type: Quality Risk > Components: JDG Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1, 11.2.3 > > > An unsigned long/bigint from a database will still be mapped to a teiid long - which will have issues with values above max_long. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5681) Error when trying to sort an expanded data set

by Christoph John (Jira)

[ https://issues.jboss.org/browse/TEIID-5681?page=com.atlassian.jira.plugin... ] Christoph John commented on TEIID-5681: --------------------------------------- Well, I think then we have at least a partial solution. With my mysql8 database I have to use the Teiid importer anyway. I had trouble with the JDBC importer, hence I am not using it anymore. > Error when trying to sort an expanded data set > ---------------------------------------------- > > Key: TEIID-5681 > URL: https://issues.jboss.org/browse/TEIID-5681 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > > Hello together, > when using orderby together with an odata expand operation I get and error. The statement I am trying looks as follows: > https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?$select=idDiar... > The error is: > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>null</code> > <message> > TEIID31202 Detected that an already sorted set of values was not in the expected order (typically UTF-16 / UCS-2). Please check the translator settings to ensure character columns used for joining are sorted as expected. > </message> > </error> > Please note, when using orderby without expand, the orderby is working as expected. The attribute which shall be used for ordering has the following type: > <Property Name="MealNumber" Type="Edm.String" Nullable="false" MaxLength="1"> > In the underlaying database it is defined as an ENUM('1','2','3','4','5') -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5681) Error when trying to sort an expanded data set

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5681?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5681: --------------------------------------- Usually the importer will automatically handle widening unsigned types. However the Teiid importer was not handling bigint - TEIID-5605 So if you are using the Teiid connection importer, that will be automatically addressed with that change. I'm not sure if the Teiid Designer JDBC importer correctly handles that situation or as you say if it should be producing a warning. > Error when trying to sort an expanded data set > ---------------------------------------------- > > Key: TEIID-5681 > URL: https://issues.jboss.org/browse/TEIID-5681 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Christoph John > Assignee: Steven Hawkins > Priority: Major > > Hello together, > when using orderby together with an odata expand operation I get and error. The statement I am trying looks as follows: > https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?$select=idDiar... > The error is: > <error xmlns="http://docs.oasis-open.org/odata/ns/metadata"> > <code>null</code> > <message> > TEIID31202 Detected that an already sorted set of values was not in the expected order (typically UTF-16 / UCS-2). Please check the translator settings to ensure character columns used for joining are sorted as expected. > </message> > </error> > Please note, when using orderby without expand, the orderby is working as expected. The attribute which shall be used for ordering has the following type: > <Property Name="MealNumber" Type="Edm.String" Nullable="false" MaxLength="1"> > In the underlaying database it is defined as an ENUM('1','2','3','4','5') -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2019