EdColeman commented on PR #3562:
URL: https://github.com/apache/accumulo/pull/3562#issuecomment-1624150468

   BLUF - I am not seeing clone copy the configuration hierarchy - it seems to 
copy the appropiate properties, and upgrade from 1.10 -> 2.1 seems okay too,
   
   I checked clonetable and what happens during an upgrade.  Basically, set 
custom system and namespace props, cloned the table and then upgraded from 1.10 
to 2.1-SNAPSHOT.  The resulting properties of the clone in 2.1 look as 
expected.  The clone does not have properties inherited from the configuration 
stored as table properties.
   
   In 2.1, after the upgrade - the shell shows:
   ```
   root@uno> config -f custom -t ns1.tbl1_clone1
   
-----------+--------------------------+---------------------------------------
   SCOPE      | NAME                     | VALUE
   
-----------+--------------------------+---------------------------------------
   namespace  | table.custom.ns_prop ... | ns1_v1
   site       | table.custom.sys_prop .. | 
   system     |    @override ........... | sys_v1
   
-----------+--------------------------+---------------------------------------
   ```
   
   And this is confirmed by looking at the properties stored in the ZooKeeper 
node 
   ```
   > accumulo zoo-info-viewer -t ns1.tbl1_clone1 --print-props
   
   Tables: 
   Name: ns1.tbl1_clone1, Data Version:0, Data Timestamp: 
2023-07-06T18:25:17.356529Z:
     
table.constraint.1=org.apache.accumulo.core.constraints.DefaultKeySizeConstraint
     
table.iterator.majc.vers=20,org.apache.accumulo.core.iterators.user.VersioningIterator
     table.iterator.majc.vers.opt.maxVersions=1
     
table.iterator.minc.vers=20,org.apache.accumulo.core.iterators.user.VersioningIterator
     table.iterator.minc.vers.opt.maxVersions=1
     
table.iterator.scan.vers=20,org.apache.accumulo.core.iterators.user.VersioningIterator
     table.iterator.scan.vers.opt.maxVersions=1
   ```
   


-- 
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]

Reply via email to