Description
Classpath contexts are assigned to a table via the table configuration. You can test at scale by cloning your table and assigning a new classpath context to the cloned table. However, you would also need to change your application to use the new table names and since we cannot disable compactions you would start to consume more space in the filesystem for that table. We can support users passing in a context name to use for the scan on existing tables.
Attachments
Attachments
Issue Links
- is related to
-
ACCUMULO-4054 Add optional context name to TableOperations.testClassLoad
- Resolved
-
ACCUMULO-4055 Add test in ConditionalWriterIT for setting context name on Scanner
- Resolved
- relates to
-
ACCUMULO-4169 TabletServer.config contextCleaner removes contexts that are not set on a table
- Resolved
-
ACCUMULO-4058 mvn test on ScannerContextIT will fail if test jar is not already built.
- Resolved
-
ACCUMULO-4057 Duplicated code in IteratorUtil
- Resolved
- links to