[JBoss JIRA] (TEIIDDES-2418) Converting all source symbol data types not reflected in Type Resolver
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2418?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2418:
--------------------------------------
Assignee: Mark Drilling
> Converting all source symbol data types not reflected in Type Resolver
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2418
> URL: https://issues.jboss.org/browse/TEIIDDES-2418
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs, Transformations
> Affects Versions: 9.0.2
> Reporter: Andrej Šmigala
> Assignee: Mark Drilling
> Priority: Minor
> Fix For: 9.1, 9.0.2, 8.6.2
>
> Attachments: TyperesolverProject.zip
>
>
> When using the Type Resolver, clicking the Convert all source SQL symbol datatypes does not show the changed expression in the Source SQL Symbol column. Other than that, it works as expected, i.e. the type conflict message goes away, and after clicking OK, the Reconciller actually contains the correct CONVERT statements.
> However, clicking the left arrows for each column correctly changes the Source SQL Symbol.
> Clicking Change all target column datatypes shows similar behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2389) Add ui support for whole texttable no trim
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2389?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2389:
-----------------------------------
Component/s: Import/Export
> Add ui support for whole texttable no trim
> ------------------------------------------
>
> Key: TEIIDDES-2389
> URL: https://issues.jboss.org/browse/TEIIDDES-2389
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Environment: Teiid 8.8.0 Final
> Reporter: Shiveeta Mattoo
> Assignee: Barry LaFond
> Labels: File-connector, TEXTTABLE, TRIM
> Fix For: 9.1
>
>
> TEIID-3167 allows for NO TRIM to be specified against the whole texttable regardless of whether it is fixed width or delimited. If delimited, then unqualified entries will not be trimmed. For example:
> a , "b"
> would be parsed as
> a ,b - such that the space is preserved after a, but the qualified entry is unaffected.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2389) Add ui support for whole texttable no trim
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2389?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2389:
--------------------------------------
Assignee: Barry LaFond
> Add ui support for whole texttable no trim
> ------------------------------------------
>
> Key: TEIIDDES-2389
> URL: https://issues.jboss.org/browse/TEIIDDES-2389
> Project: Teiid Designer
> Issue Type: Enhancement
> Environment: Teiid 8.8.0 Final
> Reporter: Shiveeta Mattoo
> Assignee: Barry LaFond
> Labels: File-connector, TEXTTABLE, TRIM
> Fix For: 9.1
>
>
> TEIID-3167 allows for NO TRIM to be specified against the whole texttable regardless of whether it is fixed width or delimited. If delimited, then unqualified entries will not be trimmed. For example:
> a , "b"
> would be parsed as
> a ,b - such that the space is preserved after a, but the qualified entry is unaffected.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2405:
--------------------------------------
Assignee: Mark Drilling
> Teiid Importer *MUST* not require class-name property working with Teiid Sources
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2405
> URL: https://issues.jboss.org/browse/TEIIDDES-2405
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 9.1, 9.0.2
>
>
> When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source
> {code}
> {"managedconnectionfactory-class" => {
> "type" => STRING,
> "display" => "managedconnectionfactory-class",
> "read-only" => "true",
> "advanced" => "true",
> "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory"
> }},
> {code}
> That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2405:
-----------------------------------
Fix Version/s: 9.0.2
> Teiid Importer *MUST* not require class-name property working with Teiid Sources
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2405
> URL: https://issues.jboss.org/browse/TEIIDDES-2405
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Priority: Critical
> Fix For: 9.1, 9.0.2
>
>
> When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source
> {code}
> {"managedconnectionfactory-class" => {
> "type" => STRING,
> "display" => "managedconnectionfactory-class",
> "read-only" => "true",
> "advanced" => "true",
> "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory"
> }},
> {code}
> That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-2429:
-------------------------------------------
I never said it couldn't be done. I said it would not be done in the released Designer 9.0. During the normal course of releases, tested support for Teiids 8.8 and 8.9 will be in Designer 9.1. Currently, looking with @blafond at allowing minimal support for untested new versions of Teiid (8.10), probably aimed at inclusion in 9.0.2.
> Teiid Designer do not compatible with Teiid 8.10
> ------------------------------------------------
>
> Key: TEIIDDES-2429
> URL: https://issues.jboss.org/browse/TEIIDDES-2429
> Project: Teiid Designer
> Issue Type: Bug
> Components: Diagrams
> Affects Versions: 9.0
> Environment: Teiid 8.10.Beta2
> JBDS 8.0(https://devstudio.jboss.com/updates/8.0/integration-stack/)
> Reporter: Kylin Soong
> Priority: Critical
>
> Import Metadata from JDBC Data source through the following error:
> Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
> at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
> at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2215)
> Does this should be a feature request?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years