topic Re: [resolved] Schemas and XML Export/Import feature in Talend Studio

[resolved] Schemas and XML Export/Import feature

Anonymous — Thu, 20 Sep 2012 11:04:19 GMT

Hello,
I actually use TOS for Data Integration.
More exactly i deal with schemas of db connections.
In the schema window, there are 2 columns in the list of schema columns:
"Column" : that shows you a label for the column
"Db Column" : that shows you the physical name of the Db column
In 4.2 version, i used a feature that allows to export a schema in a XML format and then re-import it.
In 5.1.2, it exports correctly the schema:

<?xml version="1.0" encoding="UTF-8"?>
<schema dbmsId="mega_id">
    <column comment="" default="" key="false"
        label="_310000000D00_Absolute_Identifier_" length="8"
        nullable="false"
        originalDbColumnName="~310000000D00"
        pattern="" precision="0" talendType="id_String" type="MegaIdentifier"/>
    <column comment="" default="" key="false"
        label="_lfGkEeBZ6910_Aggregated_Status_" length="160"
        nullable="true"
        originalDbColumnName="~lfGkEeBZ6910"
        pattern="" precision="0" talendType="id_String" type="String"/>
</schema>

Then in the XML file, i modify the label in order to make it more user friendly:

<?xml version="1.0" encoding="UTF-8"?>
<schema dbmsId="mega_id">
    <column comment="" default="" key="false"
        label="MA_Absolute_Identifier" length="8"
        nullable="false"
        originalDbColumnName="~310000000D00"
        pattern="" precision="0" talendType="id_String" type="MegaIdentifier"/>
    <column comment="" default="" key="false"
        label="MA_Aggregated_Status" length="160"
        nullable="true"
        originalDbColumnName="~lfGkEeBZ6910"
        pattern="" precision="0" talendType="id_String" type="String"/>
</schema>

Then i import this file in the schema using the button called "Replace all rows by import from xml file".
But the value in Column and Db Column are the same and equal to the label.
If i export the new schema it gives me:

<?xml version="1.0" encoding="UTF-8"?>
<schema dbmsId="mega_id">
    <column comment="" default="" key="false"
        label="MA_Absolute_Identifier" length="8"
        nullable="false"
        originalDbColumnName="MA_Absolute_Identifier"
        pattern="" precision="0" talendType="id_String" type="MegaIdentifier"/>
    <column comment="" default="" key="false"
        label="MA_Aggregated_Status" length="160"
        nullable="true"
        originalDbColumnName="MA_Aggregated_Status"
        pattern="" precision="0" talendType="id_String" type="String"/>
</schema>

So in fact the physical column name seems to be lost when importing xml file.
Is this a bug or just an error from me?
Thanks

Re: [resolved] Schemas and XML Export/Import feature

janhess — Thu, 20 Sep 2012 11:45:44 GMT

If you change the label name in the schema, the column name changes in both versions.

Re: [resolved] Schemas and XML Export/Import feature

Anonymous — Thu, 20 Sep 2012 11:58:26 GMT

Effectively so my conclusion is that it is a bug, no?

Re: [resolved] Schemas and XML Export/Import feature

janhess — Thu, 20 Sep 2012 13:33:04 GMT

Not necessarily. Why would you want them to be different?
You can give them any name - they don't have to be the same as the database column name.

Re: [resolved] Schemas and XML Export/Import feature

Anonymous — Thu, 20 Sep 2012 13:45:33 GMT

The Db Column name is the one used by talend to make operations on the database table so it must not be at the hand of the user.

Re: [resolved] Schemas and XML Export/Import feature

janhess — Thu, 20 Sep 2012 14:08:17 GMT

Yes on output but not on input.

Re: [resolved] Schemas and XML Export/Import feature

Anonymous — Thu, 22 Nov 2012 09:46:51 GMT

Is it possible to declare a bug in jira for this please?
The problem exists too in Talend 5.2 version.

Re: [resolved] Schemas and XML Export/Import feature

Anonymous — Fri, 30 Nov 2012 08:27:11 GMT

Hi all,
For those who are interested in this thread. An issue has been logged in Jira and at this moment it has been solved and it will be available in the next releases 5.1.3 and 5.2.1.
https://jira.talendforge.org/browse/TDI-23890