[GitHub] [accumulo] alerman commented on issue #3233: Only use table-scoped properties when creating table with --copy-config

["alerman (via GitHub)" <gi...@apache.org>]

alerman commented on issue #3233:
URL: https://github.com/apache/accumulo/issues/3233#issuecomment-1604257963

   @ctubbsii The Table configuration was not bad, when the table was cloned. Here is the steps that cause this for us:
   
   1. System wide context is set to CONTEXTA (in 1.10 with table.classpath.context, in 2.1.0 with table.class.loader.context) -- This is _not_ set on the table itself
   2. Table SRCTABLE is cloned to DESTTABLE using `-cc`, which adds a table level setting for the above property
   3. CONTEXTB is added, and the property is updated (in 1.10 with table.classpath.context, in 2.1.0 with table.class.loader.context)
   4. After some time, CONTEXTA is deleted
   5. DESTTABLE now throws errors because CONTEXTA is gone
   
   As the user, i have no idea that there is a table level property unless I go check. This isnt expected. SRCTABLE did not have a table level context set, so why does DESTTABLE. This didn't just copy the config, it added new table level properties which were not set on SRCTABLE when the create with copy config was run


-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org