gaborgsomogyi commented on pull request #26935: URL: https://github.com/apache/spark/pull/26935#issuecomment-716437353
Just for my own understanding is it possible/does it make sense from use-case perspective to differentiate the implementation of a read-only and read-write state store (apart from modification APIs are throwing exceptions in read-only)? If no then why do we need 2 different public APIs? If the read-only stuff is just a wrapper which makes sense only internally (enforcing read-only behavior) we can use decorator pattern which is not public. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
