[JBoss JIRA] (TEIIDDES-2343) Support importing Dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2343?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2343:
----------------------------------------
Teiid Admin VDB api does provide access to a model element <metadata> via a getSchemaText() method, however, it's a simple String and would need to get parsed. The DDL segments of that string can be handled via our DDL parser, but the wrapper CDATA would need to get pulled out.
> Support importing Dynamic VDB
> -----------------------------
>
> Key: TEIIDDES-2343
> URL: https://issues.jboss.org/browse/TEIIDDES-2343
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> There should be an import option that supports importing a dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (TEIIDDES-2343) Support importing Dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2343?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2343:
----------------------------------------
The Dynamic VDB defined via Web Tooling, usually includes simple <source> entries defining the JNDI/translator info for a source and <model> entries that define *CDATA* containining *VIEWS* which can be simple or complex and contain the user's transformation (i.e SQL).
The Admin API provides a *getSchema()* method which returns DDL, but treats ALL of this metadata as *source* metadata, hence on importing through Teiid Connection, the user's *transformation SQL* is not provided.
So their is no current capability to fully transfer the user's Dynamic VDB (from the Web-Tooling) through the Teiid Runtime.
> Support importing Dynamic VDB
> -----------------------------
>
> Key: TEIIDDES-2343
> URL: https://issues.jboss.org/browse/TEIIDDES-2343
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> There should be an import option that supports importing a dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (TEIIDDES-2344) Empty error message in insert procedure transformation
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2344?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2344:
----------------------------------
Assignee: Barry LaFond
> Empty error message in insert procedure transformation
> ------------------------------------------------------
>
> Key: TEIIDDES-2344
> URL: https://issues.jboss.org/browse/TEIIDDES-2344
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 8.6
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
>
> When creating a virtual insert procedure and omitting a non-nullable column from the insert, the error message is simply
> {quote}ERROR: ERROR{quote}
> E. g. I have a PUBLISHERS table with three columns, of which PUBLISHER_ID is NOT NULL, the insert procedure is
> {code:sql}
> FOR EACH ROW
> BEGIN ATOMIC
> INSERT INTO Books.PUBLISHERS (Books.PUBLISHERS.NAME) VALUES ("NEW".NAME);
> END
> {code}
> The error in previous versions of Designer for the same procedure would be
> {quote}
> ERROR: Element Books.PUBLISHERS.PUBLISHER_ID of books.publishers is neither nullable nor has a default value. A value must be specified in the insert.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (TEIIDDES-1998) Connection Profile loses Binding Type
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1998?page=com.atlassian.jira.plu... ]
Matus Makovy resolved TEIIDDES-1998.
------------------------------------
Resolution: Done
In 8.3.4.Final is everything OK.
> Connection Profile loses Binding Type
> -------------------------------------
>
> Key: TEIIDDES-1998
> URL: https://issues.jboss.org/browse/TEIIDDES-1998
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration, Modeling
> Affects Versions: 8.3
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.3.4, 8.6
>
> Attachments: screen1.png, screen2.png
>
>
> Whenever importing WSDL into Source model, the connection profile loses it's binding info and I am required to edit the CP and add the binding info with each import. We should find a way to persist it or some other way to get the binding for import.
> The error is: "Connection Profile is invalid since it does not contain the required property DefaultBinding".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (TEIIDDES-2345) Using VARIABLES.ROWCOUNT in update procedure causes validation error
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIIDDES-2345:
----------------------------------------
Summary: Using VARIABLES.ROWCOUNT in update procedure causes validation error
Key: TEIIDDES-2345
URL: https://issues.jboss.org/browse/TEIIDDES-2345
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 8.6
Reporter: Andrej Šmigala
Trying to get the number of affected rows in the update/insert/delete procedure of a view table by using the VARIABLES.ROWCOUNT variable causes the following error:
{quote}ERROR: TEIID31118 Element "VARIABLES.ROWCOUNT" is not defined by any relevant group.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (TEIIDDES-2344) Empty error message in insert procedure transformation
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2344?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-2344:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1144324
> Empty error message in insert procedure transformation
> ------------------------------------------------------
>
> Key: TEIIDDES-2344
> URL: https://issues.jboss.org/browse/TEIIDDES-2344
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 8.6
> Reporter: Andrej Šmigala
> Priority: Minor
>
> When creating a virtual insert procedure and omitting a non-nullable column from the insert, the error message is simply
> {quote}ERROR: ERROR{quote}
> E. g. I have a PUBLISHERS table with three columns, of which PUBLISHER_ID is NOT NULL, the insert procedure is
> {code:sql}
> FOR EACH ROW
> BEGIN ATOMIC
> INSERT INTO Books.PUBLISHERS (Books.PUBLISHERS.NAME) VALUES ("NEW".NAME);
> END
> {code}
> The error in previous versions of Designer for the same procedure would be
> {quote}
> ERROR: Element Books.PUBLISHERS.PUBLISHER_ID of books.publishers is neither nullable nor has a default value. A value must be specified in the insert.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (TEIIDDES-2344) Empty error message in insert procedure transformation
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIIDDES-2344:
----------------------------------------
Summary: Empty error message in insert procedure transformation
Key: TEIIDDES-2344
URL: https://issues.jboss.org/browse/TEIIDDES-2344
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 8.6
Reporter: Andrej Šmigala
Priority: Minor
When creating a virtual insert procedure and omitting a non-nullable column from the insert, the error message is simply
{quote}ERROR: ERROR{quote}
E. g. I have a PUBLISHERS table with three columns, of which PUBLISHER_ID is NOT NULL, the insert procedure is
{code:sql}
FOR EACH ROW
BEGIN ATOMIC
INSERT INTO Books.PUBLISHERS (Books.PUBLISHERS.NAME) VALUES ("NEW".NAME);
END
{code}
The error in previous versions of Designer for the same procedure would be
{quote}
ERROR: Element Books.PUBLISHERS.PUBLISHER_ID of books.publishers is neither nullable nor has a default value. A value must be specified in the insert.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months