exceptionfactory commented on PR #6676:
URL: https://github.com/apache/nifi/pull/6676#issuecomment-1329469155

   Thanks for the reply @TheGreatRandall.
   
   The unit test failures are visible in the `Checks` tab on GitHub, and should 
also appear when building on a local machine. Here is the current set of 
failures:
   
   ```
   Error:  Failures: 
   Error:    TestXMLReader.testContentField:176 expected: <5> but was: <1>
   Error:    TestXMLReader.testInferSchema:201 expected: 
<MapRecord[{software=MapRecord[{content_field=Apache NiFi, favorite=true}], 
num=123, name=John Doe}]> but was: <>
   Error:    TestXMLReader.testInferSchemaContentFieldNameNotSet:220 expected: 
<MapRecord[{software=MapRecord[{favorite=true}], num=123, name=John Doe}]> but 
was: <>
   Error:    
TestXMLReader.testInferSchemaContentFieldNameNotSetSubElementExists:239 
expected: <MapRecord[{field_with_attribute=MapRecord[{attr=attr_content, 
value=123}]}]> but was: <>
   Error:    
TestXMLReader.testInferSchemaContentFieldNameSetSubElementExistsNameClash:259 
expected: <MapRecord[{field_with_attribute=MapRecord[{attr=attr_content, 
value=content of field}]}]> but was: <>
   Error:    
TestXMLReader.testInferSchemaContentFieldNameSetSubElementExistsNoNameClash:280 
expected: <MapRecord[{field_with_attribute=MapRecord[{content_field=content of 
field, attr=attr_content, value=123}]}]> but was: <>
   Error:    TestXMLReader.testInferSchemaIgnoreAttributes:299 expected: 
<MapRecord[{software=Apache NiFi, num=123, name=John Doe}]> but was: <>
   Error:    TestXMLReader.testRecordFormatArray:104 expected: <4> but was: <1>
   Error:    TestXMLReader.testRecordFormatDeterminedBasedOnAttribute:82 
expected: <4> but was: <1>
   ```
   
   `MapRecord.toString()` uses `LinkedHashMap`, so is this a problem in 
`MapRecord`, or some other class?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to