Logstash Configuarion file issue

Elastic Stack Logstash
4

@Syed.Ubaid -

  1. It seems that you are facing the same issue as what was reported in this Discuss topic.

The last run metadata file will store the sql_last_value and It is updated accordingly after subsequent queries are run.

It seems that Logstash cannot parse the value stored in this file. It could be because you have been running Logstash with different SQL statements and the sql_last_value type keeps on changing?

  1. What you could try:
  • use the clean_run option to ignore the previous state. or,
  • use use_column_value option along with the tracking_column option. or,
  • delete the last run metadata file but I believe this would only be a temporary solution.

I hope that helps.