You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Nick Reich (JIRA)" <ji...@apache.org> on 2017/06/20 18:26:00 UTC

[jira] [Assigned] (GEODE-2860) refactor EventTracker to be on DistributedRegion instead of LocalRegion

     [ https://issues.apache.org/jira/browse/GEODE-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Reich reassigned GEODE-2860:
---------------------------------

    Assignee: Nick Reich

> refactor EventTracker to be on DistributedRegion instead of LocalRegion
> -----------------------------------------------------------------------
>
>                 Key: GEODE-2860
>                 URL: https://issues.apache.org/jira/browse/GEODE-2860
>             Project: Geode
>          Issue Type: Improvement
>          Components: regions
>            Reporter: Darrel Schneider
>            Assignee: Nick Reich
>              Labels: storage_3
>
> Currently LocalRegion has a non-final field named "eventTracker". It is initialized in a method named createEventTracker which does nothing on LocalRegion but is implemented on DistributedRegion and BucketRegion to initialize the eventTracker field.
> I think things would be clearer if this field was moved to DistributedRegion.
> All the code on LocalRegion that currently tests for a non-null eventTracker can be changed to do nothing and overridden on DistributedRegion to use its eventTracker. DistributedRegion can make this field final and always set it in its constructor. Since BucketRegion extends DistributedRegion it does not to do anything (it currently implements createEventTracker but that was not needed since it inherits the same impl from DistributedRegion).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)