Skip to content

S3 Destination ignoring s3_path_format argument #11482

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

Closed
leoalmeidasant opened this issue Mar 28, 2022 · 1 comment · Fixed by #11496
Closed

S3 Destination ignoring s3_path_format argument #11482

leoalmeidasant opened this issue Mar 28, 2022 · 1 comment · Fixed by #11496
Labels
area/connectors Connector related issues connectors/destination/s3 type/bug Something isn't working

Comments

@leoalmeidasant
Copy link

Environment

  • Airbyte version: example is 0.35.59-alpha
  • OS Version / Instance: AWS EKS
  • Deployment: Kubernetes
  • Destination Connector and version: s3-destination 0.2.12
  • Severity: medium
  • Step where error happened: Sync job

Current Behavior

After upgrading s3 destination connector from 0.2.10 to 0.2.12, the output ignoring argument s3_bucket_path in s3 path.

S3 Bucket Name = bucket-example
s3_bucket_path = foo
ouput_path will be s3://bucket-example/${SOUCE_NAMESPACE}/${STREAM_NAME}

Expected Behavior

output_path should be s3://bucket-example/foo/${SOUCE_NAMESPACE}/${STREAM_NAME}

Steps to Reproduce

  1. create a source
  2. create destination and keep empty the field s3_path_format
  3. create a connection and sync
@ChristopheDuong
Copy link
Contributor

ChristopheDuong commented Mar 29, 2022

Thanks for reporting this!
it should be fixed with a new version and I also updated the docs accordingly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues connectors/destination/s3 type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants