[
https://issues.apache.org/jira/browse/NIFI-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250366#comment-15250366
]
Joe Skora commented on NIFI-1197:
---------------------------------
Props go to [~mosermw] (the correct one this time) for finding the POM issue.
That didn't even cross my mind last night.
I couldn't figure out how it successfully built and tested for you guys with
the import mismatch, but after seeing the pom issue it makes sense.
Lessons learned. This is a pinch point of the multi-branch development scheme
that we'll get the hang of, but POM files especially will need special
attention moving from branch to branch.
> improve SSL options for getmongo and putmongo processor configuration
> properties
> --------------------------------------------------------------------------------
>
> Key: NIFI-1197
> URL: https://issues.apache.org/jira/browse/NIFI-1197
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.7.0
> Reporter: subhash parise
> Labels: patch
> Fix For: 1.0.0, 0.7.0
>
> Attachments:
> 0001-Fix-0.x-branch-nifi-mongodb-bundle-POM-reference-to-.patch
>
>
> Hi Team,
> Now getmongo and putmongo configuration properties are mongodb URI,database
> name, collection name, etc, but if the mongodb server configured with the ssl
> it won't accept ssl options in mongodb uri.
> Could anyone please improve the ssl options in mongo proccessors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
