[ 
https://issues.apache.org/jira/browse/NIFI-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280310#comment-17280310
 ] 

Joey Frazee commented on NIFI-8208:
-----------------------------------

I took a little look at this and if we use mongodb-driver-legacy, most of the 
changes seem to be of two sorts:

* Two of the WriteConcern modes have been removed after being deprecated for a 
while. These are FSYNCED and REPLICA_ACKNOWLEDGED. The recommended replacements 
are JOURNALED and W2. This change would be just an update to the property 
descriptor description and probably a warning.
* Use of the Bson library APIs. This requires some more changes, but still 
straightforward.

These changes make it all incompatible with the 3.x driver versions so this 
begs the question about whether we should just jump to mongo-driver-sync or 
mongo-driver-reactivestreams. 4.1 and 4.2 are advertised to be compatible with 
all recent Mongo versions, so this should be ok.

> Upgrade MongoDB Driver to 4.2 series
> ------------------------------------
>
>                 Key: NIFI-8208
>                 URL: https://issues.apache.org/jira/browse/NIFI-8208
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.12.1
>         Environment: Linux / Kerberos
>            Reporter: Nick Lange
>            Priority: Minor
>              Labels: MongoDB
>
> MongoDBs 3.12.X series driver tries to create a Kerberos Subject from a 
> String which fails. The driver was reworked for version 4.2 and may just do 
> the right thing. Without this fix, clients are forced to turn off subject 
> matching in Java which seems to defeat some of the compartmentalization the 
> nifi is looking to achieve.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to