November 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1912) Allow non-managed extension properties

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-1912: ---------------------------------------- Summary: Allow non-managed extension properties Key: TEIIDDES-1912 URL: https://issues.jboss.org/browse/TEIIDDES-1912 Project: Teiid Designer Issue Type: Enhancement Components: Teiid Integration Reporter: Steven Hawkins Requiring managed extension properties puts additional management burden on users and in the case of missing built-in properties does not allow for an easy way to add the properties. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1911?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1911: ---------------------------------------- TEIID-2687 only included the extension properties that could be automatically gleaned off off ExecutionFactory, the importer properties were not part of it. If they need to be, we need someway to expose them on Teiid side. > Teiid Connection lacks a way to define importer properties > ---------------------------------------------------------- > > Key: TEIIDDES-1911 > URL: https://issues.jboss.org/browse/TEIIDDES-1911 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > > In Teiid Connection importer, it lacks a way to define the "import" properties that makes usage cumbersome for user to define to import specific parts of schema, or sometimes impossible (see TEIID-1905) > basically, when user chooses the "translator", after they should be able define some custom key/value pairs as properties, when then should be converted as model import properties in "importVDB-vdb.xml" file. Some sample properties are defined here > https://docs.jboss.org/author/display/TEIID/JDBC+Translator > see "importer" properties. Do not confuse similar "execution properties" which are translator overrides. The sample vdb is like this > {code} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="hive" version="1"> > <description>Shows how to query HiveVDB using Hive</description> > <property name="UseConnectorMetadata" value="cached"/> > <model name="hive"> > <property name="importer.trimColumnNames" value="true"/> > <source name="Hive conector" translator-name="hive" connection-jndi-name="java:/hive-ds"/> > </model> > </vdb> > {code} > As per GUI concerned it should be added in "Select the translator and target model" panel, after the selection of translator -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1911?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1911: ------------------------------------------ TEIID-2687 covers that, but it would be generally useful to support specifying arbitrary properties. > Teiid Connection lacks a way to define importer properties > ---------------------------------------------------------- > > Key: TEIIDDES-1911 > URL: https://issues.jboss.org/browse/TEIIDDES-1911 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > > In Teiid Connection importer, it lacks a way to define the "import" properties that makes usage cumbersome for user to define to import specific parts of schema, or sometimes impossible (see TEIID-1905) > basically, when user chooses the "translator", after they should be able define some custom key/value pairs as properties, when then should be converted as model import properties in "importVDB-vdb.xml" file. Some sample properties are defined here > https://docs.jboss.org/author/display/TEIID/JDBC+Translator > see "importer" properties. Do not confuse similar "execution properties" which are translator overrides. The sample vdb is like this > {code} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="hive" version="1"> > <description>Shows how to query HiveVDB using Hive</description> > <property name="UseConnectorMetadata" value="cached"/> > <model name="hive"> > <property name="importer.trimColumnNames" value="true"/> > <source name="Hive conector" translator-name="hive" connection-jndi-name="java:/hive-ds"/> > </model> > </vdb> > {code} > As per GUI concerned it should be added in "Select the translator and target model" panel, after the selection of translator -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1911?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1911: ---------------------------------------- Does Teiid provide easy access to these relevant properties through the API? > Teiid Connection lacks a way to define importer properties > ---------------------------------------------------------- > > Key: TEIIDDES-1911 > URL: https://issues.jboss.org/browse/TEIIDDES-1911 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > > In Teiid Connection importer, it lacks a way to define the "import" properties that makes usage cumbersome for user to define to import specific parts of schema, or sometimes impossible (see TEIID-1905) > basically, when user chooses the "translator", after they should be able define some custom key/value pairs as properties, when then should be converted as model import properties in "importVDB-vdb.xml" file. Some sample properties are defined here > https://docs.jboss.org/author/display/TEIID/JDBC+Translator > see "importer" properties. Do not confuse similar "execution properties" which are translator overrides. The sample vdb is like this > {code} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="hive" version="1"> > <description>Shows how to query HiveVDB using Hive</description> > <property name="UseConnectorMetadata" value="cached"/> > <model name="hive"> > <property name="importer.trimColumnNames" value="true"/> > <source name="Hive conector" translator-name="hive" connection-jndi-name="java:/hive-ds"/> > </model> > </vdb> > {code} > As per GUI concerned it should be added in "Select the translator and target model" panel, after the selection of translator -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1905: ---------------------------------------- Needs TEIID-1911, to satisfy this need > TrimColumn names should be enabled with hive translator metadata import > ----------------------------------------------------------------------- > > Key: TEIIDDES-1905 > URL: https://issues.jboss.org/browse/TEIIDDES-1905 > Project: Teiid Designer > Issue Type: Bug > Environment: DV Beta > Teiid Designer 8.3.Beta2 > Reporter: Filip Nguyen > > *Problem* > Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names. > *Why* > There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-1911: -------------------------------------- Summary: Teiid Connection lacks a way to define importer properties Key: TEIIDDES-1911 URL: https://issues.jboss.org/browse/TEIIDDES-1911 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Reporter: Ramesh Reddy In Teiid Connection importer, it lacks a way to define the "import" properties that makes usage cumbersome for user to define to import specific parts of schema, or sometimes impossible (see TEIID-1905) basically, when user chooses the "translator", after they should be able define some custom key/value pairs as properties, when then should be converted as model import properties in "importVDB-vdb.xml" file. Some sample properties are defined here https://docs.jboss.org/author/display/TEIID/JDBC+Translator see "importer" properties. Do not confuse similar "execution properties" which are translator overrides. The sample vdb is like this {code} <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <vdb name="hive" version="1"> <description>Shows how to query HiveVDB using Hive</description> <property name="UseConnectorMetadata" value="cached"/> <model name="hive"> <property name="importer.trimColumnNames" value="true"/> <source name="Hive conector" translator-name="hive" connection-jndi-name="java:/hive-ds"/> </model> </vdb> {code} As per GUI concerned it should be added in "Select the translator and target model" panel, after the selection of translator -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ] Filip Nguyen updated TEIIDDES-1905: ----------------------------------- Comment: was deleted (was: Ramesh, sorry I didn't know it is possible to set importer property when importing using the Wizard. In that case you are right, this can be rejected.) > TrimColumn names should be enabled with hive translator metadata import > ----------------------------------------------------------------------- > > Key: TEIIDDES-1905 > URL: https://issues.jboss.org/browse/TEIIDDES-1905 > Project: Teiid Designer > Issue Type: Bug > Environment: DV Beta > Teiid Designer 8.3.Beta2 > Reporter: Filip Nguyen > > *Problem* > Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names. > *Why* > There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ] Filip Nguyen commented on TEIIDDES-1905: ---------------------------------------- Ramesh, sorry I didn't know it is possible to set importer property when importing using the Wizard. In that case you are right, this can be rejected. > TrimColumn names should be enabled with hive translator metadata import > ----------------------------------------------------------------------- > > Key: TEIIDDES-1905 > URL: https://issues.jboss.org/browse/TEIIDDES-1905 > Project: Teiid Designer > Issue Type: Bug > Environment: DV Beta > Teiid Designer 8.3.Beta2 > Reporter: Filip Nguyen > > *Problem* > Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names. > *Why* > There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1905: ---------------------------------------- Filip, this is error introduced by the Hive driver. In Teiid we added a import property for handling this gracefully. Now, it is user's duty to add this import property when using the "Teiid Connection" importer to properly import the metadata from the Hive, when using this particular version of the Hive driver. Or we need to make this "trimColums" to true by default in the Teiid. But not force this on Designer to provide. All the translators have multiple import properties that can be used to customize this importer, but so far Teiid does not have smarts in the system to expose what these properties are so that Designer can provide a intelligent GUI on top unless they hard code for each of the translator. > TrimColumn names should be enabled with hive translator metadata import > ----------------------------------------------------------------------- > > Key: TEIIDDES-1905 > URL: https://issues.jboss.org/browse/TEIIDDES-1905 > Project: Teiid Designer > Issue Type: Bug > Environment: DV Beta > Teiid Designer 8.3.Beta2 > Reporter: Filip Nguyen > > *Problem* > Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names. > *Why* > There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1905) TrimColumn names should be enabled with hive translator metadata import

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1905?page=com.atlassian.jira.plu... ] Filip Nguyen commented on TEIIDDES-1905: ---------------------------------------- Ramesh, why it should not be an issue with 0.11 driver? I am using the driver and it leaves the padding spaces. Which renders the imported base table unusable. So your conclusion is that, user should import with spaces and fix the source model? > TrimColumn names should be enabled with hive translator metadata import > ----------------------------------------------------------------------- > > Key: TEIIDDES-1905 > URL: https://issues.jboss.org/browse/TEIIDDES-1905 > Project: Teiid Designer > Issue Type: Bug > Environment: DV Beta > Teiid Designer 8.3.Beta2 > Reporter: Filip Nguyen > > *Problem* > Importing Hive Tables, when using Teiid Connection >> Source model, is introducing padding spaces into column names. > *Why* > There is a problem with Hive 0.11 driver which introduces padding spaces into metadata (data types and column names). The problem has been resolved (TEIID-2524) but it is necessary that dynamic VDBs that import this metadata use importer property trimColumnNames property set to true. So it is probably needed to add this property to importVDB-vdb.xml in the case of hive translator import in the Designer. -- 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

12 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2013