February 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2858: ------------------------------------ Otherwise, using char (as originally imported type), the results were truncated (which started the whole issue). > Database use of char[>1] cause using Convert(x,x) and negates using an index > ---------------------------------------------------------------------------- > > Key: TEIID-2858 > URL: https://issues.jboss.org/browse/TEIID-2858 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans. > Note: There is no option to change the database schemas, because they are from a COTS product. > I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-2858 at 2/20/14 2:04 PM: ------------------------------------------------------------- That's not true. It was tested in this manner and the results are posted in the other jira. This is when we realized the convert was being used. was (Author: van.halbert): That's not true. It was tested in this manner and the results are posted in the other jira. > Database use of char[>1] cause using Convert(x,x) and negates using an index > ---------------------------------------------------------------------------- > > Key: TEIID-2858 > URL: https://issues.jboss.org/browse/TEIID-2858 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans. > Note: There is no option to change the database schemas, because they are from a COTS product. > I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-2858: -------------------------------- > Database use of char[>1] cause using Convert(x,x) and negates using an index > ---------------------------------------------------------------------------- > > Key: TEIID-2858 > URL: https://issues.jboss.org/browse/TEIID-2858 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans. > Note: There is no option to change the database schemas, because they are from a COTS product. > I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2858: ------------------------------------ That's not true. It was tested in this manner and the results are posted in the other jira. > Database use of char[>1] cause using Convert(x,x) and negates using an index > ---------------------------------------------------------------------------- > > Key: TEIID-2858 > URL: https://issues.jboss.org/browse/TEIID-2858 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans. > Note: There is no option to change the database schemas, because they are from a COTS product. > I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2858. ----------------------------------- Resolution: Rejected The issue here is with selecting an inappropriate runtime type. If a fixed char with length greater than 1 is modeled as string no convert will be used. > Database use of char[>1] cause using Convert(x,x) and negates using an index > ---------------------------------------------------------------------------- > > Key: TEIID-2858 > URL: https://issues.jboss.org/browse/TEIID-2858 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans. > Note: There is no option to change the database schemas, because they are from a COTS product. > I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-2858: ------------------------------- Issue Type: Bug (was: Enhancement) > Database use of char[>1] cause using Convert(x,x) and negates using an index > ---------------------------------------------------------------------------- > > Key: TEIID-2858 > URL: https://issues.jboss.org/browse/TEIID-2858 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans. > Note: There is no option to change the database schemas, because they are from a COTS product. > I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index

by Van Halbert (JIRA)

Van Halbert created TEIID-2858: ---------------------------------- Summary: Database use of char[>1] cause using Convert(x,x) and negates using an index Key: TEIID-2858 URL: https://issues.jboss.org/browse/TEIID-2858 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.4.1 Reporter: Van Halbert Assignee: Steven Hawkins When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans. Note: There is no option to change the database schemas, because they are from a COTS product. I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2813) Report translator CPU time

by Mark Addleman (JIRA)

[ https://issues.jboss.org/browse/TEIID-2813?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2813: -------------------------------------- Sorry for the delay. No, my contribution is held up in legal. It doesn't look like I'll get approval for it soon. > Report translator CPU time > -------------------------- > > Key: TEIID-2813 > URL: https://issues.jboss.org/browse/TEIID-2813 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Addleman > Assignee: Steven Hawkins > > The COMMAND_LOG ought to report the CPU time accumulated by the translator for performance tuning purposes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2857) Build Error with Teiid POM Dependency

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2857?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2857: ------------------------------------ Regarding snapshot for: jboss-integration-platform-bom It can be updated to use the latest, which is CR6, but no final is available yet. > Build Error with Teiid POM Dependency > ------------------------------------- > > Key: TEIID-2857 > URL: https://issues.jboss.org/browse/TEIID-2857 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.6 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > > In the jboss public maven repository: > https://repository.jboss.org/nexus/content/groups/public > The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be > Teiid build/configuration bugs. > These two issues are causing our source code build to fail. > The pom file is located here: > https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/... > In this pom file there are two declared dependencies: > <version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform> > <jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version> > <dependency> > <groupId>org.jboss.integration-platform</groupId> > <artifactId>jboss-integration-platform-bom</artifactId> > <version>${version.org.jboss.integration-platform}</version> > <scope>import</scope> > <type>pom</type> > </dependency> > <dependency> > <groupId>org.jboss.as</groupId> > <artifactId>jboss-as-parent</artifactId> > <version>${jbossas-version}</version> > <type>pom</type> > <scope>import</scope> > </dependency> > Here are the issues: > 1) Snapshot dependency existing in the 8.6.0-FINAL Release > - jboss-integration-platform-bom/6.0.0-SNAPSHOT > 2) Declared dependency does not exist in the repo repository.jboss.org > - jboss-as-parent/7.2.0.Alpha1-redhat-4 > - We see dependencies only for: > - 7.2.0.Alpha1-SNAPSHOT > - 7.2.0.Fina > I'm not sure why these dependencies are needed when pulling in the Teiid artifacts, but perhaps because the <scope> of > these dependencies is set to "import" (<scope>import</scope>) > Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found. > For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in > repository.jboss.org so this also fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2857) Build Error with Teiid POM Dependency

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2857?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2857: --------------------------------------- > Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found. I'm not sure that means there is a bug here so much as what version is available for us to reference. - Van, is there a need to reference a snapshot here? > For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in repository.jboss.org so this also fails. It exists in eap repository - see https://github.com/teiid/teiid/blob/master/settings.xml > Build Error with Teiid POM Dependency > ------------------------------------- > > Key: TEIID-2857 > URL: https://issues.jboss.org/browse/TEIID-2857 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.6 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > > In the jboss public maven repository: > https://repository.jboss.org/nexus/content/groups/public > The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be > Teiid build/configuration bugs. > These two issues are causing our source code build to fail. > The pom file is located here: > https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/... > In this pom file there are two declared dependencies: > <version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform> > <jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version> > <dependency> > <groupId>org.jboss.integration-platform</groupId> > <artifactId>jboss-integration-platform-bom</artifactId> > <version>${version.org.jboss.integration-platform}</version> > <scope>import</scope> > <type>pom</type> > </dependency> > <dependency> > <groupId>org.jboss.as</groupId> > <artifactId>jboss-as-parent</artifactId> > <version>${jbossas-version}</version> > <type>pom</type> > <scope>import</scope> > </dependency> > Here are the issues: > 1) Snapshot dependency existing in the 8.6.0-FINAL Release > - jboss-integration-platform-bom/6.0.0-SNAPSHOT > 2) Declared dependency does not exist in the repo repository.jboss.org > - jboss-as-parent/7.2.0.Alpha1-redhat-4 > - We see dependencies only for: > - 7.2.0.Alpha1-SNAPSHOT > - 7.2.0.Fina > I'm not sure why these dependencies are needed when pulling in the Teiid artifacts, but perhaps because the <scope> of > these dependencies is set to "import" (<scope>import</scope>) > Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found. > For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in > repository.jboss.org so this also fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2014