Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use_tracking_column uses last read value from result set instead of the maximal value #131

Open
L00kian opened this issue May 12, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@L00kian
Copy link

L00kian commented May 12, 2023

Logstash information:

  1. Logstash version - 8.6.1
  2. Logstash installation source - Docker
  3. How is Logstash being run - container in kubernetes deployment
  4. How was the Logstash Plugin installed - bundled

JVM: Bundled

OS version: Bundled

Description of the problem including expected versus actual behavior:

Expected result: when running a query with 'use_tracking_column' set to true it is expected that plugin will use maximal value read (since documentation doesn't state otherwise)
Actual result: the last read value is used (i.e last in the result set)

Steps to reproduce:

Use any query that is not ordered by the 'use_tracking_column' column

@L00kian L00kian added the bug Something isn't working label May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant