Description
Accumulo supports user supplied application code running on the server side, but it does not currently share the configuration space with users.
Two specific examples come to mind, but there may be others:
1. Users can supply their own tablet balancer, but have no way to configure it. I can envision a balancer implementation that allows an administrator to modify the number of migrations per iteration by manipulating a property.
2. Users can supply their own iterator implementations. The same iterator class can be applied to multiple tables, each with their own configuration. The behavior of an iterator could be modified at runtime by an administrator by manipulating one property instead of modifying the iterator configuration on each table where it is being used.
Need to think about property visibility...
Attachments
Issue Links
- duplicates
-
ACCUMULO-2841 Arbitrary namespace and table metadata tags
- Resolved