May 2016 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-2837) Server in TD looks like it is not connected after start

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2837?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2837: ----------------------------------- Component/s: Teiid Integration > Server in TD looks like it is not connected after start > ------------------------------------------------------- > > Key: TEIIDDES-2837 > URL: https://issues.jboss.org/browse/TEIIDDES-2837 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 10.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Critical > Fix For: 10.0.1 > > Attachments: Screen Shot 2016-05-09 at 9.42.34.png, Screen Shot 2016-05-09 at 9.43.02.png > > > When I start new server in TD (or try to connect to running server) it looks like TD is not connected to server / teiid instance, even though the server status is [Started, Synchronized]. > I have to refresh the server, to make it work. > See attached screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2813) LDAP importer does not prevent invalid characters in table names

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2813?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2813: ----------------------------------- Issue Type: Enhancement (was: Bug) > LDAP importer does not prevent invalid characters in table names > ---------------------------------------------------------------- > > Key: TEIIDDES-2813 > URL: https://issues.jboss.org/browse/TEIIDDES-2813 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.0.5 > Reporter: Marc Shirley > > Import prefills table names with the LDAP object such as "ou=people" which includes the invalid character '='. The import wizard should prevent a user from naming objects with invalid characters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2818) preview on view that uses another view that is materialized fails

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2818?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2818: ----------------------------------- Fix Version/s: 10.0.2 > preview on view that uses another view that is materialized fails > ----------------------------------------------------------------- > > Key: TEIIDDES-2818 > URL: https://issues.jboss.org/browse/TEIIDDES-2818 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 9.0.6 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.2 > > > If you mark a view table(view.table1) materialized true, the preview option is grayed out as it should be, but if you then create another view table(view.table2) that uses the above materialized view table, the preview option is available but errors with: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.api.exception.query.QueryPlannerException: Group does not exist: view.table1 > We should document this that this is not possible and/or a better error description would be nice and/or disable the preview data option for a view model which is based on view model which has materialized set to true. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2832) Unable to preview - connection-jndi-name is null in dynamic vdb

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2832?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2832: ----------------------------------- Fix Version/s: 10.0.2 > Unable to preview - connection-jndi-name is null in dynamic vdb > --------------------------------------------------------------- > > Key: TEIIDDES-2832 > URL: https://issues.jboss.org/browse/TEIIDDES-2832 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 10.0.2 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 10.0.2 > > Attachments: server.log > > > Import from salesforce using SF importer, then attempt to preview Account table, results in the attached server.log exception. > The dynamic VDB content: > <vdb name="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9" version="1"> > <description>Importer VDB</description> > <property name="UseConnectorMetadata" value="true" /> > <property name="deployment-name" value="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9-vdb.xml" /> > <model name="SFModel" type="PHYSICAL" visible="true"> > <source name="SFModel" translator-name="salesforce" connection-jndi-name="null" /> > <metadata type="DDL"><![CDATA[ > CREATE FOREIGN TABLE Account ( > Id string(18) NOT NULL OPTIONS(NAMEINSOURCE 'Id', NATIVE_TYPE 'id', "teiid_sf:Defaulted on Create" 'TRUE'), -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2844) Quick fix on imported TD VDB produces exception

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2844?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2844: ----------------------------------- Description: When you import attached VDB to a project in TD, there will be a warning that "The VDB's model file "SourceModel" does not exist in the workspace.". After you try to apply quick fix, there is an exception(See screenshot). Problem is that the model is in 2 folders (project/folder2/view/ViewModel.xmi). When you have a model that is directly in project folder or a model that is in one folder quick fix works. was: When you import attached VDB to a project in TD, there will be a warning that "The VDB's model file "SourceModel" does not exist in the workspace.". After you try to apply quick fix, there is an exception(See screenshot). Problem is that the model is in 2 folders (project/folder2/view/ViewModel). When you have a model that is directly in project folder or a model that is in one folder quick fix works. > Quick fix on imported TD VDB produces exception > ----------------------------------------------- > > Key: TEIIDDES-2844 > URL: https://issues.jboss.org/browse/TEIIDDES-2844 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0 > Reporter: Matus Makovy > Attachments: Screen Shot 2016-05-17 at 12.02.43.png, VDB1.vdb > > > When you import attached VDB to a project in TD, there will be a warning that "The VDB's model file "SourceModel" does not exist in the workspace.". After you try to apply quick fix, there is an exception(See screenshot). > Problem is that the model is in 2 folders (project/folder2/view/ViewModel.xmi). When you have a model that is directly in project folder or a model that is in one folder quick fix works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2841) Deprecate XML, XSD and XML Document metamodels

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2841?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2841: ---------------------------------------- What is a XML and XSD models? I know we one time had XML model based XQuery, that can be gone. XSD is still very important. We need to evaluate and re-tool XSD based usecases using the SQL/XML IMO. > Deprecate XML, XSD and XML Document metamodels > ---------------------------------------------- > > Key: TEIIDDES-2841 > URL: https://issues.jboss.org/browse/TEIIDDES-2841 > Project: Teiid Designer > Issue Type: Task > Components: Modeling, Web Services Support > Affects Versions: 10.0 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 10.0.1 > > > Support for creating Web Services, XML Document and Schema (XSD) models should be deprecated. The direction of Teiid runtime metadata has changed and these features should be phased out. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2493: ---------------------------------------- [~blafond] Please also try Windows, this could have came from that. > Check for spaces in the parent directory Flat File connection importer > ---------------------------------------------------------------------- > > Key: TEIIDDES-2493 > URL: https://issues.jboss.org/browse/TEIIDDES-2493 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0, 9.2.1 > > > Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen. > ==================== > The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this. > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} > The embedded space in the ParentDirectory property value is problematic. > Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2493: ---------------------------------------- [~rareddy] This issue was logged because of your comment in the description: *The embedded space in the ParentDirectory property value is problematic.*. It appears to work for the File Directory/Folder use case (TEIIDDES-2493), but fails on the file URL-based use-case (TEIIDDES-2795): org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 SourceModel_1: java.net.URISyntaxException: Illegal character in path at index 40: *file:/home/blafond/Downloads/temp_1/flat file folder/EmpData.csv* So we should NOT be checking for spaces in the File/Directory connection profile wizard, correct? > Check for spaces in the parent directory Flat File connection importer > ---------------------------------------------------------------------- > > Key: TEIIDDES-2493 > URL: https://issues.jboss.org/browse/TEIIDDES-2493 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0, 9.2.1 > > > Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen. > ==================== > The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this. > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} > The embedded space in the ParentDirectory property value is problematic. > Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2493: ------------------------------------------ Thank goodness > Check for spaces in the parent directory Flat File connection importer > ---------------------------------------------------------------------- > > Key: TEIIDDES-2493 > URL: https://issues.jboss.org/browse/TEIIDDES-2493 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0, 9.2.1 > > > Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen. > ==================== > The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this. > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} > The embedded space in the ParentDirectory property value is problematic. > Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2493: ---------------------------------------- [~shawkins] bloody heck... I ran through it *slowly* and was able to deploy the DS and preview successfully {code} <config-property name="ParentDirectory"> /home/blafond/Downloads/temp_1/flat file folder </config-property> {code} > Check for spaces in the parent directory Flat File connection importer > ---------------------------------------------------------------------- > > Key: TEIIDDES-2493 > URL: https://issues.jboss.org/browse/TEIIDDES-2493 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Labels: release_notes, verified_jbdsis-9.0.0.Beta > Fix For: 10.0, 9.2.1 > > > Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen. > ==================== > The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this. > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} > The embedded space in the ParentDirectory property value is problematic. > Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this > {code:java} > <config-property name="ParentDirectory"> > /home/mdrilling/My Dir/data > </config-property> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2016