ctubbsii opened a new issue, #3529: URL: https://github.com/apache/accumulo/issues/3529
I was thinking through some of the problems that could occur with a misuse of `AccumuloConfiguration.isPropertySet`, and it occurred to me that it might be possible for the `SystemConfiguration` class to report that some properties are set when they no longer are. This is due to the way we handle certain "fixed" properties that cannot be changed at runtime. We still allow these properties to be set, but they will only take effect on a restart. For example, if `gc.port` is set in ZooKeeper at system startup, it will be added to the `RuntimeFixedProperties`. Calls to `SystemConfiguration.isPropertySet(Property.GC_PORT` will return true, even if the property is deleted from ZooKeeper. But if it was not initially set (and used a default value), then was subsequently set, it will still return true. So, the affirmative result is not revealing the presence of the property in the current runtime, or the current value in ZK, separately, but the `OR` of those two. This is not necessarily a bug, and so I will close this issue immediately after opening, because I don't know that there's anything to be done about it. After all, `isPropertySet` is an internal API only. But, I wanted to document this strangeness, for reference, if it becomes an issue in future. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
