MongoDB 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.

Connection string

Enter credentials in the connection string on the MongoDB tab.

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

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

To enter credentials for LDAP authentication, enter the username and password before the host name, and set the authMechanism option to PLAIN. Use the following format:

mongodb://username:password@host[:port][/[database]?authMechanism=PLAIN

Credentials tab

Select either the Username/Password or LDAP authentication type on the Credentials tab. When using LDAP authentication, you also choose between server-driven or plain authentication.

Then, you specify the username and password for the authentication type.

• 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.

<BSON Timestamp field name>:Timestamp(<timestamp>, <ordinal>)

"Transaction":{
    "Timestamp":Jan 26, 2016 14:50:09PM
    "Ordinal":1
}