| commit | 02a5c7ceae7da2e4f6bfb22e781f59c1d4e921bc | [log] [tgz] |
|---|---|---|
| author | Russell Branca <chewbranca@gmail.com> | Wed Apr 30 14:28:36 2014 -0700 |
| committer | Robert Newson <rnewson@apache.org> | Wed Jul 30 18:16:34 2014 +0100 |
| tree | 48ebcda7f72f5a0de855ec59133f1e87bea9942b | |
| parent | c1bb498b37d9055822fcd10d66adc6e305502ff7 [diff] |
Use shard suffix in the security metadata id The primary purpose here is to be able to distinguish between different version of the same database name. We shouldn't have security properties be inherited when a database is recreated. Adding the suffix to the metadata id allows us to make this distinction, but it also allows us to lazily deal with clearing out security docs for old deleted database.