CoderNasim2023 commented on issue #58475: URL: https://github.com/apache/spark/issues/58475#issuecomment-5995265890
এই comment-টি দিতে পারেন: > Hi, I am interested in investigating this issue. I understand the problem as a credential-rotation gap for long-running JDBC reads, where credentials are captured when the reader is created but may expire before execution/materialization. > > Before proposing an implementation, could you clarify the preferred scope? > > 1. Should credential refresh happen during JDBC connection creation for each partition/task? > 2. Should Spark accept a credential provider or callback instead of static JDBC options? > 3. Should the reader retry with refreshed credentials after an authentication failure? > 4. Is the expected solution specific to Spark JDBC, or should it be designed for other DataSource V2 integrations as well? > > I would like to first confirm the expected API and retry semantics with the maintainers before preparing a PR. @tmaoz -- 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]
