[JBoss JIRA] (TEIIDDES-1388) Improve Flat File importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1388?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1388.
------------------------------------
Resolution: Out of Date
We've implemented most of these suggestions during 8.x development.
> Improve Flat File importer
> --------------------------
>
> Key: TEIIDDES-1388
> URL: https://issues.jboss.org/browse/TEIIDDES-1388
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 7.7, 7.7.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: Future
>
>
> The Flat File importer still lacks simplicity. Need to spend another cycle improving usability
> PAUL NITTEL wrote:
> I'm tinkering with this thing and have a few suggestions. (The problem with coming up with cool wizardly things is they spark other synapses thereby creating an endless flow of work.)
> The Create Teiid Flat File Connection action seems to be a mixture of building the data source connection and laying the groundwork for the transformation (like where are the column name and types). Moving this to the Create Source Model wizard might make it easier and flow better for the user.
> Rather than checkboxes that presume much about how flat file data may be constructed, how about allowing the user to tell you which lines are contain heading and type info (if any, of course)? In the case of my weird data file, there a comment in line 1, line 2 is blank, line 3 have column names and line 4 has types. Data starts in line 5.
> I realize my case is atypical, but might be worth consideration. ;-)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2429) Teiid Designer do not compatible with Teiid 8.10
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2429?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2429:
------------------------------------------
> Of course, if Teiid would like to align their release schedule with Designer then we can ensure that the next released version is always integrated?
That is not necessary. What we are saying is that Designer should relax it's compatibility check to allow some forward usage. There can be a big dialog about potential issues, but to prevent it altogether seems unnecessary as we attempt to maintain backwards compatibility - especially at an artifact level. There will of course be issues - such as connecting an earlier Designer to an 8.11 runtime with the TEIID-3372 change as that will require a modification on the Designer side to view the metadata elements in a vdb properly. However just deploying and querying with an older client as Ramesh says should be compatible.
> 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
> Fix For: 9.1, 9.0.2
>
>
> 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)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2445) Set connection profile action uses wrong driver info.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2445?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2445:
----------------------------------------
Looks like the Data Tools project isn't updating their ProfileManager's cache of connection profiles. and the driver properties aren't necessarily passed on the each connection profile base properties list.
This is going to have to be a minor known issue.
> Set connection profile action uses wrong driver info.
> -----------------------------------------------------
>
> Key: TEIIDDES-2445
> URL: https://issues.jboss.org/browse/TEIIDDES-2445
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration
> Affects Versions: 8.6.1
> Environment: JBDS: 7.1.1.GA
> TD: 8.6.1.CR1
> OS: Win 7
> Reporter: Juraj Duráni
> Assignee: Barry LaFond
> Fix For: Future
>
>
> If a new connection profile is imported (Database Development > Data Source explorer > Import) and its driver is changed afterward (jar list), then Set Connection Profile action sets connection profile to a source model with old jar-list-paths.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2445) Set connection profile action uses wrong driver info.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2445?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2445:
-----------------------------------
Fix Version/s: Future
(was: 8.6.2)
(was: 9.1)
(was: 9.0.2)
> Set connection profile action uses wrong driver info.
> -----------------------------------------------------
>
> Key: TEIIDDES-2445
> URL: https://issues.jboss.org/browse/TEIIDDES-2445
> Project: Teiid Designer
> Issue Type: Bug
> Components: Datatools Integration
> Affects Versions: 8.6.1
> Environment: JBDS: 7.1.1.GA
> TD: 8.6.1.CR1
> OS: Win 7
> Reporter: Juraj Duráni
> Assignee: Barry LaFond
> Fix For: Future
>
>
> If a new connection profile is imported (Database Development > Data Source explorer > Import) and its driver is changed afterward (jar list), then Set Connection Profile action sets connection profile to a source model with old jar-list-paths.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2440) No proper column mapping for second primary key in view model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2440?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2440:
----------------------------------------
Committed to master: https://github.com/Teiid-Designer/teiid-designer/commit/b26bd52bd877a9600...
> No proper column mapping for second primary key in view model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2440
> URL: https://issues.jboss.org/browse/TEIIDDES-2440
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3.4, 8.6
> Environment: Windows
> Reporter: Endy Brosens
> Assignee: Barry LaFond
> Fix For: 9.1, 9.0.2, 8.6.2
>
> Attachments: property-not-supported.png, TEIIDDES-2440-workaround.png
>
>
> I have a source relational model where some entities I want to expose via OData REST don't have a primary key. As you know, teiid OData support will not expose a given entity via REST unless the entity has either a primary key or unique constraint defined.
>
> I also have a view model defined where i transform some entity names to make them more REST API resource model "friendly". This view model is also where I want to define some primary keys for entities in the source model that don't have primary keys.
>
> I can define a primary key set on one given entity in my view model, but when I try to define a primary key set on a second entity in the view model the columns that are available for selection are those related to the first given entity I defined a primary key for. It would seem that one should only be able to select columns that are associated with the entity you're working with.
>
> This occurs on teiid designer 8.3.4.Final, 8.6, teiid 8.7, on windows.
> The workaround is to edit the View Model in the Standard Eclipse XML Editor and assign column GUID's to the Primary Key XML element.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months