[
https://issues.apache.org/jira/browse/NIFI-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-5903:
-----------------------------
Description:
QueryRecord is an immensely powerful tool when evaluating "flat" data such as
CSV or flattened JSON. However, when evaluating data that has a lot of nested
elements, it loses a lot of its power quickly because there is no way to query
those nested elements. We should enable users to use RecordPath to pull out
particular fields of a Record so that we can write queries like:
{{SELECT *}}
{{FROM FLOWFILE}}
{{WHERE RPATH(organization, '/department/name') = 'Research and Engineering'}}
was:
QueryRecord is an immensely powerful tool when evaluating "flat" data such as
CSV or flattened JSON. However, when evaluating data that has a lot of nested
elements, it loses a lot of its power quickly because there is no way to query
those nested elements. We should enable users to use RecordPath to pull out
particular fields of a Record so that we can write queries like:
{{SELECT *}}
{{FROM FLOWFILE}}
{{WHERE RPATH(organization, '/department/name') = 'Research and Engineering'}}
> Allow RecordPath to be used in order to access nested fields within
> QueryRecord
> -------------------------------------------------------------------------------
>
> Key: NIFI-5903
> URL: https://issues.apache.org/jira/browse/NIFI-5903
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.9.0
>
>
> QueryRecord is an immensely powerful tool when evaluating "flat" data such as
> CSV or flattened JSON. However, when evaluating data that has a lot of nested
> elements, it loses a lot of its power quickly because there is no way to
> query those nested elements. We should enable users to use RecordPath to pull
> out particular fields of a Record so that we can write queries like:
> {{SELECT *}}
> {{FROM FLOWFILE}}
> {{WHERE RPATH(organization, '/department/name') = 'Research and Engineering'}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)