aboutsummaryrefslogtreecommitdiffstats
path: root/src/main/scripts/schemaMod.sh
diff options
context:
space:
mode:
Diffstat (limited to 'src/main/scripts/schemaMod.sh')
-rw-r--r--src/main/scripts/schemaMod.sh29
1 files changed, 15 insertions, 14 deletions
diff --git a/src/main/scripts/schemaMod.sh b/src/main/scripts/schemaMod.sh
index d1fb009..c7b8ce9 100644
--- a/src/main/scripts/schemaMod.sh
+++ b/src/main/scripts/schemaMod.sh
@@ -3,20 +3,17 @@
# This script is used to correct mistakes made in the database schema.
# It currently just allows you to change either the dataType and/or indexType on properties used by nodes.
#
-# NOTE - Titan is not elegant in 0.5.3 about making changes to the schema. Bad properties never
-# actually leave the database, they just get renamed and stop getting used. So it is
-# really worthwhile to get indexes and dataTypes correct the first time around.
+# NOTE - JanusGraph is not particularly elegant in about making changes to the schema.
+# So it is really worthwhile to get indexes and dataTypes correct the first time around.
# Note also - This script just makes changes to the schema that is currently live.
# If you were to create a new schema in a brandy-new environment, it would look like
-# whatever ex5.json (as of June 2015) told it to look like. So, part of making a
-# change to the db schema should Always first be to make the change in ex5.json so that
-# future environments will have the change. This script is just to change existing
-# instances of the schema since schemaGenerator (as of June 2015) does not update things - it
-# just does the initial creation.
+# whatever our OXM files told it to look like. So, part of making a
+# change to the live db schema should Always first be to make the change in the appropriate
+# OXM schema file so that future environments will have the change. This script is
+# just to change existing instances of the schema since schemaGenerator does not
+# update things - it just does the initial creation.
#
-# Boy, this is getting to be a big comment section...
-#
-# To use this script, you need to pass four parameters:
+# To use this script, there are 4 required parameters, and one optional:
# propertyName -- the name of the property that you need to change either the index or dataType on
# targetDataType -- whether it's changing or not, you need to give it: String, Integer, Boolean or Long
# targetIndexInfo -- whether it's changing or not, you need to give it: index, noIndex or uniqueIndex
@@ -24,7 +21,11 @@
# set this to false would be maybe if you were changing to an incompatible dataType so didn't
# want it to try to use the old data (and fail). But 99% of the time this will just be 'true'.
#
+# commitBlockSize -- OPTIONAL -- how many updates to commit at once.
+# Default will be used if no value is passed.
+#
# Ie. schemaMod flavor-id String index true
+# or, schemaMod flavor-id String noIndex true 50000
#
COMMON_ENV_PATH=$( cd "$(dirname "$0")" ; pwd -P )
@@ -32,14 +33,14 @@ COMMON_ENV_PATH=$( cd "$(dirname "$0")" ; pwd -P )
start_date;
check_user;
-if [ "$#" -ne 4 ]; then
+if [ "$#" -ne 4 ] && [ "$#" -ne 5 ]; then
echo "Illegal number of parameters"
- echo "usage: $0 propertyName targetDataType targetIndexInfo preserveDataFlag"
+ echo "usage: $0 propertyName targetDataType targetIndexInfo preserveDataFlag [blockSize]"
exit 1
fi
source_profile;
-execute_spring_jar org.onap.aai.dbgen.schemamod.SchemaMod ${PROJECT_HOME}/resources/schemaMod-logback.xml "$1" "$2" "$3" "$4"
+execute_spring_jar org.onap.aai.dbgen.schemamod.SchemaMod ${PROJECT_HOME}/resources/schemaMod-logback.xml "$@"
if [ "$?" -ne "0" ]; then
echo "Problem executing schemaMod "
end_date;