[JBoss JIRA] Created: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
12:03 p.m.
Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat
File connection profile and targets Teiid formatted source table files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Fix For: 7.5
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
- Would be filtered to be only select & edit Flat File Source connection profiles
- Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
- User could pick and choose (check-boxes) what tables, procedures, etc... to create
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1017:
----------------------------------------
Added UI Mockup: <ImportTeiidMetadata Wizard>
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Fix For: 7.5
Attachments: ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
- Would be filtered to be only select & edit Flat File Source connection
profiles
- Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
- User could pick and choose (check-boxes) what tables, procedures, etc... to create
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:16 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Description:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the virtual procedures containing the
canned complex SQL which contains the FILE funtions that require the table, column info
was:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
- Would be filtered to be only select & edit Flat File Source connection profiles
- Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
- User could pick and choose (check-boxes) what tables, procedures, etc... to create
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
> Create "Metadata from Teiid Metadata File" import option which utilizes DTP
Flat File connection profile and targets Teiid formatted source table files
>
--------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1017
> URL: https://issues.jboss.org/browse/TEIIDDES-1017
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Fix For: 7.5
>
> Attachments: ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata Wizard.png
>
>
> To improve usability of File connectors, users need the ability to import from a
Teiid Source file via the import wizard.
> 1) Add an new import option > "Metadata from Teiid Metadata File"
> 2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> >> Would be filtered to be only select & edit Flat File Source
connection profiles
> >> Connection profile points to folder on file system
> 3) Page 2 would show summary of what Metadata objects are available
> > User could pick and choose (check-boxes) what tables, procedures,
etc... to use
> 4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
> 5) Page 4 (if update) to show differences
> Relational model would be generated that contains the standard File connector
procedures
> Virtual Model would be created (or selected) where the virtual procedures containing
the canned complex SQL which contains the FILE funtions that require the table, column
info
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 p.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1017:
----------------------------------------
Edited UI Mockup <ImportTeiidMetadata Wizard>: Added View Model selector/definition
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Fix For: 7.5
Attachments: ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata Wizard.bmml,
ImportTeiidMetadata Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the virtual procedures containing the
canned complex SQL which contains the FILE funtions that require the table, column info
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:34 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: EmpData.txt
Our standard text source example file - Employees
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the virtual procedures containing the
canned complex SQL which contains the FILE funtions that require the table, column info
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:58 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: ImportTeiidMetadata Wizard.bmml)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the virtual procedures containing the
canned complex SQL which contains the FILE funtions that require the table, column info
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:06 p.m.
New subject: [JBoss JIRA] Assigned: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond reassigned TEIIDDES-1017:
--------------------------------------
Assignee: Mark Drilling
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Mark Drilling
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the virtual procedures containing the
canned complex SQL which contains the FILE funtions that require the table, column info
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:47 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Description:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
was:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the virtual procedures containing the
canned complex SQL which contains the FILE funtions that require the table, column info
> Create "Metadata from Teiid Metadata File" import option which utilizes DTP
Flat File connection profile and targets Teiid formatted source table files
>
--------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1017
> URL: https://issues.jboss.org/browse/TEIIDDES-1017
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 7.5
>
> Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml,
ImportTeiidMetadata Wizard.png
>
>
> To improve usability of File connectors, users need the ability to import from a
Teiid Source file via the import wizard.
> 1) Add an new import option > "Metadata from Teiid Metadata File"
> 2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> >> Would be filtered to be only select & edit Flat File Source
connection profiles
> >> Connection profile points to folder on file system
> 3) Page 2 would show summary of what Metadata objects are available
> > User could pick and choose (check-boxes) what tables, procedures,
etc... to use
> 4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
> 5) Page 4 (if update) to show differences
> Relational model would be generated that contains the standard File connector
procedures
> Virtual Model would be created (or selected) where the view tables containing the
canned complex SQL which contains the FILE functions that require the table, column info.
> EXAMPLE:
> ==========================================================
> SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
> (EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f,
TEXTTABLE(file COLUMNS lastName string, firstName string, middleName string, empId
biginteger, department string, annualSalary double, title string, homePhone string, mgrId
biginteger, street string, city string, state string, ZipCode string HEADER 3) AS emp
> ==========================================================
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:38 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1017:
----------------------------------------
Edited UI Mockup <ImportTeiidMetadata Wizard>: Added additional file configuration
dialog and concept of multiple data files
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Mark Drilling
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:40 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: ImportTeiidMetadata Wizard.bmml)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Mark Drilling
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:16 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1017:
----------------------------------------
Edited UI Mockup <ImportTeiidMetadata Wizard>: Added View Name to first page
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Mark Drilling
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:18 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: ImportTeiidMetadata Wizard.bmml)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Mark Drilling
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Description:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
was:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
> Create "Metadata from Teiid Metadata File" import option which utilizes DTP
Flat File connection profile and targets Teiid formatted source table files
>
--------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1017
> URL: https://issues.jboss.org/browse/TEIIDDES-1017
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 7.5
>
> Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml,
ImportTeiidMetadata Wizard.png
>
>
> To improve usability of File connectors, users need the ability to import from a
Teiid Source file via the import wizard.
> 1) Add an new import option > "Metadata from Teiid Metadata File"
> 2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> >> Would be filtered to be only select & edit Flat File Source
connection profiles
> >> Connection profile points to folder on file system
> 3) Page 2 would show summary of what Metadata objects are available
> > User could pick and choose (check-boxes) what tables, procedures,
etc... to use
> 4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
> 5) Page 4 (if update) to show differences
> Relational model would be generated that contains the standard File connector
procedures
> Virtual Model would be created (or selected) where the view tables containing the
canned complex SQL which contains the FILE functions that require the table, column info.
> - user will define a View Table name for each data file they wish to import
> - if a View Table already exists in an existing View Model, user will be warned/asked
to overwrite (or uncheck) before FINISH
> EXAMPLE:
> ==========================================================
> SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
> (EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f,
TEXTTABLE(file COLUMNS lastName string, firstName string, middleName string, empId
biginteger, department string, annualSalary double, title string, homePhone string, mgrId
biginteger, street string, city string, state string, ZipCode string HEADER 3) AS emp
> ==========================================================
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:52 p.m.
New subject: [JBoss JIRA] Assigned: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond reassigned TEIIDDES-1017:
--------------------------------------
Assignee: Barry LaFond (was: Mark Drilling)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Description:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
was:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
> Create "Metadata from Teiid Metadata File" import option which utilizes DTP
Flat File connection profile and targets Teiid formatted source table files
>
--------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1017
> URL: https://issues.jboss.org/browse/TEIIDDES-1017
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 7.5
>
> Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml,
ImportTeiidMetadata Wizard.png
>
>
> To improve usability of File connectors, users need the ability to import from a
Teiid Source file via the import wizard.
> 1) Add an new import option > "Metadata from Teiid Metadata File"
> 2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> >> Would be filtered to be only select & edit Flat File Source
connection profiles
> >> Connection profile points to folder on file system
> 3) Page 2 would show summary of what Metadata objects are available
> > User could pick and choose (check-boxes) what tables, procedures,
etc... to use
> 4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
> 5) Page 4 (if update) to show differences
> Relational model would be generated that contains the standard File connector
procedures
> Virtual Model would be created (or selected) where the view tables containing the
canned complex SQL which contains the FILE functions that require the table, column info.
> - user will define a View Table name for each data file they wish to import
> - if a View Table already exists in an existing View Model, user will be warned/asked
to overwrite (or uncheck) before FINISH
> EXAMPLE:
> ==========================================================
> SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
> (EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f,
TEXTTABLE(file COLUMNS lastName string, firstName string, middleName string, empId
biginteger, department string, annualSalary double, title string, homePhone string, mgrId
biginteger, street string, city string, state string, ZipCode string HEADER 3) AS emp
> ==========================================================
> Looks like the final SQL will look like:
> SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
> FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS
Name string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-page-1.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-designer-import-options.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-configure.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:47 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-page-2.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:47 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-view-table.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:20 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1017:
----------------------------------------
1.5.3.2. TEXTTABLE
The TEXTTABLE funciton processes character input to produce tabular ouptut. It supports
both fixed and delimited file format parsing. The function itself defines what columns it
projects. The TEXTTABLE function is implicitly a nested table and may be correlated to
preceeding FROM clause entries.
Usage:
TEXTTABLE(expression COLUMNS <COLUMN>, ... [DELIMITER char] [(QUOTE|ESCAPE) char]
[HEADER [integer]] [SKIP integer]) AS name
COLUMN := name datatype [WIDTH integer]
Parameters
expression - the text content to process, which should be convertable to CLOB.
DELIMITER sets the field delimiter character to use. Defaults to ','.
QUOTE sets the quote, or qualifier, character used to wrap field values. Defaults to
'"'.
ESCAPE sets the escape character to use if no quoting character is in use. This is
used in situations where the delimiter or new line characters are escaped with a preceding
character, e.g. \,
HEADER specifies the text line number (counting every new line) on which the column
names occur. All lines prior to the header will be skipped. If HEADER is specified, then
the header line will be used to determine the TEXTTABLE column position by
case-insensitive name matching. This is especially useful in situations where only a
subset of the columns are needed. If the HEADER value is not specified, it defaults to 1.
If HEADER is not specified, then columns are expected to match positionally with the text
contents.
SKIP specifies the number of text lines (counting every new line) to skip before
parsing the contents. HEADER may still be specified with SKP.
Syntax Rules:
If width is specified for one column it must be specified for all columns.
If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and HEADER
should not be specified.
The columns names must be not contain duplicates.
Examples
Use of the HEADER parameter, returns 1 row ['b']:
select * from texttable('col1,col2,col3\na,b,c' COLUMNS col2 string HEADER) x
Use of fixed width, returns 1 row ['a', 'b', 'c']:
select * from texttable('abc' COLUMNS col1 string width 1, col2 string width
1, col3 string width 1) x
Use of ESCAPE parameter, returns 1 row ['a,', 'b']:
select * from texttable('a:,,b' COLUMNS col1 string, col2 string ESCAPE
':') x
As a nested table:
select x.* from t, texttable(t.clobcolumn COLUMNS first string, second date SKIP 1) x
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:18 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Description:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to skip
before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in fine-tuning
the column widths to fit row data
was:
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> Would be filtered to be only select & edit Flat File Source
connection profiles
> Connection profile points to folder on file system
3) Page 2 would show summary
of what Metadata objects are available
> User could pick and choose (check-boxes) what tables, procedures,
etc... to use
4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
> Create "Metadata from Teiid Metadata File" import option which utilizes DTP
Flat File connection profile and targets Teiid formatted source table files
>
--------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1017
> URL: https://issues.jboss.org/browse/TEIIDDES-1017
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 7.5
>
> Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml,
ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-view-table.png
>
>
> To improve usability of File connectors, users need the ability to import from a
Teiid Source file via the import wizard.
> 1) Add an new import option > "Metadata from Teiid Metadata File"
> 2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
> >> Would be filtered to be only select & edit Flat File Source
connection profiles
> >> Connection profile points to folder on file system
> 3) Page 2 would show summary of what Metadata objects are available
> > User could pick and choose (check-boxes) what tables, procedures,
etc... to use
> 4) Page 3 maybe the Model Selection page with "Update"
option, similar to JDBC importer + any more import options
> 5) Page 4 (if update) to show differences
> Relational model would be generated that contains the standard File connector
procedures
> Virtual Model would be created (or selected) where the view tables containing the
canned complex SQL which contains the FILE functions that require the table, column info.
> - user will define a View Table name for each data file they wish to import
> - if a View Table already exists in an existing View Model, user will be warned/asked
to overwrite (or uncheck) before FINISH
> EXAMPLE:
> ==========================================================
> SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
> (EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f,
TEXTTABLE(file COLUMNS lastName string, firstName string, middleName string, empId
biginteger, department string, annualSalary double, title string, homePhone string, mgrId
biginteger, street string, city string, state string, ZipCode string HEADER 3) AS emp
> ==========================================================
> Looks like the final SQL will look like:
> SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
> FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS
Name string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
> Based on Teiid docs for TEXTTABLE() function Designer will need:
> - Use Header option (boolean)
> - Quote character (Defaults to '"')
> - Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
> - HEADER may still be specified with SKIP.
> - FIXED WIDTH option (boolean)
> - If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
> - Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Commented: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1017:
----------------------------------------
(07:46:22 AM) blafond: rareddy: Hey. Looking more at the TEXTTABLE options. Seems a little
strange that when FIXED WIDTH == TRUE that you can't still have a header that
containing column names. Or can you have one, and it's ignored and you can use SKIP to
help ignore it?
(07:48:05 AM) blafond: rareddy: From an "Import" standpoint it would really be
nice to allow users to embed their column names in the flat file, else users will have to
name them by hand or take the default col1, col1... etc. names
(07:50:41 AM) rareddy: blafond: hand edit on UI vs hand edit a file and then import in UI,
I would choose former
(07:51:46 AM) rareddy: blafond, I am not exactly sure how the fixed version works
(07:52:53 AM) rareddy: blafond, I would have to see the code if it is ignoring the header;
skip is good idea in that case
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:41 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Fix Version/s: 7.4.2
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:38 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: teiid-designer-import-options.png)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-designer-import-options.png
Massaged all of Teiid Designer's Import option Labels
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: teiid-metadata-file-import-configure.png)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:40 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-configure.png
Final screen cap of Configure dialog.
Includes full support for TEXTTABLE() function options
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:36 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-parse-column.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpData.txt, ImportTeiidMetadata Wizard.bmml, ImportTeiidMetadata
Wizard.png, teiid-designer-import-options.png, teiid-metadata-file-import-configure.png,
teiid-metadata-file-import-page-1.png, teiid-metadata-file-import-page-2.png,
teiid-metadata-file-import-parse-column.png, teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:43 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: EmpDataFixed_WITH_HEADER.txt
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpData.txt, EmpDataFixed_WITH_HEADER.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:45 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: EmpData.txt)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixed_WITH_HEADER.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:45 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: EmployeeData.txt
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixed_WITH_HEADER.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:50 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: EmpDataFixed_WITH_HEADER.txt)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmployeeData.txt, ImportTeiidMetadata Wizard.bmml,
ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:52 a.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: EmpDataFixedWidth.txt
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixedWidth.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:50 a.m.
New subject: [JBoss JIRA] Resolved: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond resolved TEIIDDES-1017.
------------------------------------
Resolution: Done
Fixed in both TRUNK and 7.4.2 branch
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixedWidth.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-configure.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixedWidth.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: teiid-metadata-file-import-page-1.png)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixedWidth.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: (was: teiid-metadata-file-import-configure.png)
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixedWidth.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] Updated: (TEIIDDES-1017) Create "Metadata from Teiid Metadata File" import option which utilizes DTP Flat File connection profile and targets Teiid formatted source table files
[
https://issues.jboss.org/browse/TEIIDDES-1017?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1017:
-----------------------------------
Attachment: teiid-metadata-file-import-page-1.png
Create "Metadata from Teiid Metadata File" import option
which utilizes DTP Flat File connection profile and targets Teiid formatted source table
files
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1017
URL: https://issues.jboss.org/browse/TEIIDDES-1017
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Attachments: EmpDataFixedWidth.txt, EmployeeData.txt, ImportTeiidMetadata
Wizard.bmml, ImportTeiidMetadata Wizard.png, teiid-designer-import-options.png,
teiid-metadata-file-import-configure.png, teiid-metadata-file-import-page-1.png,
teiid-metadata-file-import-page-2.png, teiid-metadata-file-import-parse-column.png,
teiid-metadata-file-import-view-table.png
To improve usability of File connectors, users need the ability to import from a Teiid
Source file via the import wizard.
1) Add an new import option > "Metadata from Teiid Metadata File"
2) Page 1 set up similar to the JDBC importer & SF importer with the Connection
Profile combo box at top with select & edit Connection profiles buttons
>> Would be filtered to be only select & edit Flat File Source connection
profiles
>> Connection profile points to folder on file system
3) Page 2 would show summary of what Metadata objects are available
>> User could pick and choose (check-boxes) what tables, procedures, etc... to
use
4) Page 3 maybe the Model Selection page with "Update" option, similar to JDBC
importer + any more import options
5) Page 4 (if update) to show differences
Relational model would be generated that contains the standard File connector procedures
Virtual Model would be created (or selected) where the view tables containing the canned
complex SQL which contains the FILE functions that require the table, column info.
- user will define a View Table name for each data file they wish to import
- if a View Table already exists in an existing View Model, user will be warned/asked to
overwrite (or uncheck) before FINISH
EXAMPLE:
==========================================================
SELECT EMP.lastName, EMP.firstName, EMP.middleName, EMP.empId, EMP.department,
EMP.annualSalary, EMP.title, EMP.homePhone, EMP.mgrId, EMP.street, EMP.city, EMP.state,
EMP.ZipCode FROM
(EXEC EmployeeData.getTextFiles('EmployeeData.txt')) AS f, TEXTTABLE(file
COLUMNS lastName string, firstName string, middleName string, empId biginteger, department
string, annualSalary double, title string, homePhone string, mgrId biginteger, street
string, city string, state string, ZipCode string HEADER 3) AS emp
==========================================================
Looks like the final SQL will look like:
SELECT Name, Sport, Position, Team, City, StateCode, AnnualSalary
FROM(EXEC NN.getTextFiles('PlayerData.txt')) AS f, TEXTTABLE(file COLUMNS Name
string, Sport string, Position string, Team string, City string, StateCode string,
AnnualSalary string HEADER 2) AS A
Based on Teiid docs for TEXTTABLE() function Designer will need:
- Use Header option (boolean)
- Quote character (Defaults to '"')
- Skip integer value (specifies the number of text lines (counting every new line) to
skip before parsing the contents.
- HEADER may still be specified with SKIP.
- FIXED WIDTH option (boolean)
- If width is specified, then fixed width parsing is used and ESCAPE, QUOTE, and
HEADER should not be specified.
- Probably need a target NUMBER OF COLUMNS input as well to assist user in
fine-tuning the column widths to fit row data
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4877
days inactive
4903
days old
teiid-designer-issues@lists.jboss.org
38 comments
1 participants
participants (1)
-
Barry LaFond (JIRA)