rishii-19-works commented on issue #3243: URL: https://github.com/apache/polaris/issues/3243#issuecomment-3671153052
Hi @pingtimeout thanks for raising this issue. I’ve gone through the flow and understand that the failure occurs because the STS policy generated by Polaris becomes too large when namespaces are deeply nested, eventually exceeding AWS policy size limits during table creation. I’d like to take this up and work on a fix. My current thinking is to reduce the size of the generated policy (for example, by consolidating policy statements) and/or add early validation so the failure is caught with a clearer, Polaris-level error instead of an AWS exception. Please let me know if there’s a preferred direction or any design constraints I should be aware of before I start implementing. -- 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]
