# Ingestion pipeline

**URL:** <https://discuss.elastic.co/t/ingestion-pipeline/79122>\
**Category:** Logstash\
**Created:** [March 18, 2017, 7:54am UTC](https://discuss.elastic.co/t/ingestion-pipeline/79122 "2017-03-18T07:54:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![shane\_lee](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@shane\_lee](https://discuss.elastic.co/u/shane_lee)\
**Post date:** [March 20, 2017, 12:20pm UTC](https://discuss.elastic.co/t/ingestion-pipeline/79122/4 "2017-03-20T12:20:52Z")

</div>

I found some interesting topics by searching for `sql_last_value`.

This post below demonstrates using sql\_last\_value and how to actually update documents.  
As you said, it might be best to use mysql primary key as document id to handle any updates.

> [@MySQL to Elasticsearch](https://discuss.elastic.co/t/mysql-to-elasticsearch/41367/19):
>
> Please consult the documentation: [https://www.elastic.co/guide/en/logstash/current/working-with-plugins.html#updating-plugins](https://www.elastic.co/guide/en/logstash/current/working-with-plugins.html#updating-plugins) (But you might as well upgrade to Logstash 2.2.1. There's no reason to run anything older.)

Only issue I have with that is I remember reading if you let elasticsearch handle document id the bulk index is much faster?

The only action left then is delete. If record has been removed, will logstash handle that also?

Regards,  
Shane.

---

_[View the full topic](https://discuss.elastic.co/t/ingestion-pipeline/79122)._