[JBoss JIRA] (TEIIDDES-2705) Teiid designer does not take the overriden translator
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2705?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2705 at 10/30/15 1:17 PM:
------------------------------------------------------------------
Designer allows you to define Translator Overrides via the *Translator Overrides* tab in the *Advanced* tab (VDB Editor)
[~jietao] Once you define your override (unique name), that value will be available to select/change in the *Source Binding Definition* panel in the *Models* tab.
There should now be an override element in your manifest (vdb.xml) file in your archive like:
{code:xml}
<translator name="my_db2" type="db2" description="My translator override for DB2 Parts Supplier Only"/>
{code}
was (Author: blafond):
Designer allows you to define Translator Overrides via the *Translator Overrides* tab in the *Advanced* tab (VDB Editor)
[~jietao] Once you define your override (unique name), that value will be available to select/change in the *Source Binding Definition* panel in the *Models* tab.
There should now be an override element in your manifest (vdb.xml) file in your archive like:
{code:xml}
<translator name="my_db2" type="db2" description="My translator override for DB2 Parts Supplier Only"/>
{code}
> Teiid designer does not take the overriden translator
> -----------------------------------------------------
>
> Key: TEIIDDES-2705
> URL: https://issues.jboss.org/browse/TEIIDDES-2705
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: jie tao
> Priority: Optional
>
> in the VDB editor, an overriden translator can be defined, but in vdb.xml the default one is still used. No way to tell Designer to take the overriden one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2705) Teiid designer does not take the overriden translator
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2705?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2705 at 10/30/15 1:00 PM:
------------------------------------------------------------------
Designer allows you to define Translator Overrides via the *Translator Overrides* tab in the *Advanced* tab (VDB Editor)
[~jietao] Once you define your override (unique name), that value will be available to select/change in the *Source Binding Definition* panel in the *Models* tab.
There should now be an override element in your manifest (vdb.xml) file in your archive like:
{code:xml}
<translator name="my_db2" type="db2" description="My translator override for DB2 Parts Supplier Only"/>
{code}
was (Author: blafond):
Designer allows you to define Translator Overrides via the *Translator Overrides* tab in the *Advanced* tab (VDB Editor)
Once you define your override (unique name), that value will be available to select/change in the *Source Binding Definition* panel in the *Models* tab.
There should now be an override element in your manifest (vdb.xml) file in your archive like:
{code:xml}
<translator name="my_db2" type="db2" description="My translator override for DB2 Parts Supplier Only"/>
{code}
> Teiid designer does not take the overriden translator
> -----------------------------------------------------
>
> Key: TEIIDDES-2705
> URL: https://issues.jboss.org/browse/TEIIDDES-2705
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: jie tao
> Priority: Optional
>
> in the VDB editor, an overriden translator can be defined, but in vdb.xml the default one is still used. No way to tell Designer to take the overriden one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2705) Teiid designer does not take the overriden translator
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2705?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2705:
----------------------------------------
Designer allows you to define Translator Overrides via the *Translator Overrides* tab in the *Advanced* tab (VDB Editor)
Once you define your override (unique name), that value will be available to select/change in the *Source Binding Definition* panel in the *Models* tab.
There should now be an override element in your manifest (vdb.xml) file in your archive like:
{code:xml}
<translator name="my_db2" type="db2" description="My translator override for DB2 Parts Supplier Only"/>
{code}
> Teiid designer does not take the overriden translator
> -----------------------------------------------------
>
> Key: TEIIDDES-2705
> URL: https://issues.jboss.org/browse/TEIIDDES-2705
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: jie tao
> Priority: Optional
>
> in the VDB editor, an overriden translator can be defined, but in vdb.xml the default one is still used. No way to tell Designer to take the overriden one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2414) Large transformation SQL is not exported to INDEX file.
by hisao furuichi (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2414?page=com.atlassian.jira.plu... ]
hisao furuichi commented on TEIIDDES-2414:
------------------------------------------
Hello Barry.
I'm working with Hisanobu.
Customer uses Teiid Designer 9.0.3.Final-v20150810-1438-B1157.
Thx
> Large transformation SQL is not exported to INDEX file.
> -------------------------------------------------------
>
> Key: TEIIDDES-2414
> URL: https://issues.jboss.org/browse/TEIIDDES-2414
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3.4
> Reporter: Hisanobu Okuda
> Assignee: Paul Richardson
> Fix For: 9.3, 9.3.1
>
> Attachments: test.csv
>
>
> A large transformation SQL of a view model is not exported to INDEX file.
> I have a large transformation SQL > 8192 bytes in my view model. TDesigner fails to convert the xmi to XXXXXXXXXX.INDEX file. There is no transformation SQL in the INDEX file, therefore, deploying my vdb fails and the vdb is inactivated. When you deploy the vdb, you can see the following message in a log file:-
> {code}
> 17:16:11,632 WARN [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31079 View ViewModel.new_table is not defined by a query expression.
> 17:16:11,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata for the VDB test.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
> 17:16:11,637 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB test.1 is set to FAILED
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2660) Add support in Designer for foreign keys cross models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2660?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2660:
----------------------------------------
[~vhalbert] Should be possible
> Add support in Designer for foreign keys cross models
> -----------------------------------------------------
>
> Key: TEIIDDES-2660
> URL: https://issues.jboss.org/browse/TEIIDDES-2660
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Add support in Designer for foreign keys cross models.
> In Designer you cannot have a FK cross models. That is not a limitation with DDL metadata in Teiid. It's a misstatement to relate that to optimization. If the PK/FK is present we'll use that information just as we would in a single source - we do not however enforce the FK. That can be done through the use of an update procedure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2660) Add support in Designer for foreign keys cross models
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2660?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2660:
---------------------------------------
Barry,
Can this be done?
> Add support in Designer for foreign keys cross models
> -----------------------------------------------------
>
> Key: TEIIDDES-2660
> URL: https://issues.jboss.org/browse/TEIIDDES-2660
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Add support in Designer for foreign keys cross models.
> In Designer you cannot have a FK cross models. That is not a limitation with DDL metadata in Teiid. It's a misstatement to relate that to optimization. If the PK/FK is present we'll use that information just as we would in a single source - we do not however enforce the FK. That can be done through the use of an update procedure though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIIDDES-2589) The model extension definition "relational" found in model is a different version than the one in the registry.
by Jean-Pierre Matsumoto (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2589?page=com.atlassian.jira.plu... ]
Jean-Pierre Matsumoto commented on TEIIDDES-2589:
-------------------------------------------------
We had same issue "The name is invalid. The character '.' (at position 10) is not allowed". We have fixed by renaming my.table.name to my_table_name. HTH
> The model extension definition "relational" found in model is a different version than the one in the registry.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2589
> URL: https://issues.jboss.org/browse/TEIIDDES-2589
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0, 9.0.1, 9.1, 9.0.2
> Reporter: Lukas Mro
>
> After importing model from TD 8.1.0 to 9.X.X two types of errors occures
> 3 types of errors occures:
> 1. The model extension definition "rest" found in model is not registered in workspace -> this one can be autofix
> 2. The model extension definition "relational" found in model is a different version than the one in the registry -> This one do not have fix
> 3. java.lang.StringIndexOutOfBoundsException: String index out of range: 1
> -> this one do not have fix
> I`m not sure what should i send you, AMA :)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months