December 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2299) LDAP import dialog very slow

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2299?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2299: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1131437|https://bugzilla.redhat.com/show_bug.cgi?id=1131437] from NEW to MODIFIED > LDAP import dialog very slow > ---------------------------- > > Key: TEIIDDES-2299 > URL: https://issues.jboss.org/browse/TEIIDDES-2299 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3.3 > Environment: JBDS 7.1.1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Fix For: 8.6.1, 9.0.1, 9.0 > > > In the LDAP import dialog in steps "Select the LDAP entries to be modelled as tables" and "Select the LDAP attributes to be modelled as table columns", checkboxes only change their state about one second after they are clicked. > Also, typing anything into e. g. Column Name input takes several seconds. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2299) LDAP import dialog very slow

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2299?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2299: ----------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/423 > LDAP import dialog very slow > ---------------------------- > > Key: TEIIDDES-2299 > URL: https://issues.jboss.org/browse/TEIIDDES-2299 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3.3 > Environment: JBDS 7.1.1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Fix For: 8.6.1, 9.0.1, 9.0 > > > In the LDAP import dialog in steps "Select the LDAP entries to be modelled as tables" and "Select the LDAP attributes to be modelled as table columns", checkboxes only change their state about one second after they are clicked. > Also, typing anything into e. g. Column Name input takes several seconds. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2299) LDAP import dialog very slow

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2299?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2299. ------------------------------------ Resolution: Done merged into 9.0.x. and also committed to 8.6.x and master. > LDAP import dialog very slow > ---------------------------- > > Key: TEIIDDES-2299 > URL: https://issues.jboss.org/browse/TEIIDDES-2299 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3.3 > Environment: JBDS 7.1.1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Fix For: 8.6.1, 9.0.1, 9.0 > > > In the LDAP import dialog in steps "Select the LDAP entries to be modelled as tables" and "Select the LDAP attributes to be modelled as table columns", checkboxes only change their state about one second after they are clicked. > Also, typing anything into e. g. Column Name input takes several seconds. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2403) Relax BIRT version range to 4.4.0 from 4.4.1

by Paul Leacu (JIRA)

Paul Leacu created TEIIDDES-2403: ------------------------------------ Summary: Relax BIRT version range to 4.4.0 from 4.4.1 Key: TEIIDDES-2403 URL: https://issues.jboss.org/browse/TEIIDDES-2403 Project: Teiid Designer Issue Type: Task Components: Teiid Integration Affects Versions: 9.0.1 Reporter: Paul Leacu Assignee: Barry LaFond Priority: Blocker The JBT unified TP 4.41.0.Final pulls in BIRT 4.4.0. It can't pull in BIRT 4.4.1 until after SR1 goes final. The associated JBTIS/ JBDSIS TPs must back off to 4.4.0 (from 4.4.1) its BIRT plugins if we want to install into Eclipse SR0 cleanly or we will have to forge an Eclipse SR1 remediation dialog for it (messy). So - since JBTIS TP must go .Final before we can legally pull in a 4.4.1 Birt, please: Update meta-data ranges and feature references of BIRT 4.4.1 to use/include 4.4.0. Thanks! -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1037: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1093210|https://bugzilla.redhat.com/show_bug.cgi?id=1093210] from ASSIGNED to MODIFIED > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.6.1, 9.0.1, 9.0 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1037. ------------------------------------ Resolution: Done removed explicit conversion of an *integer* type to *int* type when parsing Flat File datatype line. committed to master, 8.6.x and 9.0.x > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.6.1, 9.0.1, 9.0 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1037: ----------------------------------- Fix Version/s: 9.0.1 > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.6.1, 9.0.1, 9.0 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] Barry LaFond reopened TEIIDDES-1037: ------------------------------------ issue with integer datatypes in generated SQL > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.6.1, 9.0 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2014