Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Only piggybacking on the Materialization provided by the materialized parameter. It would limit the desired customisation possibilities to the user.
  • Creating a specific class for subscription-stores Materialization - it would increase the API footprint without bringing and code complexity without a good trade-off.
  • Not deprecating the previous API. As agreed on the discussion, a user that is concerned about the materialization method of a table-store is likely concerned with the materialization method of subscription store. 
  • Applying Bug-fix : since to the old API. Since the old API call is being deprecated, users that would be interested on avoiding the opinionated storage should instead use the new API.