PircDef commented on pull request #1968:
URL: https://github.com/apache/accumulo/pull/1968#issuecomment-808278751
> In short: centralized pluggable services, that have per-table config I
think is better than having per-table services.
I think I must be misunderstanding something. How do you envision this for
tables that are imported from users that do not use the existing service at
all? I'm thinking of the word service as roughly meaning "encrypter, decrypter,
and key utilities". The PR has even less, leaving the utilities up to the
encrypter/decrypters.
```
public interface CryptoService {
enum Scope {WAL, RFILE}
FileEncrypter getEncrypter();
FileDecrypter getDecrypter();
}
```
Lets assume that an Accumulo instance is running with the default crypto
service (AESCryptoService) enabled. User A wants to import their table, and
they have a custom encrypter/decrypter. Additionally, they have some custom
utilities for communicating with their key server. Under this pull request, all
of this custom software would be bundled under the UserACryptoService, and
Accumulo would have to be configured to use this service when requested by the
table.
How do you see this working with a centralized pluggable service?
--
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]
