[
https://issues.apache.org/jira/browse/GEODE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575303#comment-16575303
]
Darrel Schneider commented on GEODE-5487:
-----------------------------------------
A new feature should be discussed on the geode user forum.
Can you send a proposal to that forum of this feature?
It should propose what APIs will change, what the behavior is, and possible
alternatives.
For example: should this be enabled by a RegionAttribute using api, gfsh, xml,
or by a system property?
What level should it be at (region, or transaction or connection)?
> Choice of detect read conflict on transaction commit on a per-region basis.
> ---------------------------------------------------------------------------
>
> Key: GEODE-5487
> URL: https://issues.apache.org/jira/browse/GEODE-5487
> Project: Geode
> Issue Type: Improvement
> Components: docs, transactions
> Reporter: Eugene Nedzvetsky
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Geode supports detect read conflict(-Dgemfire.detectReadConflicts=true) on
> transaction commit(see
> https://geode.apache.org/docs/guide/11/developing/transactions/transaction_semantics.html)
> This functionality can be enabled only on application level. It can
> dramatically decrease application performance.
> I propose to add ability to setup this property per region basis.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
