milleruntime commented on pull request #1968: URL: https://github.com/apache/accumulo/pull/1968#issuecomment-808237782
> general.* would also work (and could be changed at runtime, unlike instance.*). The main point here is that these aren't characteristics of the table, but rather, characteristics of the crypto service module that inform it of how to behave in specific contexts. Using the general prefix might work. I think being able to change the configuration at runtime is important when dealing with per-table changes. But I think by not including encryption as a table characteristic we are pushing more complexity to the user and creating more complexity in the code. Instead of the user configuring the service like they would other table specific classes (balancer, scan dispatcher) they have to know specialized options within the service (they will have to know some, key location etc). Then Accumulo has to deal with special circumstances of having general properties that operate on a per-table basis. How will table operations like clone or export table know how to include encryption as part of the operation? As a user, I would expect a cloned table to also be encrypted. It seems you are creating a lot of complexity just to save a few properties. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
