[
https://issues.apache.org/jira/browse/GEODE-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred Krone updated GEODE-3676:
------------------------------
Description:
We are going to create a new processor users can configure to run before or
after an entry is put into the CacheWriter.
Use cases:
1) Needing to update an entry when doing write behind caching. For example --
inserting into a DB and needed to add the auto generated id to the domain
object entry.
2) Needing to update an entry when doing read trough. Example: needing to
update a PdxInstance on-the-fly. Per Gideon's example here:
https://jira-pivotal.atlassian.net/browse/GEM-1569
How we do this probably will model how we do pre / post processing for
diskstores for encryption.
was:Allow cache writer to modify the incoming value before getting put into
gemfire
> Allow CacheWriter to modify a value before being put into the cache
> -------------------------------------------------------------------
>
> Key: GEODE-3676
> URL: https://issues.apache.org/jira/browse/GEODE-3676
> Project: Geode
> Issue Type: Improvement
> Components: regions
> Reporter: Fred Krone
> Assignee: Lynn Gallinat
>
> We are going to create a new processor users can configure to run before or
> after an entry is put into the CacheWriter.
> Use cases:
> 1) Needing to update an entry when doing write behind caching. For example
> -- inserting into a DB and needed to add the auto generated id to the domain
> object entry.
> 2) Needing to update an entry when doing read trough. Example: needing to
> update a PdxInstance on-the-fly. Per Gideon's example here:
> https://jira-pivotal.atlassian.net/browse/GEM-1569
> How we do this probably will model how we do pre / post processing for
> diskstores for encryption.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
