

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say


"The intake layer of Datadog’s self-serve analytics platform is largely built on Airbyte.Airbyte’s ease of use and extensibility allowed any team in the company to push their data into the platform - without assistance from the data team!"


“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”


“We chose Airbyte for its ease of use, its pricing scalability and its absence of vendor lock-in. Having a lean team makes them our top criteria. The value of being able to scale and execute at a high level by maximizing resources is immense”
Create a new Java project using your preferred IDE or build tool (e.g., Maven or Gradle).
Add the necessary dependencies to your project's build file for Kafka and Elasticsearch clients.
For Maven, add the following to your `pom.xml`:
```xml
<dependencies>
<!-- Kafka Client -->
<dependency>
<groupId>org.apache.kafka</groupId>
<artifactId>kafka-clients</artifactId>
<version>YOUR_KAFKA_VERSION</version>
</dependency>
<!-- Elasticsearch Client -->
<dependency>
<groupId>org.elasticsearch.client</groupId>
<artifactId>elasticsearch-rest-high-level-client</artifactId>
<version>YOUR_ELASTICSEARCH_VERSION</version>
</dependency>
</dependencies>
```
Create an instance of the Elasticsearch high-level REST client to interact with your Elasticsearch cluster.
```java
import org.elasticsearch.client.RestClient;
import org.elasticsearch.client.RestHighLevelClient;
public class ElasticsearchConnector {
public RestHighLevelClient createClient() {
return new RestHighLevelClient(
RestClient.builder(new HttpHost("localhost", 9200, "http"))
);
}
}
```
Set up a Kafka producer to send messages to your Kafka topic.
```java
import org.apache.kafka.clients.producer.KafkaProducer;
import org.apache.kafka.clients.producer.ProducerConfig;
import org.apache.kafka.clients.producer.ProducerRecord;
import org.apache.kafka.common.serialization.StringSerializer;
import java.util.Properties;
public class KafkaDataPublisher {
public KafkaProducer<String, String> createProducer() {
Properties props = new Properties();
props.put(ProducerConfig.BOOTSTRAP_SERVERS_CONFIG, "localhost:9092");
props.put(ProducerConfig.KEY_SERIALIZER_CLASS_CONFIG, StringSerializer.class.getName());
props.put(ProducerConfig.VALUE_SERIALIZER_CLASS_CONFIG, StringSerializer.class.getName());
return new KafkaProducer<>(props);
}
}
```
Write a method to extract data from Elasticsearch using the search API. You can specify the index and query as needed.
```java
import org.elasticsearch.action.search.SearchRequest;
import org.elasticsearch.action.search.SearchResponse;
import org.elasticsearch.client.RequestOptions;
import org.elasticsearch.index.query.QueryBuilders;
import org.elasticsearch.search.SearchHit;
import org.elasticsearch.search.builder.SearchSourceBuilder;
import java.util.ArrayList;
import java.util.List;
public class ElasticsearchDataExtractor {
private final RestHighLevelClient client;
public ElasticsearchDataExtractor(RestHighLevelClient client) {
this.client = client;
}
public List<String> fetchData() throws IOException {
SearchRequest searchRequest = new SearchRequest("your_index");
SearchSourceBuilder searchSourceBuilder = new SearchSourceBuilder();
searchSourceBuilder.query(QueryBuilders.matchAllQuery());
searchRequest.source(searchSourceBuilder);
SearchResponse searchResponse = client.search(searchRequest, RequestOptions.DEFAULT);
List<String> results = new ArrayList<>();
for (SearchHit hit : searchResponse.getHits().getHits()) {
results.add(hit.getSourceAsString());
}
return results;
}
}
```
Iterate over the extracted data and publish each record to the Kafka topic.
```java
public class DataMover {
public static void main(String[] args) throws IOException {
// Create Elasticsearch client
ElasticsearchConnector esConnector = new ElasticsearchConnector();
RestHighLevelClient esClient = esConnector.createClient();
// Create Kafka producer
KafkaDataPublisher kafkaPublisher = new KafkaDataPublisher();
KafkaProducer<String, String> producer = kafkaPublisher.createProducer();
// Extract data from Elasticsearch
ElasticsearchDataExtractor extractor = new ElasticsearchDataExtractor(esClient);
List<String> data = extractor.fetchData();
// Publish data to Kafka
for (String record : data) {
producer.send(new ProducerRecord<>("your_topic", record));
}
// Close resources
producer.close();
esClient.close();
}
}
```
Compile and run your Java application. Monitor both Elasticsearch and Kafka to ensure data is being moved correctly.
Add proper exception handling and logging to your application to manage any errors or issues that arise during the data transfer process.
Depending on the volume of data, you may need to optimize your queries, batch size, and producer settings. You might also consider parallelizing the data extraction and publishing process to handle larger datasets more efficiently.
After successfully moving the data, perform any necessary clean-up, such as closing connections and disposing of resources.
This guide provides a basic framework for moving data from Elasticsearch to Kafka without third-party connectors. Depending on your specific requirements and environment, you may need to adjust configurations, error handling, and performance tuning to suit your use case.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Elasticsearch is a distributed search and analytics engine for all types of data. Elasticsearch is the central component of the ELK Stack (Elasticsearch, Logstash, and Kibana).
Elasticsearch's API provides access to a wide range of data types, including:
1. Textual data: Elasticsearch can index and search through large volumes of textual data, including documents, emails, and web pages.
2. Numeric data: Elasticsearch can store and search through numeric data, including integers, floats, and dates.
3. Geospatial data: Elasticsearch can store and search through geospatial data, including latitude and longitude coordinates.
4. Structured data: Elasticsearch can store and search through structured data, including JSON, XML, and CSV files.
5. Unstructured data: Elasticsearch can store and search through unstructured data, including images, videos, and audio files.
6. Log data: Elasticsearch can store and search through log data, including server logs, application logs, and system logs.
7. Metrics data: Elasticsearch can store and search through metrics data, including performance metrics, network metrics, and system metrics.
8. Machine learning data: Elasticsearch can store and search through machine learning data, including training data, model data, and prediction data.
Overall, Elasticsearch's API provides access to a wide range of data types, making it a powerful tool for data analysis and search.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: