org.apache.nifinifi-mongodb-services-nar2.4.0org.apache.nifinifi-mongodb-client-service-api-nar2.4.02.1.0rel/nifi-2.4.0main1org.apache.nifi.mongodb.MongoDBControllerServiceCONTROLLER_SERVICEProvides a controller service that configures a connection to MongoDB and provides access to that connection to other Mongo-related components.mongomongodbserviceMongo URIMongo URIMongoURI, typically of the form: mongodb://host1[:port1][,host2[:port2],...]truefalsetrueENVIRONMENTfalsefalseDatabase UserDatabase UserDatabase user namefalsefalsetrueENVIRONMENTfalsefalsePasswordPasswordThe password for the database userfalsetruetrueENVIRONMENTfalsefalseSSL Context ServiceSSL Context ServiceThe SSL Context Service used to provide client certificate information for TLS/SSL connections.org.apache.nifi.ssl.SSLContextProviderorg.apache.nifinifi-standard-services-api-nar2.4.0falsefalsefalseNONEfalsefalseWrite ConcernWrite ConcernThe write concern to useACKNOWLEDGEDACKNOWLEDGEDACKNOWLEDGEDWrite operations that use this write concern will wait for acknowledgement, using the default write concern configured on the serverUNACKNOWLEDGEDUNACKNOWLEDGEDWrite operations that use this write concern will return as soon as the message is written to the socket. Exceptions are raised for network issues, but not server errorsFSYNCEDFSYNCEDDeprecated. Use of "JOURNALED" is preferredJOURNALEDJOURNALEDWrite operations wait for the server to group commit to the journal file on diskREPLICA_ACKNOWLEDGEDREPLICA_ACKNOWLEDGEDDeprecated. Use of "W2" is preferredMAJORITYMAJORITYExceptions are raised for network issues, and server errors; waits on a majority of servers for the write operationW1W1Write operations that use this write concern will wait for acknowledgement from a single memberW2W2Write operations that use this write concern will wait for acknowledgement from two membersW3W3Write operations that use this write concern will wait for acknowledgement from three memberstruefalsefalseNONEfalsefalseorg.apache.nifi.mongodb.MongoDBClientServiceorg.apache.nifinifi-mongodb-client-service-api-nar2.4.0org.apache.nifi.mongodb.MongoDBLookupServiceCONTROLLER_SERVICEProvides a lookup service based around MongoDB. Each key that is specified will be added to a query as-is. For example, if you specify the two keys, user and email, the resulting query will be { "user": "tester", "email": "tester@test.com" }. The query is limited to the first result (findOne in the Mongo documentation). If no "Lookup Value Field" is specified then the entire MongoDB result document minus the _id field will be returned as a record.mongomongodblookuprecordschema-access-strategySchema Access StrategySpecifies how to obtain the schema that is to be used for interpreting the data.inferUse 'Schema Name' Propertyschema-nameThe name of the Schema to use is specified by the 'Schema Name' Property. The value of this property is used to lookup the Schema in the configured Schema Registry service.Use 'Schema Text' Propertyschema-text-propertyThe text of the Schema itself is specified by the 'Schema Text' Property. The value of this property must be a valid Avro Schema. If Expression Language is used, the value of the 'Schema Text' property must be valid after substituting the expressions.Infer from ResultinfertruefalsefalseNONEfalsefalseschema-registrySchema RegistrySpecifies the Controller Service to use for the Schema Registryorg.apache.nifi.schemaregistry.services.SchemaRegistryorg.apache.nifinifi-standard-services-api-nar2.4.0falsefalsefalseNONEfalsefalseschema-access-strategySchema Access Strategyschema-nameschema-reference-readerschema-nameSchema NameSpecifies the name of the schema to lookup in the Schema Registry property${schema.name}falsefalsetrueENVIRONMENTfalsefalseschema-access-strategySchema Access Strategyschema-nameschema-versionSchema VersionSpecifies the version of the schema to lookup in the Schema Registry. If not specified then the latest version of the schema will be retrieved.falsefalsetrueFLOWFILE_ATTRIBUTESfalsefalseschema-access-strategySchema Access Strategyschema-nameschema-branchSchema BranchSpecifies the name of the branch to use when looking up the schema in the Schema Registry property. If the chosen Schema Registry does not support branching, this value will be ignored.falsefalsetrueFLOWFILE_ATTRIBUTESfalsefalseschema-access-strategySchema Access Strategyschema-nameschema-textSchema TextThe text of an Avro-formatted Schema${avro.schema}falsefalsetrueFLOWFILE_ATTRIBUTESfalsefalseschema-access-strategySchema Access Strategyschema-text-propertymongo-lookup-client-serviceClient ServiceA MongoDB controller service to use with this lookup service.org.apache.nifi.mongodb.MongoDBClientServiceorg.apache.nifinifi-mongodb-client-service-api-nar2.4.0truefalsefalseNONEfalsefalsemongo-db-nameMongo Database NameThe name of the database to usetruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsemongo-collection-nameMongo Collection NameThe name of the collection to usetruefalsetrueFLOWFILE_ATTRIBUTESfalsefalsemongo-lookup-value-fieldLookup Value FieldThe field whose value will be returned when the lookup key(s) match a record. If not specified then the entire MongoDB result document minus the _id field will be returned as a record.falsefalsefalseNONEfalsefalsemongo-lookup-projectionProjectionSpecifies a projection for limiting which fields will be returned.falsefalsefalseNONEfalsefalseorg.apache.nifi.lookup.LookupServiceorg.apache.nifinifi-standard-services-api-nar2.4.0