April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2916?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2916: ---------------------------------- Fix Version/s: 8.7.1 Affects Version/s: 8.6 (was: 8.8) > HIVE2: Teiid didn't translate the SQL correctly for numeric field > ------------------------------------------------------------------ > > Key: TEIID-2916 > URL: https://issues.jboss.org/browse/TEIID-2916 > Project: Teiid > Issue Type: Sub-task > Components: Misc. Connectors > Affects Versions: 8.6 > Environment: HIVE2 with Teiid > Reporter: Ivan Chan > Labels: Teiid > Fix For: 8.7.1 > > > Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver. > Original Query: > select "store_sales", > "store_state", > "store_country" > from "Impala"."sales_new" > where "store_sales" between 1.5 and 10 > limit 1000 > After Translation (Teiid): > SELECT g_0.store_sales AS c_0, g_0.store_state AS c_ > 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS > decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000 > "decimal" is not supported identifier in HIVE driver: > Encountered: IDENTIFIER > Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT, > STRING, TIMESTAMP, TINYINT -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2926) Import properties definitions provided via getTranslatorDefinitions() call do not return default values

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2926?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2926. --------------------------------- Labels: Final (was: ) Resolution: Done Fixed the coding error in the TranslatorUtil.java class to correctly return the default value of the import property. Also added unit test to verify. > Import properties definitions provided via getTranslatorDefinitions() call do not return default values > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-2926 > URL: https://issues.jboss.org/browse/TEIID-2926 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7 > > > While enabling runtime-provided *IMPORT* properties for the Teiid Connection importer in Designer, I noticed that the property definitions that got returned did not include a *defaultValue*. > The feature will work as is, however, users may be needlessly setting some properties to default (like most booleans) to false. > This is also inconsistent with the Translator Override property definitions. The majority of those are defined with default values. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2926) Import properties definitions provided via getTranslatorDefinitions() call do not return default values

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2926?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2926: -------------------------------- Affects Version/s: 8.7 Component/s: AdminApi > Import properties definitions provided via getTranslatorDefinitions() call do not return default values > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-2926 > URL: https://issues.jboss.org/browse/TEIID-2926 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Barry LaFond > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7 > > > While enabling runtime-provided *IMPORT* properties for the Teiid Connection importer in Designer, I noticed that the property definitions that got returned did not include a *defaultValue*. > The feature will work as is, however, users may be needlessly setting some properties to default (like most booleans) to false. > This is also inconsistent with the Translator Override property definitions. The majority of those are defined with default values. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2925) "driver-name" property missing for resource-adapters

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2925?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2925. --------------------------------- Labels: Final (was: ) Resolution: Done Added "driver-name" property for the module based resource-adapters. it is derived based on module name of the installed RA and created connection factory's RA. > "driver-name" property missing for resource-adapters > ---------------------------------------------------- > > Key: TEIID-2925 > URL: https://issues.jboss.org/browse/TEIID-2925 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7 > > > For resource-adapter that are module based the "driver-name" property is missing, so it becomes cumbersome to match with its original type after the connection factory creation. > Admin API should provide a way when getDataSource(...) is called, "driver-name" must be always present -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2926) Import properties definitions provided via getTranslatorDefinitions() call do not return default values

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2926?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2926: -------------------------------- Fix Version/s: 8.7 > Import properties definitions provided via getTranslatorDefinitions() call do not return default values > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-2926 > URL: https://issues.jboss.org/browse/TEIID-2926 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Ramesh Reddy > Fix For: 8.7 > > > While enabling runtime-provided *IMPORT* properties for the Teiid Connection importer in Designer, I noticed that the property definitions that got returned did not include a *defaultValue*. > The feature will work as is, however, users may be needlessly setting some properties to default (like most booleans) to false. > This is also inconsistent with the Translator Override property definitions. The majority of those are defined with default values. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2926) Import properties definitions provided via getTranslatorDefinitions() call do not return default values

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2926?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2926: -------------------------------- Summary: Import properties definitions provided via getTranslatorDefinitions() call do not return default values (was: Import properti definitions provided via getTranslatorDefinitions() call do not return default values) Issue Type: Bug (was: Enhancement) Assignee: Ramesh Reddy (was: Steven Hawkins) > Import properties definitions provided via getTranslatorDefinitions() call do not return default values > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-2926 > URL: https://issues.jboss.org/browse/TEIID-2926 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Ramesh Reddy > > While enabling runtime-provided *IMPORT* properties for the Teiid Connection importer in Designer, I noticed that the property definitions that got returned did not include a *defaultValue*. > The feature will work as is, however, users may be needlessly setting some properties to default (like most booleans) to false. > This is also inconsistent with the Translator Override property definitions. The majority of those are defined with default values. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2926) Import properti definitions provided via getTranslatorDefinitions() call do not return default values

by Barry LaFond (JIRA)

Barry LaFond created TEIID-2926: ----------------------------------- Summary: Import properti definitions provided via getTranslatorDefinitions() call do not return default values Key: TEIID-2926 URL: https://issues.jboss.org/browse/TEIID-2926 Project: Teiid Issue Type: Enhancement Reporter: Barry LaFond Assignee: Steven Hawkins While enabling runtime-provided *IMPORT* properties for the Teiid Connection importer in Designer, I noticed that the property definitions that got returned did not include a *defaultValue*. The feature will work as is, however, users may be needlessly setting some properties to default (like most booleans) to false. This is also inconsistent with the Translator Override property definitions. The majority of those are defined with default values. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2925) "driver-name" property missing for resource-adapters

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2925: ----------------------------------- Summary: "driver-name" property missing for resource-adapters Key: TEIID-2925 URL: https://issues.jboss.org/browse/TEIID-2925 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7 For resource-adapter that are module based the "driver-name" property is missing, so it becomes cumbersome to match with its original type after the connection factory creation. Admin API should provide a way when getDataSource(...) is called, "driver-name" must be always present -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2849) MongoDB: Provide basic metadata support

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2849?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2849: ------------------------------------- is array compare like {code} select * from foo where array = (1, 2..) {code} In that case, there is more work to be done on mongodb translator to support it. MongoDB does support search, however update of array lacking full support. > MongoDB: Provide basic metadata support > --------------------------------------- > > Key: TEIID-2849 > URL: https://issues.jboss.org/browse/TEIID-2849 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: mongodb > Fix For: 8.7 > > > Currently there is no native metadata import support in the MongoDB translator. It was avoided int he first run because there is no good way to interpret the complex document records. This position has not changed, but this enhancement request is to see if it can capture simple documents or top level documents as a starting point to capture and then to improve upon manually using tooling. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2849) MongoDB: Provide basic metadata support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2849?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2849: --------------------------------------- I saw a commit saying that array types were marked as unsearchable. Is this because of a source restriction, since in Teiid array values are comparable. > MongoDB: Provide basic metadata support > --------------------------------------- > > Key: TEIID-2849 > URL: https://issues.jboss.org/browse/TEIID-2849 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: mongodb > Fix For: 8.7 > > > Currently there is no native metadata import support in the MongoDB translator. It was avoided int he first run because there is no good way to interpret the complex document records. This position has not changed, but this enhancement request is to see if it can capture simple documents or top level documents as a starting point to capture and then to improve upon manually using tooling. -- 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

11 years, 11 months

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 2014