MongoDB Atlas Lookup

<embedded document>.<field name>.<embedded field name>

/<field name>

{
  _id: 123,
  customer: {
       name: "Ed Martinez",
       status: "gold",
	phone: "123-456-7891",
	location: {
	  city: "San Francisco",
	  state: "California"
	}
  }
}

Size-based eviction

Configure the maximum number of values that the processor caches. When the maximum number is reached, the processor evicts the oldest values from the cache.

Time-based eviction

Configure the amount of time that a value can remain in the cache without being written to or accessed. When the expiration time is reached, the processor evicts the value from the cache. The eviction policy determines whether the processor measures the expiration time since the last write of the value or since the last access of the value.

For example, you set the eviction policy to expire after the last access and set the expiration time to 60 seconds. After the processor does not access a value for 60 seconds, the processor evicts the value from the cache.

Authentication method

Specify the authentication to use with the Authentication Method property on the Credentials tab:

• None
• Username / Password
• LDAP

Then, define the username and password for username/password or LDAP authentication.

When using username/password authentication, you also specify the authentication mechanism to use. You can also specify an authentication database.

Connection string

If you prefer, you can specify credentials in the connection string on the Connection tab. However, specifying credentials on the Credentials tab is the recommended method.

To enter credentials for username/password authentication for self-managed clusters, enter the username and password before the host name. Use the following format:

mongodb://username:password@host[:port][/[database][?options]]

To enter credentials for MongoDB Atlas, specify the URL from your Atlas cluster settings.

• Primary - Requires reading from the primary member.
• Primary Preferred - Prefers reading from the primary, but allows reads from a secondary member.
• Secondary - Requires reading from a secondary member.
• Secondary Preferred - Prefers reading from a secondary, but allows reads from a primary when necessary.
• Nearest - Reads from the member with the least network latency.