[
https://issues.apache.org/jira/browse/GEODE-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317743#comment-16317743
]
Swapnil Bawaskar commented on GEODE-4234:
-----------------------------------------
Users should not have to pay the performance penalty if this flag is set, but
not all operations are transactional. We should have selectively enable this
property on a per-thread basis only for the threads that call
{{CacheTransactionManager.begin()}}.
> Add ability to enable global copy-on-read via gfsh
> --------------------------------------------------
>
> Key: GEODE-4234
> URL: https://issues.apache.org/jira/browse/GEODE-4234
> Project: Geode
> Issue Type: New Feature
> Components: docs, gfsh, transactions
> Reporter: Michael Dodge
> Fix For: 1.5.0
>
>
> A cache supports a "copy on read" feature for cache read operations. (See
> [http://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/GemFireCache.html#setCopyOnRead-boolean-])
> The documentation for transactions
> ([https://geode.apache.org/docs/guide/11/developing/transactions/run_a_cache_transaction.html])
> recommends enabling this feature. However, the documentation for enabling
> this feature
> ([https://geode.apache.org/docs/guide/11/developing/transactions/working_with_transactions.html#concept_vx2_gs4_5k])
> only shows how to enable it via {{cache.xml}} or Java inside the server.
> There should be a way to enable the "copy on read" feature for a cache using
> {{gfsh}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
