Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Abandoned
-
None
-
None
-
None
-
None
Description
Currentlyif a user wants to have multiple iterator configurations for a table, they must be individually set on the scanner. This makes it difficult, so we should provide the ability for a table to have profiles. By default we should also support a naked profile for use by client side deletes so transformed keys do not create problems.
Attachments
Issue Links
- is related to
-
ACCUMULO-1397 Provide shell support for .accumulorc file
- Resolved
-
ACCUMULO-1635 Support external configuration in client API
- Resolved
-
ACCUMULO-1228 Allow clients to disable column families and locality groups
- Resolved
-
ACCUMULO-1726 Typed configuration framework
- Resolved
- relates to
-
ACCUMULO-759 remove priority setting for scan-time iterators
- Open