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

sqlite3 cache reading re-reading existing files that are in the cache on Connector Restart. #2901

Closed
alextreichler opened this issue Sep 27, 2024 · 1 comment
Labels
bug needs investigation It looks as though have all the information needed but investigation is required

Comments

@alextreichler
Copy link

alextreichler commented Sep 27, 2024

Issue
The following YAML below monitors an SFTP and when a new file is added it reads the file contents to stdout. However, when I restart the redpanda connect service, it reads all the files in the SFTP again - even though they are processed already and in the cache (sqlite3).

Expected behavior:
When redpanda connect is restarted, it should not process the file again that have already been processed in the SFTP as they exist inside the cache.

Sample Yaml

input:
  sftp:
    address: "0.0.0.0:2200"
    credentials:
      username: "foo"
      password: "pass"
    paths:
      - /products/*.csv
    scanner:
      csv:
        custom_delimiter: "|"
        parse_header_row: true
        continue_on_error: false
    watcher:
      enabled: true
      cache: "sql"

output:
  stdout: {}
cache_resources: # []
  - label: "sql"
    sql:
      driver: "sqlite"
      dsn: file:/dir/to/database/file/my.db
      table: sftp_cache
      key_column: foo
      value_column: bar
@mihaitodor mihaitodor added bug needs investigation It looks as though have all the information needed but investigation is required labels Oct 20, 2024
@mihaitodor
Copy link
Collaborator

Should be fixed in v4.45.0. Please let us know if you still encounter this issue in the new versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs investigation It looks as though have all the information needed but investigation is required
Projects
None yet
Development

No branches or pull requests

2 participants