elasticsearch index sink ElasticSearch Index Sink

Provided by: "Apache Software Foundation"

Support Level for this Kamelet is: "Preview"

This sink stores documents into ElasticSearch.

Input data must have JSON format according to the index used.

  • indexId / ce-indexid: as the index ID for Elasticsearch

If the header won’t be set the exchange ID will be used as index.

  • indexName / ce-indexname: as the index Name for Elasticsearch

If the header won’t be set the exchange ID will be used as index name.

Configuration Options

The following table summarizes the configuration options available for the elasticsearch-index-sink Kamelet:

Property Name Description Type Default Example

clusterName *

ElasticSearch Cluster Name

Name of the cluster.

string

"quickstart"

hostAddresses *

Host Addresses

Comma separated list with ip:port formatted remote transport addresses to use.

string

"quickstart-es-http:9200"

enableSSL

Enable SSL

Do we want to connect using SSL?

boolean

true

indexName

Index in ElasticSearch

The name of the index to act against.

string

"data"

password

Password

Password to connect to ElasticSearch.

string

user

Username

Username to connect to ElasticSearch.

string

Fields marked with an asterisk (*) are mandatory.

Dependencies

At runtime, the elasticsearch-index-sink Kamelet relies upon the presence of the following dependencies:

  • camel:jackson

  • camel:kamelet

  • camel:elasticsearch-rest

  • camel:gson

  • camel:bean

Usage

This section describes how you can use the elasticsearch-index-sink.

Knative Sink

You can use the elasticsearch-index-sink Kamelet as a Knative sink by binding it to a Knative object.

elasticsearch-index-sink-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: elasticsearch-index-sink-binding
spec:
  source:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: elasticsearch-index-sink
    properties:
      clusterName: "quickstart"
      hostAddresses: "quickstart-es-http:9200"

Prerequisite

You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the elasticsearch-index-sink-binding.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f elasticsearch-index-sink-binding.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind channel:mychannel elasticsearch-index-sink -p "sink.clusterName=quickstart" -p "sink.hostAddresses=quickstart-es-http:9200"

This command creates the KameletBinding in the current namespace on the cluster.

Kafka Sink

You can use the elasticsearch-index-sink Kamelet as a Kafka sink by binding it to a Kafka topic.

elasticsearch-index-sink-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: elasticsearch-index-sink-binding
spec:
  source:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: elasticsearch-index-sink
    properties:
      clusterName: "quickstart"
      hostAddresses: "quickstart-es-http:9200"

Prerequisites

  • You’ve installed Strimzi.

  • You’ve created a topic named my-topic in the current namespace.

  • You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the elasticsearch-index-sink-binding.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f elasticsearch-index-sink-binding.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind kafka.strimzi.io/v1beta1:KafkaTopic:my-topic elasticsearch-index-sink -p "sink.clusterName=quickstart" -p "sink.hostAddresses=quickstart-es-http:9200"

This command creates the KameletBinding in the current namespace on the cluster.