# Is Logstash JDBC tracking\_column meant to work with BIGINT?

**URL:** <https://discuss.elastic.co/t/is-logstash-jdbc-tracking-column-meant-to-work-with-bigint/280856>\
**Category:** Logstash\
**Created:** [August 10, 2021, 12:40am UTC](https://discuss.elastic.co/t/is-logstash-jdbc-tracking-column-meant-to-work-with-bigint/280856 "2021-08-10T00:40:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![catmanjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catmanjan/32/77810_2.png) [@catmanjan](https://discuss.elastic.co/u/catmanjan)\
**Post date:** [August 10, 2021, 12:40am UTC](https://discuss.elastic.co/t/is-logstash-jdbc-tracking-column-meant-to-work-with-bigint/280856/1 "2021-08-10T00:40:40Z")

</div>

I have a Logstash JDBC configuration with tracking\_column set to a BIGINT of the format YYYYMMDDhhmmsss

This is obviously a very big number and the value set in last\_run\_metadata\_path is always set to zero.

If I use a different BIGINT tracking\_column which has small numbers it works as expected.

Is this a bug?

---

<div class="post-metadata">

**Author:** ![catmanjan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/catmanjan/32/77810_2.png) [@catmanjan](https://discuss.elastic.co/u/catmanjan)\
**Post date:** [August 10, 2021, 1:50am UTC](https://discuss.elastic.co/t/is-logstash-jdbc-tracking-column-meant-to-work-with-bigint/280856/2 "2021-08-10T01:50:14Z")

</div>

Here is my config:

```auto
input {
	jdbc {
		jdbc_driver_library => "C:\sqljdbc_6.0\enu\jre8\sqljdbc42.jar"
		jdbc_driver_class => "com.microsoft.sqlserver.jdbc.SQLServerDriver"
		jdbc_connection_string => "jdbc:sqlserver://sql;databaseName=database;username=username;password=password;"
		jdbc_user => "username"
		jdbc_password => "password"
		schedule => "* * * * * *"
		statement => "select top(1) lastupdated from table where cast(lastupdated as bigint) > :sql_last_value order by lastupdated asc"
		use_column_value => true
		tracking_column => "lastupdated"
		tracking_column_type => "numeric"
		last_run_metadata_path => "C:\logstash-7.14.0-windows-x86_64\logstash-7.14.0\config\sql_last_value.yml"
	}
}
output {
	stdout { codec => json }
}

```

The sql\_last\_value.yml file just contains `--- 0`

---

<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:** [September 7, 2021, 1:50am UTC](https://discuss.elastic.co/t/is-logstash-jdbc-tracking-column-meant-to-work-with-bigint/280856/3 "2021-09-07T01:50:43Z")

</div>

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