# Multiple pipelines with jdbc\_static

**URL:** <https://discuss.elastic.co/t/multiple-pipelines-with-jdbc-static/129482>\
**Category:** Logstash\
**Created:** [April 25, 2018, 12:21pm UTC](https://discuss.elastic.co/t/multiple-pipelines-with-jdbc-static/129482 "2018-04-25T12:21:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![agriffit](https://avatars.discourse-cdn.com/v4/letter/a/b77776/32.png) [@agriffit](https://discuss.elastic.co/u/agriffit)\
**Post date:** [April 25, 2018, 12:21pm UTC](https://discuss.elastic.co/t/multiple-pipelines-with-jdbc-static/129482/1 "2018-04-25T12:21:00Z")

</div>

I'm planning to do a simple sqlite lookup using jdbc\_static however I am confused by the documentation regards multiple pipelines.

The documentation states that each pipeline will create a unique local instance of the table, but then the preserve\_existing parameter implies that behaviour can be overridden. It's not exactly clear what the benefits/risks of using preserve\_existing are? Is it just to save memory (i.e. only have one local copy)? And how does it interact with the loader\_schedule option? Do I only need to configure that on one pipeline?

Thanks,

Alan

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 23, 2018, 12:31pm UTC](https://discuss.elastic.co/t/multiple-pipelines-with-jdbc-static/129482/2 "2018-05-23T12:31:44Z")

</div>

Closed on May 23, 2018, 12:31pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.