Change of namespace in xml
Posted: Wed Aug 15, 2018 5:02 am
Hi,
I have a problem for which I was unable to find some solution from the search. Posting it here.
I have an exiting job with xml unpack stage to read the xml file and output data to some text files.
Now there is a change in xsd from the source, change of namespace and additional elements
Earlier the namespace is ......../Event/1.0 and now it is changed to ......../Event/2.0 and so when I replace the xsd definition and in the XML_parser setup, from DocumentRoot when I browse for the new xsd all the earlier mappings(output links mapping) are throwing errors and this is requiring me to remap every column.
To validate from my end, in the new xsd I have retained the earlier namespace ......../Event/1.0 and repeated above steps passing through XMLParse Setup and Document root i do not see any errors.
So I concluded it is only because of change of namespace, the errors are thrown.
I have around 600 columns to be mapped for the existing job.
Can anyone know a better way to handle this(new namespace) so that I can avoid remapping of all columns
I have a problem for which I was unable to find some solution from the search. Posting it here.
I have an exiting job with xml unpack stage to read the xml file and output data to some text files.
Now there is a change in xsd from the source, change of namespace and additional elements
Earlier the namespace is ......../Event/1.0 and now it is changed to ......../Event/2.0 and so when I replace the xsd definition and in the XML_parser setup, from DocumentRoot when I browse for the new xsd all the earlier mappings(output links mapping) are throwing errors and this is requiring me to remap every column.
To validate from my end, in the new xsd I have retained the earlier namespace ......../Event/1.0 and repeated above steps passing through XMLParse Setup and Document root i do not see any errors.
So I concluded it is only because of change of namespace, the errors are thrown.
I have around 600 columns to be mapped for the existing job.
Can anyone know a better way to handle this(new namespace) so that I can avoid remapping of all columns