Actually my data flow looks like this -
Assuming that AttributeToJson processor should give a json output. Is there any other way to verify it.
I'm following this post -
@Ankit Jain ExtractHL7Attributes is just going to parse the HL7 and add the field values as attributes on the FlowFile. The FlowFile contents remains as the original pipe-delimited HL7 flat file. You need to add AttributesToJSON after ExtractHL7Attributes and before PutHBaseJSON, since as @Artem Ervits mentions, PutHBaseJSON needs the FlowFile to be JSON and not the original HL7.
Sorry about the first image, it wasn't clear. but I've used AttributeToJson processor,Please check the 2nd screen shot still getting the above highlighted error.
I'd suggest inspecting the content of the data in the queues or via the data provenance to verify whether there is indeed invalid data. If you don't specify specific fields AttributesToJSON does dump attributes besides the HL7 attributes, so it is possible there is content that wouldn't be valid from the point of view of PutHBaseJSON.
If you are working with example or non-PII HL7 data, it'd be helpful to post the HL7 message itself and the JSON output itself.
I'm trying to parse following MDM^T02.hl7 message -
Where i could check the json output?
@Ankit Jain Copying the answer from https://community.hortonworks.com/questions/65241/error-while-storing-hl7-attributes-in-hbase.html: In AttributesToJSON do you have the Destination property set to "flowfile-content"? If you don't then what it does is put the JSON in the JSONAttributes attribute and it leaves the FlowFile contents the same, in this case an HL7 document. An HL7 document of course isn't JSON and starts with MSH, so this is the error you'd see if you have Destination set to "flowfile-attribute" (the default) and not "flowfile-content".