[
https://issues.apache.org/jira/browse/NIFI-10829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636219#comment-17636219
]
dataminer.accolade commented on NIFI-10829:
-------------------------------------------
[~exceptionfactory] I think it makes sense to implement two consumers. One for
the EWS API for legacy systems that do not support the new Graph API.
> Adding the parent folder name as an argument to the ConsumeEWS processor
> ------------------------------------------------------------------------
>
> Key: NIFI-10829
> URL: https://issues.apache.org/jira/browse/NIFI-10829
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Reporter: dataminer.accolade
> Priority: Major
> Attachments: image-2022-11-16-17-32-21-819.png
>
>
> I want to be able to pass the root folder as an argument to the ConsumeEWS
> processor.
> [Source|https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/ConsumeEWS.java#L393]
> !image-2022-11-16-17-32-21-819.png!
> Primarily I am interested in
> [PublicFoldersRoot|https://learn.microsoft.com/en-us/dotnet/api/microsoft.exchange.webservices.data.wellknownfoldername?view=exchange-ews-api]
> making PublicFoldersRoot selectable will require the implementation of the
> deep search because, [deep traversal queries cannot be performed on public
> folders.|https://learn.microsoft.com/en-us/exchange/client-developer/web-service-reference/findfolder-operation?redirectedfrom=MSDN]
> Alternatively it would be nice to pass the path of the folder instead of a
> folder name with a specific root to avoid the usage of deep search.
> I would implement the new feature if it is desired and if it makes sense for
> the project.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
