netapp-acheng commented on issue #3440: URL: https://github.com/apache/polaris/issues/3440#issuecomment-3780079794
@MonkeyCanCode You wrote: Do you mind also help to confirm if the second fix is necessary in case we mixed changes due to alignment in the testing (which you reported without it, it won't be using the right STS credential but AWS secret/key instead)? Based on my understanding, without the 2nd fix, table would lost its write capabilities after a metadata refresh (thus I implicitly added it back). If preferred, I can submit 2 PRs later tonight then wait for final confirmation before merge them in assuming approved by the Polaris dev team. I assume the 2nd fix referring to the change you made on Jan 19: > I am suspected the issue is within table refresh and I had pushed additional changes to https://github.com/apache/polaris/pull/3445. Yes, this fix is necessary. -- 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]
