[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ]
Juraj Duráni commented on TEIIDDES-2458:
----------------------------------------
Hi,
I thought. But without correct name in source is the source model is useless.
Image customer's scenario:
1. create connection profile for Sybase 15 ASE
2. import source model
3. create and deploy VDB
4. query VDB -> this step will fail as there is incorrect name in source.
> Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2458
> URL: https://issues.jboss.org/browse/TEIIDDES-2458
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Environment: JBDS: 8.0.2GA
> TD: 9.0.1.Final
> OS: Fedora 20
> java: oracle 1.7
> JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502)
> Sybase DB: ASE 15.0.3/EBF
> Reporter: Juraj Duráni
> Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png
>
>
> I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2458:
----------------------------------------
[~jdurani] From your screen caps, the JDBC metadata being displayed in the tree shows *bqt2 > TABLE* rather than *bqt2 > dbo > TABLE* so if the *dbo* schema isn't displayed in the tree, it won't be set as *name in source*.
> Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2458
> URL: https://issues.jboss.org/browse/TEIIDDES-2458
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Environment: JBDS: 8.0.2GA
> TD: 9.0.1.Final
> OS: Fedora 20
> java: oracle 1.7
> JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502)
> Sybase DB: ASE 15.0.3/EBF
> Reporter: Juraj Duráni
> Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png
>
>
> I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2488) Allow UDFs to call Teiid functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2488?page=com.atlassian.jira.plu... ]
Steven Hawkins reassigned TEIIDDES-2488:
----------------------------------------
Description:
Teiid 8.11 adds the ability to define virtual functions using the standard procedure syntax:
create virtual function my-func (param1 string) returns string as
return param1 || 'abc';;
If function class/method metadata is also defined, it will not be used. Only in and a return parameter are supported. There is not yet a restriction on the definition (a single statement is shown above, but could be a block), but following other databases we may limit the type of statements that are allowed.
was:
Currently custom functions require the implementation on be in Java, there could be an alternative way to allow using Teiid expressions inside the custom functions. The related thread is here-
https://developer.jboss.org/thread/251179
Assignee: (was: Steven Hawkins)
> Allow UDFs to call Teiid functions
> ----------------------------------
>
> Key: TEIIDDES-2488
> URL: https://issues.jboss.org/browse/TEIIDDES-2488
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Sanjeev Gour
>
> Teiid 8.11 adds the ability to define virtual functions using the standard procedure syntax:
> create virtual function my-func (param1 string) returns string as
> return param1 || 'abc';;
> If function class/method metadata is also defined, it will not be used. Only in and a return parameter are supported. There is not yet a restriction on the definition (a single statement is shown above, but could be a block), but following other databases we may limit the type of statements that are allowed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ]
Kylin Soong updated TEIIDDES-2487:
----------------------------------
Description:
issue
====
Create Relational Model from SOAP service validation failed with "No Columns defined error"
Reproduce
========
1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
Enhancement
==========
1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
2. Simplify XML document modeling related operation - current wizard not user-friendly, web should do some enhancement in request/response xml document modeling.
3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier.
[1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
[2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
was:
issue
====
Create Relational Model from SOAP service validation failed with "No Columns defined error"
Reproduce
========
1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
Enhancement
==========
1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
2. Simplify XML document modeling related operation - I think if these wizards offer XML document modeling like structure for mapping, that may help user experience.
3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier.
[1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
[2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
> Teidd Designer Import SOAP Relational Model Mapping No Columns defined
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2487
> URL: https://issues.jboss.org/browse/TEIIDDES-2487
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png
>
>
> issue
> ====
> Create Relational Model from SOAP service validation failed with "No Columns defined error"
> Reproduce
> ========
> 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
> 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
> Enhancement
> ==========
> 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
> 2. Simplify XML document modeling related operation - current wizard not user-friendly, web should do some enhancement in request/response xml document modeling.
> 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier.
> [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
> [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ]
Kylin Soong updated TEIIDDES-2487:
----------------------------------
Description:
issue
====
Create Relational Model from SOAP service validation failed with "No Columns defined error"
Reproduce
========
1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
Enhancement
==========
1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
2. Simplify XML document modeling related operation - I think if these wizards offer XML document modeling like structure for mapping, that may help user experience.
3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier.
[1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
[2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
was:
issue
====
Create Relational Model from SOAP service validation failed with "No Columns defined error"
Reproduce
========
1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
Enhancement
==========
1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
2. Simplify XML document modeling related operation - I think if these wizards offer XML document modeling like structure for mapping, that may help user experience.
3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also
some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier
[1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
[2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
> Teidd Designer Import SOAP Relational Model Mapping No Columns defined
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2487
> URL: https://issues.jboss.org/browse/TEIIDDES-2487
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png
>
>
> issue
> ====
> Create Relational Model from SOAP service validation failed with "No Columns defined error"
> Reproduce
> ========
> 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
> 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
> Enhancement
> ==========
> 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
> 2. Simplify XML document modeling related operation - I think if these wizards offer XML document modeling like structure for mapping, that may help user experience.
> 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier.
> [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
> [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ]
Kylin Soong updated TEIIDDES-2487:
----------------------------------
Description:
issue
====
Create Relational Model from SOAP service validation failed with "No Columns defined error"
Reproduce
========
1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
Enhancement
==========
1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
2. Simplify XML document modeling related operation - I think if these wizards offer XML document modeling like structure for mapping, that may help user experience.
3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also
some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier
[1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
[2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
was:
## issue
Create Relational Model from SOAP service validation failed with "No Columns defined error"
> Teidd Designer Import SOAP Relational Model Mapping No Columns defined
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2487
> URL: https://issues.jboss.org/browse/TEIIDDES-2487
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png
>
>
> issue
> ====
> Create Relational Model from SOAP service validation failed with "No Columns defined error"
> Reproduce
> ========
> 1. deploy attached StateService to JBoss DV 6.1(assume it DV run on localhost), WSDL File can be viewed via [2]
> 2. Use attached 4 pics to import SOAP Web Service will reproduce the issue(teiid-designer-ws-3.png and teiid-designer-ws-4.png show validation errors)
> Enhancement
> ==========
> 1. Simplify the import wizard - from a user's perspective, I think the main obstacle is the wizard is too complex, especially SOAP, federation related wizard, it's very difficult to operate without a step by step documents.
> 2. Simplify XML document modeling related operation - I think if these wizards offer XML document modeling like structure for mapping, that may help user experience.
> 3. Simplify vdb archive structure - the Designer generated vdb is more complexed compared with dynamic vdb, it have more definition files(sources.xmi, views.xmi, vdb.xml), there also
> some metamatrix link like [2] exist in .xmi, actually these links not really exist, if we remove these kinds of things, the designer wizard logic may be more easier
> [1] http://localhost:8080/StateService/stateService/StateServiceImpl?WSDL
> [2] http://www.metamatrix.com/metamodels/SimpleDatatypes-instance#XMLLiteral
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2487) Teidd Designer Import SOAP Relational Model Mapping No Columns defined
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2487?page=com.atlassian.jira.plu... ]
Kylin Soong updated TEIIDDES-2487:
----------------------------------
Description:
## issue
Create Relational Model from SOAP service validation failed with "No Columns defined error"
was:Create Relational Model from SOAP service validation failed with "No Columns defined error"
> Teidd Designer Import SOAP Relational Model Mapping No Columns defined
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2487
> URL: https://issues.jboss.org/browse/TEIIDDES-2487
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Kylin Soong
> Attachments: StateService.jar, teiid-designer-ws-1.png, teiid-designer-ws-2.png, teiid-designer-ws-3.png, teiid-designer-ws-4.png
>
>
> ## issue
> Create Relational Model from SOAP service validation failed with "No Columns defined error"
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years