April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2943) getIndexInfo is not correct

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2943?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2943. ----------------------------------- Resolution: Done Corrected the type and unique flag handling. TEIID-2944 was logged to add cardinality information as well. > getIndexInfo is not correct > --------------------------- > > Key: TEIID-2943 > URL: https://issues.jboss.org/browse/TEIID-2943 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > DatabaseMetaData.getIndexInfo returns 0 (statistical index) for all indexes. Also the unique flag is not properly honored. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2944) getIndexInfo should return statistical information

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2944: ------------------------------------- Summary: getIndexInfo should return statistical information Key: TEIID-2944 URL: https://issues.jboss.org/browse/TEIID-2944 Project: Teiid Issue Type: Enhancement Components: JDBC Driver Reporter: Steven Hawkins Assignee: Steven Hawkins DatabaseMetaData.getIndexInfo can return statistical indexes with cardinality information and/or cardinality can be returned on the other index info for the table. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2922. ----------------------------------- Resolution: Done Added a validation that constraint names (if given) need to be unique. Also added logic to the jdbc import to prevent the primary key from also being imported as an index. > Extra unique constraint in dynamic vdb schema > --------------------------------------------- > > Key: TEIID-2922 > URL: https://issues.jboss.org/browse/TEIID-2922 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.8 > > > I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table with only a primary key. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2943) getIndexInfo is not correct

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2943: ------------------------------------- Summary: getIndexInfo is not correct Key: TEIID-2943 URL: https://issues.jboss.org/browse/TEIID-2943 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 DatabaseMetaData.getIndexInfo returns 0 (statistical index) for all indexes. Also the unique flag is not properly honored. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2814) HIVE: quote is removed for TIMESTAMP field in where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2814?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2814: --------------------------------------- Ivan, If you are still having issues with timestamp comparison after 0.13, please open up a new issue and we'll figure out what translator changes would be needed. > HIVE: quote is removed for TIMESTAMP field in where clause > ----------------------------------------------------------- > > Key: TEIID-2814 > URL: https://issues.jboss.org/browse/TEIID-2814 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: HIVE and Teiid 8.6 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > Fix For: 8.4.2, 8.7 > > > I am running teiid 8.6 against HIVE. And I found out that quote was removed for TIMESTAMP field in where clause. And it caused java.sql.SQLException: Error while processing statement: FAILED: ParseException line 1:88 missing EOF > Original SQL: > select "the_date", > "store_sales" > from "hive2"."sales_seq" > where ("the_date" > '1970-05-16 00:10:04') > Teiid generated SQL: > SELECT g_0.the_date, g_0.store_sales FROM sales_seq g_0 WHERE g_0.the_date > 1970-05-16 00:10:04.0 > Exception: > Caused by: java.sql.SQLException: Error while processing statement: FAILED: > ParseException line 1:88 missing EOF at '00' near '16' -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2922) Extra unique constraint in dynamic vdb schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2922?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2922: ---------------------------------- Fix Version/s: 8.8 I think that it does make sense to ensure named constraints have a unique name (at the table scope), so we'll add a validation rule on our side for that. This also means that we will need to address mysql returning the primary key in two ways. > Extra unique constraint in dynamic vdb schema > --------------------------------------------- > > Key: TEIID-2922 > URL: https://issues.jboss.org/browse/TEIID-2922 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Steven Hawkins > Fix For: 8.8 > > > I'm getting an extra Unique Constraint in the dynamic VDB schema - for a MySQL table with only a primary key. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2942) Enhanced sort join produces duplicate results

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2942?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2942. ----------------------------------- Resolution: Done Corrected the indexing logic to also account for sort distinct. > Enhanced sort join produces duplicate results > --------------------------------------------- > > Key: TEIID-2942 > URL: https://issues.jboss.org/browse/TEIID-2942 > 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.8 > > > In a plan where an enhanced sort join chooses to create an index on a child that should be SORT_DISTINCT, the distinct processing does not occur. > For example this would occur with a query such as: > select a.e1, b.e2 from pm1.g1 as a, (select e1, e2 from pm2.g2 union select e1, e2 from pm2.g2) as b where a.e1 = b.e1 > where the source does not support union. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2937) Change Apache POI version to 3.10

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2937?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2937: --------------------------------------- Now I'm seeing that the tech preview repository redirects to https, but they have a bad cert which will choke the build as well: Failed to read artifact descriptor for org.apache.poi:poi:jar:3.10: Could not transfer artifact org.apache.poi:poi:pom:3.10 from/to redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/): hostname in certificate didn't match: <maven.repository.redhat.com> != <a248.e.akamai.net> OR <*.akamaihd.net> OR <*.akamaihd-staging.net> OR <a248.e.akamai.net> > Change Apache POI version to 3.10 > --------------------------------- > > Key: TEIID-2937 > URL: https://issues.jboss.org/browse/TEIID-2937 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > Upgrade the Apache POI version used in accessing Excel file to use POI 3.10. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2942) Enhanced sort join produces duplicate results

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2942: ------------------------------------- Summary: Enhanced sort join produces duplicate results Key: TEIID-2942 URL: https://issues.jboss.org/browse/TEIID-2942 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.8 In a plan where an enhanced sort join chooses to create an index on a child that should be SORT_DISTINCT, the distinct processing does not occur. For example this would occur with a query such as: select a.e1, b.e2 from pm1.g1 as a, (select e1, e2 from pm2.g2 union select e1, e2 from pm2.g2) as b where a.e1 = b.e1 where the source does not support union. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2941) Add documentation that explains expected usage patterns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2941?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2941: --------------------------------------- You can add something where ever it seems applicable. Most of the reference doc talks about features somewhat in isolation. To walk through something end-to-end from translator/vdb to sql sounds much more like a quick start. > Add documentation that explains expected usage patterns > ------------------------------------------------------- > > Key: TEIID-2941 > URL: https://issues.jboss.org/browse/TEIID-2941 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Optional > > Would like to see documentation added to explains certain data source usage patterns for which cannot be explained just by using the data source. Example is: > How to access a JSON REST service: > You read JSON using file or web service translator, then use the JSONToXML function, to convert to XML, then use the XMLTABLE function to parse. > This isn't straight forward in the documentation to a novice. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2014