aws s3 ls returns unexpected results in Tigris

I ran into some unexpected behavior that 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/

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

# 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

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

# 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

The bucket and path can be provided privately.

aws s3 ls returns unexpected results in Tigris

aws s3 ls s3://bucket/path/

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

# 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

aws s3 ls s3://bucket/path

# 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

# 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

The bucket and path can be provided privately.

aws s3 ls returns unexpected results in Tigris

Similar Threads

aws s3 ls returns unexpected results in Tigris

Similar Threads

Similar Threads

Similar Threads