This command line tools is used to do one-off migration task from legacy file based storage to new path mapped storage
There are two commands here: scan and migrate
Usage: java -jar ${package}.jar scan [options]
Options:
-B (--batch) : Batch of paths to process each time
-b (--base) : Base dir of storage for all indy artifacts
-w (--workdir) : Work dir to store all generated working files
-f (--filter) : Regex style filter string to filter some files which are unwanted
-t (--threads) : Threads will run concurrently to scan against repos for pkg types
Usage: java -jar ${package}.jar migrate [options]
Options:
-w (--workdir) : Work dir to store all generated working files
-b (--base) : Base dir of storage for all indy artifacts
-H (--host) : Cassandra server hostname
-P (--port) : Cassandra server port
-k (--keyspace) : Cassandra server keyspace
-p (--password) : Cassandra server password
-u (--user) : Cassandra server username
-d (--dedupe) : If to use checksum to dedupe all files in file storage
-t (--threads) : Threads which will run migrating concurrently
-i (--indexGA) : Determine if to index GA cache during migrate operation
-c (--cacheTable): Indy cache table in cassandra, should come with keyspace together
-g (--indexGAStorePattern): The store pattern for stores which will be cached in GA cache
For migrate command, when it start, there will be a "status" file generated in ${workDir} to record current processing status, and will be updated every 30 seconds.