aayush2761 opened a new pull request, #11964: URL: https://github.com/apache/ozone/pull/11964
### What changes are proposed in the PR? and Why? In FSO buckets, a non-shallow key listing whose prefix is also an **existing directory** returned only that directory and its subtree, and omitted other keys that still **match the prefix string** (for example prefix `dir1bh` missed `dir1bha/` and `dir1bha/file1`). That broke parity with LEGACY layout and with S3 ListObjects(V2) when no delimiter is used. This change updates `OzoneListStatusHelper#listStatusFSO` so that when the request is in **listKeys-style partial-prefix** mode (`allowPartialPrefixes` true, non-blank `listPrefix`, normalized `keyName` equal to normalized `listPrefix`) and the path resolves to a **directory**, the listing uses the same **parent-scoped** `getDbKey` path as the existing partial-prefix cases, instead of scoping only to that directory’s object id. ### Context and rationale (third person) The Jira describes creating `dir1bh/file1` and `dir1bha/file1`, listing with prefix `dir1bh`, and observing that FSO omits the `dir1bha` paths while LEGACY does not. Shallow listing with delimiter continues to work; the gap was non-shallow listing driven by the client FSO iterator calling `listStatusLight` with partial prefixes. ### Approach A narrow guard `isListKeysPartialPrefixPath` gates the new branch so normal directory listing (without `listPrefix` / without this equality) is unchanged. Integration tests in `TestListKeysWithFSO` assert full LEGACY parity for the root repro, drop the old FSO-short expected list, add explicit failure when an expected key is missing, and add a nested `parent/dir1bh` scenario. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-17413 ## How was this patch tested? - `mvn -pl :ozone-manager -am install -DskipTests -DskipShade -DskipRecon` - `mvn -pl :ozone-manager checkstyle:check` (if run locally) No UI changes. -- 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]
