Removing the observers requires rewriting the entire mechanism for handling configuration changes that observers are currently handling. It's not a simple replacement of the existing methods to an equivalent set of methods. It would have to be rewritten to leverage ZooCache's ability to track changes with a counter, and to reload when that counter is different.
On Tue, May 14, 2019 at 9:54 PM d resnik <[email protected]> wrote: > > Devs, > I am trying to work on this ticket, but I am getting stuck. > Remove observers from configuration · Issue #1123 · apache/accumulo > > > | > | > | > | | | > > | > > | > | > | | > Remove observers from configuration · Issue #1123 · apache/accumulo > > https://issues.apache.org/jira/browse/ACCUMULO-4822 > | > > | > > | > > > Specifically, what should I do in NamespaceConfWatcher in the case on line 94 > > case None: > > switch (event.getState()) { > > case Expired: > > ServerConfigurationFactory.expireAllTableObservers(); > break; > Which ends up trying to call expireAllObservers() on all the > TableConfigurations. This method is no longer available because > TableConfiguration now extends AccumuloConfigruation in my branch. > What is the equivalent to expireAllTableObservers() and/or > expireAllObservers() if I remove all the Observer refs? Or does this case > even need to be there without the Observer classes. > Any ideas would be appreciated. > Thanks, > Don
