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

Recursive search only works down one level #9677

Closed
cyberduck opened this issue Aug 31, 2016 · 4 comments
Closed

Recursive search only works down one level #9677

cyberduck opened this issue Aug 31, 2016 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 31, 2016

7a6b8e0 created the issue

I did some searching around and couldn't decide if this was intentional or not, so feel free to close this as such if it is.

Recursive searching only works one level deep. For example, if I have a path with some files that looks like:

/Bucket/Collections/Bob/Date1/SomeRecording1.wav
/Bucket/Collections/Bob/Date1/SomeRecording2.wav
/Bucket/Collections/Bob/Date1/SomeRecording3.wav
/Bucket/Collections/Bob/Date2/SomeRecording1.wav
/Bucket/Collections/Bob/Date2/SomeRecording2.wav
/Bucket/Collections/Bob/Date2/SomeRecording3.wav
/Bucket/Collections/Steve/Date1/SomeRecording1.wav
/Bucket/Collections/Steve/Date1/SomeRecording2.wav
/Bucket/Collections/Steve/Date1/SomeRecording3.wav
/Bucket/Collections/Steve/Date2/SomeRecording1.wav
/Bucket/Collections/Steve/Date2/SomeRecording2.wav
/Bucket/Collections/Steve/Date2/SomeRecording3.wav

If I drill down to the person's name and try to search, I'll get the expected resulting date folders that have contents that match. This is fine.

If I back up to a lower directory, however, and try searching no results will be found. Based on the time, logs, and status bars it seems like it's poking through the directories, but never returns any paths. This is preventing me from searching for matches among multiple directories. I couldn't sit in /Bucket and search on "SomeRecording1" and have it return all the directories that have that. I've tried expanding out the directories as much as I can in case that's related somehow, but I have too many files to practically expand it that far.

Here's a snippet of the logs. They're all basically like this as it walks through the tree. Apologies for the weird formatting, it wasn't including newlines properly.

  GET /?max-keys=1000&prefix=recordings%2FCollections%20-%20Broken%20Promise%2F7_1_2016%2F&delimiter=%2F HTTP/1.1
  Date: Wed, 31 Aug 2016 15:23:37 GMT
  x-amz-request-payer: requester
  x-amz-content-sha256: sha256 key  
  Host: bucket.s3.amazonaws.com
  x-amz-date: 20160831T152337Z
  Authorization: auth stuff
  Connection: Keep-Alive
  User-Agent: Cyberduck/5.2.0.20906 (Windows 10/10.0) (x86)
  HTTP/1.1 200 OK
  x-amz-id-2: amz id info
  x-amz-request-id: 1CDB3FEB58747DCA
  Date: Wed, 31 Aug 2016 15:23:38 GMT
  x-amz-bucket-region: us-east-1
  Content-Type: application/xml
  Transfer-Encoding: chunked
  Server: AmazonS3

Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2016

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2016

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 17, 2016

@dkocher commented

I cannot reproduce this issue. Can you please double check your search term. Note that it will only attempt the directories the first time you search but will subsequently use cached entries. You might need to Reload the browser view.

@cyberduck cyberduck closed this Oct 17, 2016
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 19, 2016

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants