# \[Logstash\]\[jdbc input plugin\]sql\_last\_value with timestamp type support milliseconds?

**URL:** <https://discuss.elastic.co/t/logstash-jdbc-input-plugin-sql-last-value-with-timestamp-type-support-milliseconds/218520>\
**Category:** Logstash\
**Created:** [February 10, 2020, 6:33am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-plugin-sql-last-value-with-timestamp-type-support-milliseconds/218520 "2020-02-10T06:33:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ztkmkoo](https://avatars.discourse-cdn.com/v4/letter/z/85e7bf/32.png) [@ztkmkoo](https://discuss.elastic.co/u/ztkmkoo)\
**Post date:** [February 10, 2020, 6:33am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-plugin-sql-last-value-with-timestamp-type-support-milliseconds/218520/1 "2020-02-10T06:33:43Z")

</div>

Hi,  
I try to collect my data from mysql (or cubrid) to elasticsearch and hadoop. (test with logstash 7.5.2 on my local windows 10 desktop)

And found `sql_last_value ` is not worked as i expected.

Its my config

```auto
input {
  jdbc {
	jdbc_driver_library => "E:\Work\Elastic\logstash-7.5.2\mysql-connector-java-5.1.42.jar"
	jdbc_driver_class => "com.mysql.jdbc.Driver"
	jdbc_connection_string => "~"
        jdbc_user => "~"
	jdbc_password => "~"
	jdbc_paging_enabled => true
	jdbc_page_size => 10
	jdbc_default_timezone => "Asia/Seoul"
    schedule => "*/1 * * * *"
    statement => "SELECT * FROM fds_hard_rule_check_log WHERE check_ymdt > :sql_last_value ORDER BY hard_rule_check_log_seq"
	use_column_value => true
	tracking_column => "check_ymdt"
	tracking_column_type => "timestamp"
  }
}

filter {
	sleep {
		time => "1"
	}
}

output {
  elasticsearch {
	hosts => ["~"]
	index => "fds_hard_rule_check_log"
	document_id => "%{hard_rule_check_log_seq}"
  }
}

```

and logstash work like this

 ![ls1](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c7208a01cae5174557e46498cc63d9dc776c0521.png)

but the check\_ymdt field in mysql is timestamp(3).  
 ![ls2](https://us1.discourse-cdn.com/elastic/original/3X/9/8/98739a5b3bf337c6ffcd1b7e72156d37b730b436.png)

so logstash always select with check\_ymdt \> 2020-02-07 16:39:28 and the row with 2020-02-07 16:39:28.212 was always selected duplicated.

i found select query is not support milliseconds. but i found `.logstash_jdbc_last_run` file, it saved milliseconds info.

```ruby
--- !ruby/object:DateTime '2020-02-07 16:39:28.212000000 +09:00'

```

I just wonder its a bug or just not support milliseconds yet.

---

<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:** [March 9, 2020, 6:43am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-plugin-sql-last-value-with-timestamp-type-support-milliseconds/218520/2 "2020-03-09T06:43:12Z")

</div>

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