Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/1969
@pvillard31 I think we can add EL to collection without having to do
anything fancy since getCollection() in AbstractMongoProcessor re-uses the
mongoClient already.
That said, is it worth also adding EL support for URI and DB in this PR?
The simple case will mean it'll get eval'd against the variable registry, which
is definitely useful for migrating from env to env.
There's another case though in being able to eval against a FlowFile for
PutMongo so you can route to different DBs if you're doing some
application-level sharding. But that would mean we'd have to manage a pool/map
of connections since the mongoClient currently is set with @OnScheduled. Makes
sense if you think that's for another PR though.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
