[JBoss JIRA] (TEIIDDES-1911) Teiid Connection lacks a way to define importer properties
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1911?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1911:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1024875
> 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
[JBoss JIRA] (TEIIDDES-1916) Password Provider UI not being initialised correctly
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1916?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1916.
---------------------------------------
Resolution: Done
> Password Provider UI not being initialised correctly
> ----------------------------------------------------
>
> Key: TEIIDDES-1916
> URL: https://issues.jboss.org/browse/TEIIDDES-1916
> Project: Teiid Designer
> Issue Type: Bug
> Components: Eclipse Integration
> Affects Versions: 8.3
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Priority: Critical
> Fix For: 8.3
>
>
> Once designer is installed in eclipse and a designer project is imported, validation of the latter takes place. With no server configured, this can result in an exception being displayed:
> {code}
> Errors occurred during the build.
> Errors running builder 'Model Validator' on project 'US_States'.
> org.eclipse.core.runtime.CoreException: Plug-in "org.teiid.designer.dqp" was unable to instantiate class "org.teiid.designer.runtime.TeiidServerManager".
> {code}
> {code}
> Exception in thread "org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator(a)1112a81.ServerVersionLoadingThread" java.lang.IllegalStateException: org.eclipse.core.runtime.CoreException: Plug-in "org.teiid.designer.dqp" was unable to instantiate class "org.teiid.designer.runtime.TeiidServerManager".
> at org.teiid.designer.core.ModelerCore.getTeiidServerManager(ModelerCore.java:2290)
> at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$ServerVersionLoadingThread.run(ModelExplorerResourceNavigator.java:323)
> Caused by: org.eclipse.core.runtime.CoreException: Plug-in "org.teiid.designer.dqp" was unable to instantiate class "org.teiid.designer.runtime.TeiidServerManager".
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.teiid.designer.ExtensionRegistryUtils.createExtensionInstances(ExtensionRegistryUtils.java:38)
> at org.teiid.designer.core.ModelerCore.getTeiidServerManager(ModelerCore.java:2288)
> ... 1 more
> Caused by: java.lang.IllegalStateException: java.lang.IllegalStateException: No implementation found for the extension point org.teiid.designer.spi.teiidPasswordProvider.
> at org.teiid.designer.runtime.DqpPlugin.getPasswordProvider(DqpPlugin.java:188)
> at org.teiid.designer.runtime.TeiidServerManager.<init>(TeiidServerManager.java:292)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:374)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> ... 6 more
> Caused by: java.lang.IllegalStateException: No implementation found for the extension point org.teiid.designer.spi.teiidPasswordProvider.
> at org.teiid.designer.ExtensionRegistryUtils.createExtensionInstances(ExtensionRegistryUtils.java:48)
> at org.teiid.designer.runtime.DqpPlugin.getPasswordProvider(DqpPlugin.java:186)
> {code}
> This is due to the DQP UI plugin not being activated (despite being installed) hence no password provider implementation is available.
> Since the password provider is used in only 2 instances, it is misguided to have the dqp plugin depend on its correct initialisation. Better to move its initialisation to when it is actually required, ie. TeiidSourceDataFactory.
--
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
[JBoss JIRA] (TEIIDDES-1916) Password Provider UI not being initialised correctly
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-1916:
-----------------------------------------
Summary: Password Provider UI not being initialised correctly
Key: TEIIDDES-1916
URL: https://issues.jboss.org/browse/TEIIDDES-1916
Project: Teiid Designer
Issue Type: Bug
Components: Eclipse Integration
Affects Versions: 8.3
Reporter: Paul Richardson
Assignee: Paul Richardson
Priority: Critical
Fix For: 8.3
Once designer is installed in eclipse and a designer project is imported, validation of the latter takes place. With no server configured, this can result in an exception being displayed:
{code}
Errors occurred during the build.
Errors running builder 'Model Validator' on project 'US_States'.
org.eclipse.core.runtime.CoreException: Plug-in "org.teiid.designer.dqp" was unable to instantiate class "org.teiid.designer.runtime.TeiidServerManager".
{code}
{code}
Exception in thread "org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator(a)1112a81.ServerVersionLoadingThread" java.lang.IllegalStateException: org.eclipse.core.runtime.CoreException: Plug-in "org.teiid.designer.dqp" was unable to instantiate class "org.teiid.designer.runtime.TeiidServerManager".
at org.teiid.designer.core.ModelerCore.getTeiidServerManager(ModelerCore.java:2290)
at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$ServerVersionLoadingThread.run(ModelExplorerResourceNavigator.java:323)
Caused by: org.eclipse.core.runtime.CoreException: Plug-in "org.teiid.designer.dqp" was unable to instantiate class "org.teiid.designer.runtime.TeiidServerManager".
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at org.teiid.designer.ExtensionRegistryUtils.createExtensionInstances(ExtensionRegistryUtils.java:38)
at org.teiid.designer.core.ModelerCore.getTeiidServerManager(ModelerCore.java:2288)
... 1 more
Caused by: java.lang.IllegalStateException: java.lang.IllegalStateException: No implementation found for the extension point org.teiid.designer.spi.teiidPasswordProvider.
at org.teiid.designer.runtime.DqpPlugin.getPasswordProvider(DqpPlugin.java:188)
at org.teiid.designer.runtime.TeiidServerManager.<init>(TeiidServerManager.java:292)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
... 6 more
Caused by: java.lang.IllegalStateException: No implementation found for the extension point org.teiid.designer.spi.teiidPasswordProvider.
at org.teiid.designer.ExtensionRegistryUtils.createExtensionInstances(ExtensionRegistryUtils.java:48)
at org.teiid.designer.runtime.DqpPlugin.getPasswordProvider(DqpPlugin.java:186)
{code}
This is due to the DQP UI plugin not being activated (despite being installed) hence no password provider implementation is available.
Since the password provider is used in only 2 instances, it is misguided to have the dqp plugin depend on its correct initialisation. Better to move its initialisation to when it is actually required, ie. TeiidSourceDataFactory.
--
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
[JBoss JIRA] (TEIIDDES-1915) Flat file connection profile doesn't allow relative path to folder & other
by Lucie Fabrikova (JIRA)
Lucie Fabrikova created TEIIDDES-1915:
-----------------------------------------
Summary: Flat file connection profile doesn't allow relative path to folder & other
Key: TEIIDDES-1915
URL: https://issues.jboss.org/browse/TEIIDDES-1915
Project: Teiid Designer
Issue Type: Feature Request
Environment: JBDS 7.0.1.GA, Teiid Designer 8.2.0Final
Reporter: Lucie Fabrikova
Priority: Minor
1. New -> Connection profile -> Flat file data source
2. Set home folder to relative path
3. Finish; Import: Flat file source >> source model
4. Choose the created flat file connection profile
5. Clicking through the wizard, a model is created
6. Executing VDB containing the model and flat file source model causes error (flat file - "EmpData.csv - not found)
ad 5. clicking on "Edit..." gives error message "Invalid flat file data source path. Please correct the connection profile."
Next unclear behavior:
ad 2. checkbox "Validate home folder" is checked and "Test connection" button does nothing, and buttons "Next", "Finish" are disabled
(after setting both relative or absolute path)
--
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
[JBoss JIRA] (TEIIDDES-1914) Recursive element - mismatch column names between mapping classes
by Lucie Fabrikova (JIRA)
Lucie Fabrikova created TEIIDDES-1914:
-----------------------------------------
Summary: Recursive element - mismatch column names between mapping classes
Key: TEIIDDES-1914
URL: https://issues.jboss.org/browse/TEIIDDES-1914
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: 8.2
Environment: JBDS 7.0.1.GA, Teiid Designer 8.2Final
Reporter: Lucie Fabrikova
I run the E2eRecursiveXmlTextSourceTestScript; the XML view model from XSD contains mapping classes Employee and Supervisor. Next I copy the attributes from Employee to Supervisor. If the order of columns in Supervisor isn't the same as in Employee, I get
"Mismatch column name between mapping class Employee and Supervisor"
I am not sure if this is bug or if the message error is considered self-explanatory.
--
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
[JBoss JIRA] (TEIIDDES-1913) Teiid Connection Importer should not proceed for some source types
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1913:
---------------------------------------
Summary: Teiid Connection Importer should not proceed for some source types
Key: TEIIDDES-1913
URL: https://issues.jboss.org/browse/TEIIDDES-1913
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.2
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.3
For some source types, teiid cannot generate DDL for creating the relational model - user is required to manually model. Two examples are ldap and mongodb. For these cases, the Teiid Connection importer should disallow their use - the vdb deployment and schema retrieval is not possible.
Need to determine which of the built-in drivers should be disallowed. If the user selects one of these types, show a message informing the user that manual modeling is required - and dont allow them to proceed.
--
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
[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:
----------------------------------------
There are 3 different properties you were talking above
1) data source properties - These have been supported begining, no issue here.
2) translator extension properties - these definitions have been added as part of TEIID-2687, needs to go along with translator override properties.
3) translator model import properties - these are very specific to the "Teiid Connection" importer scenario, will not come into picture in the general VDB scenario. These are applicable for importing from a source in a Dynamic VDB scenario.
None of them custom, they are *all* defined, only that for (1) and (2) the property definitions can be queried from Teiid. (3) is not yet. So in the absence of that the best we can do is have the user enter the "custom" properties based the documentation, which will solve the issue. or we can devise a way to expose those properties from Teiid.
> 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
[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:
----------------------------------------
Apart from the XMI/Model extension properties, there seems to be a few places where data-source/translator and VDB properties need to be managed at design-time.
>From a data-source/translator perspective there is also the issue of built-in versus custom. For all built-in properties, I would think a user would expect those properties to just show up. I would not expect any "custom" properties to just show up at design time, unless they were contributed to the Teiid/Server via some configuration file/set-up.
I guess I'd like to make sure we are consistent with our features before we start adding ability to add generic name-value properties to these entities.
> 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