aws s3 ls returns unexpected results in Tigris

Questions / Help
1

I ran into some unexpected behavior that I think might be a bug with Tigris.

I’ve been uploading files to a bucket in Tigris using Elixir and then using the aws cli to validate that the files were uploaded successfully. As you know, when you run aws s3 ls s3://bucket/path/ you have to include the trailing slash to have the aws cli expand that “directory” and show its contents.

Typical behavior

# without trailing slash
aws s3 ls s3://bucket/path
         PRE path/

# with trailing slash
aws s3 ls s3://bucket/path/
file1.json
file2.json
...
file10.json

This is typically how it works for me with Tigris as well, but I have a case where running aws s3 ls s3://bucket/path without the trailing slash instead shows the first item in that path. Then if I run it again with the trailing slash, I see that first file and all of the other files as well.

Unexpected behavior

# without trailing slash
aws s3 ls s3://bucket/path
file1.json

# with trailing slash
aws s3 ls s3://bucket/path/
file1.json
file2.json
...
file10.json

If you need the actual bucket and path, I’ll need to DM them to you, since I don’t want this info public.

2

First off, it is great that you are using Tigris :smiley:

We will investigate this issue, as the behavior between S3 and Tigris should be identical.

Could you send the bucket details to help@tigrisdata.com?

1 Like
3

Sent.

4

We have received it thanks.

5

Thank you for reporting this bug. The fix is deployed on production.

1 Like
6

Fabulous! Looks good now. Thanks for the quick response.

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.