[
https://issues.apache.org/jira/browse/NIFI-14457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944401#comment-17944401
]
David Handermann commented on NIFI-14457:
-----------------------------------------
Understanding the scope of transitive dependencies coming through a BaseX
dependency would be a good starting point for evaluation.
Giving some thought to Processor naming would also be important for packaging
and maintainability.
This may be a case where publishing a Processor in a separate GitHub repository
could be the best path forward, but it depends on some of these implementation
details.
> New processor to run xQuery on BaseX
> ------------------------------------
>
> Key: NIFI-14457
> URL: https://issues.apache.org/jira/browse/NIFI-14457
> Project: Apache NiFi
> Issue Type: Wish
> Components: Extensions
> Reporter: Oleksandr Shpak
> Assignee: Tomasz Korniszuk
> Priority: Major
>
> h2. About BaseX
> [BaseX|https://basex.org] is a powerful tool that allows to process not only
> XML, but also JSON, CSV, generate binary data, etc. It's stable and actively
> developing product that supports all xQuery 4.0 features and even more.
> Written in Java.
> h2. Processor(-s) requirements
> * FlowFile content should be passed as a context to the xquery script as
> string
> * xQuery script content is required to run the processor
> * User should be able to choose the strategy of attributes mapping
> ** Map all attributes as external variables
> ** Map only specific list of attributes as external variables
> ** Don't pass attributes
> * By analogy with invokeHttp processor the output can be assigned to the
> specific attribute
> * The next relationships should be available for this processor
> ** success
> ** failure
> ** original
> * The script response should replace the original FlowFile in case of
> success.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
