[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
> 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, out.webm, sample.csv
>
>
> 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.11#6341)
9 years, 11 months
[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 commented on TEIIDDES-1037:
----------------------------------------
Added call to setIncludeSkip() when calling setIncludeTypeLine(boolean) so the values are completely set up when profile changes.
https://github.com/Teiid-Designer/teiid-designer/commit/9b2a8fbb3a4d00a1a...
committed to master, 9.0.x and 8.6.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: 9.0, 8.6.1, 9.0.1
>
> Attachments: FlatFileDataTypes_NOT.png, out.webm, sample.csv
>
>
> 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.11#6341)
9 years, 11 months
[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:
------------------------------------
Still having issue with SKIP X not being added to SQL if user defines CP via URL and checking "Second line types" option.
> 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: 9.0, 8.6.1, 9.0.1
>
> Attachments: FlatFileDataTypes_NOT.png, out.webm, sample.csv
>
>
> 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.11#6341)
9 years, 11 months
[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-1037:
-----------------------------------
Attachment: out.webm
How to reproduce my issue - video
> 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: 9.0, 8.6.1, 9.0.1
>
> Attachments: FlatFileDataTypes_NOT.png, out.webm, sample.csv
>
>
> 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.11#6341)
9 years, 11 months
[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:
-----------------------------------
Attachment: sample.csv
> 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: 9.0, 8.6.1, 9.0.1
>
> Attachments: FlatFileDataTypes_NOT.png, sample.csv
>
>
> 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.11#6341)
9 years, 11 months