# Memcached

Kubemq memcached target connector allows services using kubemq server to access memcached server functions such `set`, `get` and `delete`.

## Prerequisites

The following are required to run the memcached target connector:

* kubemq cluster
* memcached server
* access to gcp Memcached server
* kubemq-targets deployment

## Configuration

Memcached target connector configuration properties:

| Properties Key            | Required | Description                                       | Example                           |
| ------------------------- | -------- | ------------------------------------------------- | --------------------------------- |
| hosts                     | yes      | memcached servers list address separated by comma | "localhost:11211,localhost:11212" |
| max\_idle\_connections    | no       | set max idle connection                           | "2"                               |
| default\_timeout\_seconds | no       | set default timeout seconds for operation         | "10"                              |

Example:

```yaml
bindings:
  - name: kubemq-query-gcp-memcached
    source:
      kind: kubemq.query
      name: kubemq-query
      properties:
        address: "kubemq-cluster:50000"
        client_id: "kubemq-query-gcp-memcached-connector"
        auth_token: ""
        channel: "query.memcached"
        group:   ""
        auto_reconnect: "true"
        reconnect_interval_seconds: "1"
        max_reconnects: "0"
    target:
      kind: gcp.cache.memcached
      name: gcp-memcached
      properties:
        hosts: "localhost:11211"
        max_idle_connections: "2"
        default_timeout_seconds: "10"
```

## Usage

### Get Request

Get request metadata setting:

| Metadata Key | Required | Description          | Possible values |
| ------------ | -------- | -------------------- | --------------- |
| key          | yes      | memcached key string | any string      |
| method       | yes      | get                  | "get"           |

Example:

```javascript
{
  "metadata": {
    "key": "your-memcached-key",
    "method": "get"
  },
  "data": null
}
```

### Set Request

Set request metadata setting:

| Metadata Key | Required | Description          | Possible values |
| ------------ | -------- | -------------------- | --------------- |
| key          | yes      | memcached key string | any string      |
| method       | yes      | set                  | "set"           |

Set request data setting:

| Data Key | Required | Description                       | Possible values    |
| -------- | -------- | --------------------------------- | ------------------ |
| data     | yes      | data to set for the memcached key | base64 bytes array |

Example:

```javascript
{
  "metadata": {
    "key": "your-memcached-key",
    "method": "set"
  },
  "data": "c29tZS1kYXRh" 
}
```

### Delete Request

Delete request metadata setting:

| Metadata Key | Required | Description          | Possible values |
| ------------ | -------- | -------------------- | --------------- |
| key          | yes      | memcached key string | any string      |
| method       | yes      | delete               | "delete"        |

Example:

```javascript
{
  "metadata": {
    "key": "your-memcached-key",
    "method": "delete"
  },
  "data": null
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kubemq.io/configuration/connectors/kubemq-targets/gcp/memcached.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.