ArafatKhan2198 commented on PR #6969:
URL: https://github.com/apache/ozone/pull/6969#issuecomment-2421452084
> @ArafatKhan2198 I understand that why we are assigning the startPrefix as
empty. My original question was not about why you are assigning the startPrefix
as empty. Rather the point is why there is a. need to validate that if API is
already setting default as EMPTY String. That check is redundant.
@devmadhuu
The reason for adding a check to see if the startPrefix is default (empty)
is to handle cases where both startPrefix and prevKey are empty. In such
scenarios, we need to iterate through all the records in the table.
Without this null check, validateStartPrefix would return false because it
mistakenly interprets the empty startPrefix as a volume-level search, which
isn't allowed. By adding a check for an empty string, we explicitly allow this
condition where startPrefix is `""`. Without this, for the default value of
`""`, we would encounter an error and the following would be logged:
```
return createBadRequestResponse("Invalid startPrefix: Path must be at the
bucket level or deeper.");
```
This adjustment ensures the search behaves correctly when startPrefix is
empty, avoiding unnecessary errors.
--
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]
