April 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-425) Add query capabilities to the Import from JDBC in the Designer

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-425?page=com.atlassian.jira.plug... ] Johnathon Lee closed TEIIDDES-425. ---------------------------------- Resolution: Out of Date > Add query capabilities to the Import from JDBC in the Designer > -------------------------------------------------------------- > > Key: TEIIDDES-425 > URL: https://issues.jboss.org/browse/TEIIDDES-425 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Debbie Steigner > Fix For: Future > > > For dealing with databases with extrremely large numbers of tables 10,000 +, it would be very helpful to have these 2 features: > 1. Search / Filter capabilities > 2. Ability to turn off the tables details on the "right" side of the dialog as retrieving that data table by table is exceedingly slow especially when dealing with 1000's of tables. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-257) enhancement to provide better visibility to Request parameters from within the Response document

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-257?page=com.atlassian.jira.plug... ] Johnathon Lee closed TEIIDDES-257. ---------------------------------- Resolution: Out of Date > enhancement to provide better visibility to Request parameters from within the Response document > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-257 > URL: https://issues.jboss.org/browse/TEIIDDES-257 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.0 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: Future > > Attachments: POC.vdb > > > Need a way to pass WS request inputs to an XML response doc that doesn't include them in the response. Requesting an enhancement to provide better visibility to Request parameters from within the Response document. One logical way to do that is to expose them in the Input Set of each mapping class in the Response. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-364) Add the ability to choose the properties that get copied on model creation via wizard

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-364?page=com.atlassian.jira.plug... ] Johnathon Lee closed TEIIDDES-364. ---------------------------------- Resolution: Out of Date > Add the ability to choose the properties that get copied on model creation via wizard > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-364 > URL: https://issues.jboss.org/browse/TEIIDDES-364 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: Future > > > When creating a virtual model from a physical model within the wizard and choosing the option to "copy from existing" all the properties from the physical are copied including native type. This causes an issue if materializing the virtual model to a different database than the source, because we will use the native type if it has a value, instead of translating from the MMx datatype to the appropriate target database type. Request the capability to choose which properties are copied in model creation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-365) Request "Create Relational View from Schema" to include choice elements

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-365?page=com.atlassian.jira.plug... ] Johnathon Lee closed TEIIDDES-365. ---------------------------------- Resolution: Out of Date > Request "Create Relational View from Schema" to include choice elements > ----------------------------------------------------------------------- > > Key: TEIIDDES-365 > URL: https://issues.jboss.org/browse/TEIIDDES-365 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: Future > > > Per request, can the "Create Relational View from Schema" option create columns for choice elements. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-291) XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-291?page=com.atlassian.jira.plug... ] Johnathon Lee closed TEIIDDES-291. ---------------------------------- Resolution: Out of Date > XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-291 > URL: https://issues.jboss.org/browse/TEIIDDES-291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: Ted Jones > Priority: Minor > Fix For: Future > > Attachments: XSDTest7.java > > > See the issue tracker: > https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... > Take a look at section 2.2.2.2 of the XSD spec. > http://www.w3.org/TR/xmlschema-1/ > Or this nice example: > http://www.w3schools.com/Schema/schema_complex_subst.asp > As I read the spec, these substitution groups have no effect on the structure of the XML defined by the XSD, only the names that allowed for a particular element in the XML. > We don't support this in the importer now. We would have to add functionality to find the substitution groups and add additional XPaths so that the connector could either /name or /navn in the xml document. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1306) Feature Request - auto generate primary key for model results

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1306?page=com.atlassian.jira.plu... ] Johnathon Lee closed TEIIDDES-1306. ----------------------------------- Resolution: Out of Date > Feature Request - auto generate primary key for model results > ------------------------------------------------------------- > > Key: TEIIDDES-1306 > URL: https://issues.jboss.org/browse/TEIIDDES-1306 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Debbie Steigner > > When the results from a Metadata model search, return data that doesn't have a natural row identifier > (e.g. results from a web search, where only text is returned) is there a way to auto generate a simple primary key identifier value, e.g. rowid in oracle -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2477) Nullpointer in WSConnectionInfoProvider.java when user is null

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2477?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2477: ---------------------------------------- Designer 9.1 will include this fix and it's slated for a couple of weeks from now. > Nullpointer in WSConnectionInfoProvider.java when user is null > -------------------------------------------------------------- > > Key: TEIIDDES-2477 > URL: https://issues.jboss.org/browse/TEIIDDES-2477 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.6, 9.0 > Environment: Windows 7, JBoss Developer Studio 8.1.0, Teiid Designer 9.0.1.Final > Reporter: Daan Creemers > Assignee: Ted Jones > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > > In the file https://github.com/Teiid-Designer/teiid-designer/blob/9.0.x/plugins/org.t... > @line 101: > if (null != user &! user.equals("")) { //$NON-NLS-1$ > connectionProps.setProperty(ICredentialsCommon.USERNAME_PROP_ID, user); > } > It is not correctly captured that user can be null. No short-circuit operator is used and therefore, the right-hand side of the expression is evaluated which gives a NullPointer if user is null. > Line 101 contains ampersand exclamation mark without a space in between such that short-circuit is not working. ( if (null != user &! user.equals("")) { ) > This should be ( if (null != user && !user.equals("")) { ) > After importing a REST Web Service to create a Source and View model, previewing the data generates the following NullPointer. > java.lang.NullPointerException > at org.teiid.designer.datatools.profiles.ws.WSConnectionInfoProvider.getTeiidRelatedProperties(WSConnectionInfoProvider.java:101) > at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:127) > at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:527) > at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1365) > at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2477) Nullpointer in WSConnectionInfoProvider.java when user is null

by Daan Creemers (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2477?page=com.atlassian.jira.plu... ] Daan Creemers commented on TEIIDDES-2477: ----------------------------------------- Thank you for the update. Where can I download the updated version for Teiid Designer 9.0.x for JBoss Developer Studio 8.1.0? > Nullpointer in WSConnectionInfoProvider.java when user is null > -------------------------------------------------------------- > > Key: TEIIDDES-2477 > URL: https://issues.jboss.org/browse/TEIIDDES-2477 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.6, 9.0 > Environment: Windows 7, JBoss Developer Studio 8.1.0, Teiid Designer 9.0.1.Final > Reporter: Daan Creemers > Assignee: Ted Jones > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > > In the file https://github.com/Teiid-Designer/teiid-designer/blob/9.0.x/plugins/org.t... > @line 101: > if (null != user &! user.equals("")) { //$NON-NLS-1$ > connectionProps.setProperty(ICredentialsCommon.USERNAME_PROP_ID, user); > } > It is not correctly captured that user can be null. No short-circuit operator is used and therefore, the right-hand side of the expression is evaluated which gives a NullPointer if user is null. > Line 101 contains ampersand exclamation mark without a space in between such that short-circuit is not working. ( if (null != user &! user.equals("")) { ) > This should be ( if (null != user && !user.equals("")) { ) > After importing a REST Web Service to create a Source and View model, previewing the data generates the following NullPointer. > java.lang.NullPointerException > at org.teiid.designer.datatools.profiles.ws.WSConnectionInfoProvider.getTeiidRelatedProperties(WSConnectionInfoProvider.java:101) > at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:127) > at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:527) > at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1365) > at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Johnathon Lee updated TEIIDDES-2492: ------------------------------------ Attachment: tst.xml Example file with BOM > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Johnathon Lee > Attachments: tst.xml > > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2492) add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2492?page=com.atlassian.jira.plu... ] Johnathon Lee updated TEIIDDES-2492: ------------------------------------ Attachment: (was: RaveWebServices_metadata_studies_GO29044_versions8994819964405697106.xml) > add the ability to handle the existence of a Byte Order Mark (BOM) during XML File import > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2492 > URL: https://issues.jboss.org/browse/TEIIDDES-2492 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Johnathon Lee > > existence of a BOM ( "\xEF\xBB\xBF" ) will cause an error during the import of an XML file. Can this be accounted for regardless of encoding? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 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 April 2015