# \[logstash-input-jdbc plugin\] Additional tracking column types

**URL:** <https://discuss.elastic.co/t/logstash-input-jdbc-plugin-additional-tracking-column-types/109523>\
**Category:** Logstash\
**Created:** [November 29, 2017, 7:20am UTC](https://discuss.elastic.co/t/logstash-input-jdbc-plugin-additional-tracking-column-types/109523 "2017-11-29T07:20:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashabunevich](https://avatars.discourse-cdn.com/v4/letter/a/59ef9b/32.png) [@ashabunevich](https://discuss.elastic.co/u/ashabunevich)\
**Post date:** [November 29, 2017, 7:20am UTC](https://discuss.elastic.co/t/logstash-input-jdbc-plugin-additional-tracking-column-types/109523/1 "2017-11-29T07:20:57Z")

</div>

**Hello** ,

In current version of Logstash (6.0) only two data types are supported for **"tracking\_column\_type"**. It is **numeric** and **timestamp**.

Is it possible somehow to use **[RowVersion](https://docs.microsoft.com/en-us/sql/t-sql/data-types/rowversion-transact-sql) data type** which is semantically equivalent to a **binary(8)** column?

Using existing timestamp data type is not always an option. For example, if we are using **jdbc\_paging\_enabled** and several rows have the same value in tracking column then we may have data loss if these rows "lies" on the border of the two pages.

---

<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:** [December 27, 2017, 7:21am UTC](https://discuss.elastic.co/t/logstash-input-jdbc-plugin-additional-tracking-column-types/109523/2 "2017-12-27T07:21:01Z")

</div>

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