[GitHub] [spark] gaborgsomogyi commented on pull request #26935: [SPARK-30294][SS] Explicitly defines read-only StateStore and optimize for HDFSBackedStateStore

2020-10-23 Thread GitBox
gaborgsomogyi commented on pull request #26935: URL: https://github.com/apache/spark/pull/26935#issuecomment-715217819 On Monday intended to have a look. This is an automated message from the Apache Git Service. To respond to

[GitHub] [spark] gaborgsomogyi commented on pull request #26935: [SPARK-30294][SS] Explicitly defines read-only StateStore and optimize for HDFSBackedStateStore

2020-10-26 Thread GitBox
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 (ap

[GitHub] [spark] gaborgsomogyi commented on pull request #26935: [SPARK-30294][SS] Explicitly defines read-only StateStore and optimize for HDFSBackedStateStore

2020-10-26 Thread GitBox
gaborgsomogyi commented on pull request #26935: URL: https://github.com/apache/spark/pull/26935#issuecomment-716544437 Thanks for the explanation! Your point makes sense (`read-only state only copies the specific version of state from loaded map, which doesn't involve any file operations`)