ArafatKhan2198 commented on PR #6231:
URL: https://github.com/apache/ozone/pull/6231#issuecomment-2138370143

   Thanks for the initial round of reviews, @devmadhuu and @dombizita.
   
   Could you please check the patch again? I have added more tests to cover 
every possible scenario that the search functionality might encounter.
   
   Here is a short summary of various paths and scenarios tested in the test 
class:
   
   1. **Test Root Level Search Restriction:** Ensures searching at the root 
level returns a bad request.
   2. **Test Volume Level Search Restriction:** Ensures searching at the volume 
level returns a bad request.
   3. **Test Bucket Level Search:** Verifies search results within different 
types of buckets (FSO, OBS, Legacy).
   4. **Test Directory Level Search:** Validates searching inside specific 
directories.
   5. **Test Key Level Search:** Confirms search results for specific keys 
within buckets.
   6. **Test Key Level Search Under Directory:** Verifies searching for keys 
within nested directories.
   7. **Test Search Under Nested Directory:** Checks search results within 
nested directories under `dira3`.
   8. **Test Limit Search:** Tests the limit functionality of the search API.
   9. **Test Search Open Keys with Bad Request:** Ensures bad requests with 
invalid parameters return appropriate responses.
   10. **Test Last Key in Response:** Confirms the presence of the last key in 
paginated responses.
   11. **Test Search Open Keys with Pagination:** Verifies paginated search 
results.
   12. **Test Search in Empty Bucket:** Checks the response for searching 
within an empty bucket.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to