ddanielr commented on issue #3233: URL: https://github.com/apache/accumulo/issues/3233#issuecomment-1604319936
TL;DR Would adding a `overrides only` flag for the table clone config (`-cc`) command work as a solution? @alerman I made a visual based off your steps. Original State: | Tables | Table Property | System Properties | | ------------- | ------------- | ------------- | | SRCTABLE | N/A | table.class.loader.context=CONTEXT-A | After Table Clone using `-cc`: | Tables | Table Properties | System Properties | | ------------- | ------------- | ------------- | | SRCTABLE | N/A | table.class.loader.context=CONTEXT-A | | DESTTABLE | table.class.loader.context=CONTEXT-A | table.class.loader.context=CONTEXT-A | A new system context is created (CONTEXT-B) and the old context (CONTEXT-A) is deleted: | Tables | Table Properties | System Properties | | ------------- | ------------- | ------------- | | SRCTABLE | N/A | table.class.loader.context=CONTEXT-B | | DESTTABLE | table.class.loader.context=CONTEXT-A | table.class.loader.context=CONTEXT-B | DESTTABLE now throws errors due to the missing CONTEXT-A Validating the table config is time consuming as it is also a per-table check rather than a per-property check. The `config -f table.class.loader.context` command doesn't show per-table properties overrides unless a specific table name is also passed `config -t DESTTABLE -f table.class.loader.context`. Any table clone operation run would need a comparison of the `@override` results of both table configs. Given that the overrides are probably the only desired parts of the table config in this scenario, is it possible to just selectively copy those out to the clone table? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
