Since the sample XSLT was not working for me, I tried crafting a more customized XSLT to extract attribites as elements. While I have a little more success with this, it appears there is a bug in morphlines handling of the XSLT results. As you can see from this output, child element attributes are being merged together instead of being treated as distinct items (see red font text in log output below)?
At this point, XML processing appears to be broken in moprhlines 😞
cat morphlines.conf
morphlines : [
{
id : morphtest
importCommands : ["com.cloudera.**"]
commands : [
{
xslt {
fragments : [
{
fragmentPath : "/"
queryString : """
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0" >
<!-- <xsl:output method="xml" indent="yes" /> -->
<xsl:template match="//*[name() != 'RootNode']">
<xsl:element name="{name()}">
<xsl:for-each select="@*">
<xsl:element name="{name()}">
<xsl:value-of select="."/>
</xsl:element>
</xsl:for-each>
<xsl:apply-templates select="*|text()"/>
</xsl:element>
</xsl:template>
</xsl:stylesheet>
"""
}
]
}
}
{ generateUUID { field : id } }
{ logInfo { format : "output record: {}", args : ["@{}"] } }
]
}
]
cat test2.xml
<?xml version="1.0"?>
<RootNode>
<Child1 A="a" B="B">
<Child1_1 C="c" D="d" E="e" />
<Child1_2 X="x" B="bb" />
</Child1>
</RootNode>
cat /tmp/morphlog.txt
1964 [main] TRACE com.cloudera.cdk.morphline.saxon.XSLTBuilder$XSLT - XSLT input document:
<RootNode>
<Child1 A="a" B="B">
<Child1_1 C="c" D="d" E="e"/>
<Child1_2 X="x" B="bb"/>
</Child1>
</RootNode>
1981 [main] TRACE com.cloudera.cdk.morphline.stdlib.GenerateUUIDBuilder$GenerateUUID - beforeProcess: {A=[a], B=[B], Child1_1=[cde], Child1_2=[xbb]}
1983 [main] TRACE com.cloudera.cdk.morphline.stdlib.LogInfoBuilder$LogInfo - beforeProcess: {A=[a], B=[B], Child1_1=[cde], Child1_2=[xbb], id=[28827c81-28ca-41b1-9411-b8697d765ac5]}
1984 [main] INFO com.cloudera.cdk.morphline.stdlib.LogInfoBuilder$LogInfo - output record: [{A=[a], B=[B], Child1_1=[cde], Child1_2=[xbb], id=[28827c81-28ca-41b1-9411-b8697d765ac5]}]
Notice that when I run the same xml and xsl via the standalone Saxon parser it correctly creates attributes as elements, so this leads me to think that once morphlines pipeline processes the Saxon output into a record, that this is where the merging of attributes problem is happening.
java -cp /opt/saxon/SaxonHE9-5-1-2/saxon9he.jar net.sf.saxon.Transform -s:test2.xml -xsl:test2.xsl
<?xml version="1.0" encoding="UTF-8"?>
<Child1><A>a</A><B>B</B>
<Child1_1><C>c</C><D>d</D><E>e</E></Child1_1>
<Child1_2><X>x</X><B>bb</B></Child1_2>
</Child1>
