[Input jdbc plugin] Incorrect value on "last_run_metadata_path" file

Elastic Stack Logstash
1

Logstash - v.6.3.2 OSS
ES - v.6.3.2 OSS
Oracle DB

Example input:

	jdbc {
		id => "input_jdbc"
		jdbc_driver_library => "${LOGSTASH_JDBC_DRIVER:ojdbc6.jar}"
		jdbc_driver_class => "Java::oracle.jdbc.OracleDriver"
		jdbc_connection_string => "${LOGSTASH_JDBC_CONNECTION}"
		jdbc_user => "${LOGSTASH_JDBC_USER}"
		jdbc_password => "${LOGSTASH_JDBC_PASSWORD}"
		use_column_value => true
		tracking_column => tracking_number
		last_run_metadata_path => "${LOGSTASH_METADATA_PATH}/main/last_meta"
		statement_filepath => "${LOGSTASH_JDBC_SQL_SCRIPTS_PATH}/main/sript.sql"
		schedule => "* * * * *" #run every minute
	}

Example statement :

select id,name, to_number(to_char(timestamp,'YYMMDDHH24MISSFF')) as tracking_number from test_table where tracking_number > :sql_last_value order by tracking_number

Example row from table table :

 id         |name     |timestamp
 32718938291| my_name | 30-OCT-18 10.10.00.515454000 AM -04:00

Actual result in last_meta file:

--- !ruby/object:BigDecimal '0:0.181029072223314735E18'

Expected result:

--- 181029072223314735

Due to this data is read continuously without stopping.
With what it can be connected?

2

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