snazy opened a new pull request, #4545: URL: https://github.com/apache/polaris/pull/4545
Put a hard cap on the inline NoSQL policy-mapping value size. That value sits directly in the shared policy-mappings index, so leaving it unbounded lets one attachment bloat commit size and maintenance work for no real gain. Polaris still accepts client-supplied policy-mapping parameters on the attach-policy request and persists them inline in the NoSQL policy-mappings index. I could not find any in-tree first-party caller that intentionally sets up a non-empty parameter bag itself, but the field is still live API surface, so the cap belongs in the NoSQL write path as a defensive bound on that inline index value. -- 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]
