[
https://issues.apache.org/jira/browse/NIFI-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446291#comment-16446291
]
ASF GitHub Bot commented on NIFI-4185:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2587
@JohannesDaniel thanks for the update! I commented above re: the use of
Expression Language in the property descriptor.
I do still feel like the check for 'record tag names' is unnecessary, as
the reader should not be responsible for filtering the data but rather just for
reading it. There already exist mechanisms for filtering the data (You could
use PartitionRecord + RouteOnAttribute, ValidateRecord, or QueryRecord just off
the top of my head to achieve this). Additionally, we have the Schema for the
Record Reader. So if the element name matches the top-level Schema name (or one
of them, if the top-level field is a UNION/CHOICE element), then we could use
that. So, with your example above, if you only want to read the
`<record/><record/>` part, your schema should indicate that the top-level field
name is `record`. In that case, it should filter out the `other` record. Does
that make sense?
> Add XML record reader & writer services
> ---------------------------------------
>
> Key: NIFI-4185
> URL: https://issues.apache.org/jira/browse/NIFI-4185
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: Andy LoPresto
> Assignee: Johannes Peter
> Priority: Major
> Labels: json, records, xml
>
> With the addition of the {{RecordReader}} and {{RecordSetWriter}} paradigm,
> XML conversion has not yet been targeted. This will replace the previous
> ticket for XML to JSON conversion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
