ctubbsii opened a new issue, #2692: URL: https://github.com/apache/accumulo/issues/2692
**Is your feature request related to a problem? Please describe.** After #2569 was merged, we now have the groundwork in place to set multiple properties on a table (or for the system configuration) atomically, instead of setting one at a time, as we have today. There are lots of benefits to setting multiple properties atomically. Locality group configuration, and iterator configuration are two situations where multiple properties are set. Weird things can happen if the tserver only picks up a subset of these configurations at a time. So, it's nice to see all or none of the changes. **Describe the solution you'd like** A new public API on InstanceOperations, NamespaceOperations, and TableOperations, to atomically set a map of properties on system configuration, namespace configuration, and table configuration, respectively. The provided map should just replace whatever properties were set before. Maybe something like `replaceProperties(Map)` **Describe alternatives you've considered** This could be implemented using a Map mutator... so you can supply a set of put/remove operations to mutate the existing configuration atomically. It could also be made to be conditional, so the operation fails if there's a collision with another set of mutations. However, this would increase complexity quite a bit and probably isn't needed. **Additional context** I spoke with @tchaie about working on this already. This issue is to document and track some of the details needed to make this happen. The implementation will require changes to the RPC layer to send properties to a server for setting them atomically. -- 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]
