Container Processor
The container processor loads data to Couchbase server and reads data from it.
This processor is used as a caching container that reads both the aggregated data and raw data from the bucket.
Container Processor Configuration
To add a Container processor into your pipeline, drag the processor to the canvas and right-click on it to configure.
| Field | Description |
|---|---|
| Load From Template | Select the template from the list. Only those templates will be visible in the drop down list that are created globally or within that workspace. |
| Sync With Source Template | When you use a template configuration, this tab is reflected. If any change is made in the source template, corresponding changes are reflected in Container’s configuration. |
| Connection Name | Provide a connection name for creating a connection. |
| Bucket Name | Couchbase bucket name. Select the Couchbase bucket that gets generated with Couchbase connection. You can also create a new bucket by specifying the bucket name. you also need to specify bucket password. |
| Bucket Password | Specify Bucket password in case new bucket is created. |
| Memory Quota | Memory Quota in megabytes per Couchbase server node. Memory Quota cannot be less than 100 MB. |
| Replicate View Indexes | By checking the Replicate view indexes checkbox, you ensure that view indexes, as well as data are replicated |
| Flush | When flushed, all items in the bucket are removed as soon as possible. |
| Document Id | Unique identifier for newly created documents of Couchbase. |
| Retention Enable | When selected, each newly created item lives for the number of seconds specified by retention policy. After the expiration time is reached item will be deleted by Couchbase server. |
| Record Limit | Limit to fetch the records from Couchbase. When selected Yes, specify number of records to be fetched from the Couchbase server. When selected No, all records will be fetched from the server. |
| Max No of Records | Number of records to be pulled from the server. |
| Overflow Condition | Fetch the records based on order for the selected column. (Fetch minimum records for ascending order and fetch maximum records for descending order) With aggregation, select the grouping field in the Overflow condition. |
| Fetch Data | Raw Data: Fetch the raw data from the Couchbase bucket. Aggregated Data: Fetch the aggregated data from the Couchbase. A new field is populated, where you can group the fields from the schema. |
| Output Fields | Fields in the message that needs to be a part of the output data. |
| Grouping Fields | Field of selected message on which group-by is applied. |
| Fields | Select the fields on which function is to be applied. |
Click on the NEXT button. An option to Save as Template will be available.
Add notes in the space provided and click on Save as Template.
Choose the scope of the Template and click SAVE for saving the Template and configuration details.
If you have any feedback on Gathr documentation, please email us!