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

Files are not all removed for azure_blob_storage with max_in_flight value greater than 1 #3189

Open
tifennlegoff opened this issue Feb 18, 2025 · 0 comments

Comments

@tifennlegoff
Copy link

Hi, we're observing that, if we set max_in_flight greater than 1, all files are not removed. With log level at DEBUG we can see that all files are handled, so it's seems to works.

This is our input resource configuration

---
input_resources:
  - label: main
    azure_blob_storage:
      storage_connection_string: ${AZURE_STORAGE_CONNECTION_STRING}
      storage_sas_token: ${AZURE_STORAGE_SAS_TOKEN:""}
      container: ${AZURE_CONTAINER}
      delete_objects: ${AZURE_STORAGE_INPUT_DELETE_OBJECT:true}
      prefix: "replay/"
      scanner:
        to_the_end: {}
      targets_input:
        azure_queue_storage:
          storage_connection_string: ${AZURE_STORAGE_CONNECTION_STRING}
          queue_name: ${AZURE_QUEUE_IN}
          dequeue_visibility_timeout: ${AZURE_DEQUEUE_TIMEOUT:30s}
          max_in_flight: ${AZURE_QUEUE_MAX_IN_FLIGHT:1}
          track_properties: false
        processors:
          - mapping: |-
              let json = content().decode("base64").parse_json()
              if $json.eventType == "Microsoft.Storage.BlobCreated" {
                root.name = $json.data.url.parse_url().path.trim_prefix("/" + env("AZURE_CONTAINER") + "/")
              } else {
                root = deleted()
              }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant