# Logstash jdbc input state
**URL:** https://discuss.elastic.co/t/logstash-jdbc-input-state/321192
**Category:** Logstash
**Tags:** elastic-stack-sql, jdbc
**Created:** [December 14, 2022, 8:09am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-state/321192 "2022-12-14T08:09:04Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Mahdi\_Moazami](https://discuss.elastic.co/u/Mahdi_Moazami)
#### Post date: [December 14, 2022, 8:09am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-state/321192/1 "2022-12-14T08:09:04Z")
Hi there elastic team,
Suppose i have multiple pipelines each with one jdbc input. each of them execute a sql query that uses the value of **sql\_last\_value** to fetch only updated data and each pipeline file targets a specific table in db.
My question is that is it necessary to define **last\_run\_metadata\_path** param for each of the pipelines so that the state of 'sql\_last\_value' be specific to that pipeline and not be shared among jdbc inputs or the logstash by default consider a seperate file for each pipeline to keep the state of them?
---
### Author:  [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [December 14, 2022, 3:43pm UTC](https://discuss.elastic.co/t/logstash-jdbc-input-state/321192/2 "2022-12-14T15:43:48Z")
> [@Mahdi\_Moazami](#):
>
> is it necessary to define **last\_run\_metadata\_path** param for each of the pipelines so that the state of 'sql\_last\_value' be specific to that pipeline and not be shared among jdbc inputs
Yes, it is.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 11, 2023, 3:44pm UTC](https://discuss.elastic.co/t/logstash-jdbc-input-state/321192/3 "2023-01-11T15:44:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.