Upgrading Obsidian - Revision history

Craig: /* Existing Configuration with QuickStart */

2024-12-27T22:05:38Z

Existing Configuration with QuickStart

← Older revision		Revision as of 22:05, 27 December 2024
Line 20:		Line 20:

	==== Existing Configuration with QuickStart ====		==== Existing Configuration with QuickStart ====
	If you are using [[Advanced_Configuration#~~Properties_File~~\|overrides]] support to specify '''ALL''' your configuration items, you likely are ready to go as the default configuration items are being overridden.		If you are using [[Advanced_Configuration#Properties.2FYaml_File\|overrides]] support to specify '''ALL''' your configuration items, you likely are ready to go as the default configuration items are being overridden.

	Otherwise, you are relying at least partially on embedded configuration items. You will need to replace the quickstart configuration values with your existing configuration values. The Obsidian WAR files have the <code>com.carfey.properties</code> file inside at <code>WEB-INF/classes/com.carfey.properties</code> and the standalone installation has it at the root of ''obsidian-~~props~~.jar''.		Otherwise, you are relying at least partially on embedded configuration items. You will need to replace the quickstart configuration values with your existing configuration values. The Obsidian WAR files have the <code>com.carfey.(properties/yaml)</code> file inside at <code>WEB-INF/classes/com.carfey.(properties/yaml)</code> and the standalone installation has it at the root of ''obsidian-properties-configuration.jar'' or ''obsidian-yaml-configuration.jar''.

	== Performing the Upgrade ==		== Performing the Upgrade ==

Craig: /* Database Upgrade Scripts */

2023-02-24T13:29:20Z

Database Upgrade Scripts

← Older revision		Revision as of 13:29, 24 February 2023
Line 39:		Line 39:

	Then, in your SQL client of choice, execute the scripts in order of their version numbers. This will upgrade your schema to your target version.		Then, in your SQL client of choice, execute the scripts in order of their version numbers. This will upgrade your schema to your target version.

			You'll need to allow the data portion of the migrations to execute while preventing the DDL scripts to run. To do this, you need to [[Getting_Started#Disabling_DDL_Updates\|disable DDL Updates]].

	== Performing an Always On Cluster Upgrade ==		== Performing an Always On Cluster Upgrade ==

Carfey: /* Database Upgrade Scripts */

2015-01-23T23:20:14Z

Database Upgrade Scripts

← Older revision		Revision as of 23:20, 23 January 2015
Line 38:		Line 38:
	First locate all files named "*upgrade.sql" under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.		First locate all files named "*upgrade.sql" under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

	Then, in your SQL client of choice, execute the scripts in order of their version numbers. This ~~should~~ upgrade your schema to your target version.		Then, in your SQL client of choice, execute the scripts in order of their version numbers. This will upgrade your schema to your target version.

	== Performing an Always On Cluster Upgrade ==		== Performing an Always On Cluster Upgrade ==

Carfey: /* Database Upgrade Scripts */

2015-01-23T23:19:47Z

Database Upgrade Scripts

← Older revision		Revision as of 23:19, 23 January 2015
Line 36:		Line 36:
	When you start Obsidian, it will automatically upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create and drop privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download zip file under the "db_scripts" directory.		When you start Obsidian, it will automatically upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create and drop privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download zip file under the "db_scripts" directory.

	First locate all files named "*upgrade.sql" ~~located~~ under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.		First locate all files named "*upgrade.sql" under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

	Then, in your SQL client of choice, execute the scripts in order of their version numbers. This should upgrade your schema to your target version.		Then, in your SQL client of choice, execute the scripts in order of their version numbers. This should upgrade your schema to your target version.

Carfey: /* Database Upgrade Scripts */

2015-01-23T23:19:12Z

Database Upgrade Scripts

← Older revision		Revision as of 23:19, 23 January 2015
Line 34:		Line 34:
	''Available as of version 3.0''		''Available as of version 3.0''

	When you start Obsidian, it will automatically upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create and drop privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download ~~package~~ under the "db_scripts" directory.		When you start Obsidian, it will automatically upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create and drop privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download zip file under the "db_scripts" directory.

	First locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.		First locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

Carfey: /* Database Upgrade Scripts */

2015-01-23T23:18:56Z

Database Upgrade Scripts

← Older revision		Revision as of 23:18, 23 January 2015
Line 34:		Line 34:
	''Available as of version 3.0''		''Available as of version 3.0''

	When you start Obsidian, it will automatically upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.		When you start Obsidian, it will automatically upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create and drop privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.

	First locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.		First locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

Carfey: /* Database Upgrade Scripts */

2015-01-23T23:18:41Z

Database Upgrade Scripts

← Older revision		Revision as of 23:18, 23 January 2015
Line 34:		Line 34:
	''Available as of version 3.0''		''Available as of version 3.0''

	When you start Obsidian, it will automatically ~~detect and~~ upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.		When you start Obsidian, it will automatically upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.

	First locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.		First locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

Carfey: /* Database Upgrade Scripts */

2015-01-23T23:16:33Z

Database Upgrade Scripts

← Older revision		Revision as of 23:16, 23 January 2015
Line 36:		Line 36:
	When you start Obsidian, it will automatically detect and upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.		When you start Obsidian, it will automatically detect and upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.

			First locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.
	First ~~create your database, and~~ locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

	Then, in your SQL client of choice, execute the scripts in order of their version numbers. This should upgrade your schema to your target version.		Then, in your SQL client of choice, execute the scripts in order of their version numbers. This should upgrade your schema to your target version.

Carfey: /* Database Upgrade Scripts */

2015-01-23T23:16:12Z

Database Upgrade Scripts

← Older revision		Revision as of 23:16, 23 January 2015
Line 35:		Line 35:

	When you start Obsidian, it will automatically detect and upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.		When you start Obsidian, it will automatically detect and upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.


	First create your database, and locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.		First create your database, and locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

	Then, in your SQL client of choice, execute the scripts in order of their version numbers. This should upgrade your schema to your target version.		Then, in your SQL client of choice, execute the scripts in order of their version numbers. This should upgrade your schema to your target version.


	== Performing an Always On Cluster Upgrade ==		== Performing an Always On Cluster Upgrade ==

Carfey at 23:15, 23 January 2015

2015-01-23T23:15:16Z

← Older revision		Revision as of 23:15, 23 January 2015
Line 30:		Line 30:

	The simplest mechanism is to bring down all your Obsidian Scheduler nodes during a quiet scheduling period. Deploy the new artifacts and start the each node individually verifying its startup before proceeding to the next node.		The simplest mechanism is to bring down all your Obsidian Scheduler nodes during a quiet scheduling period. Deploy the new artifacts and start the each node individually verifying its startup before proceeding to the next node.

			== Database Upgrade Scripts ==
			''Available as of version 3.0''

			When you start Obsidian, it will automatically detect and upgrade the schema in your target database. However, if you wish to run Obsidian with a database user without create privileges, or simply wish to prepare your database structure ahead of time, you can use the database upgrade scripts provided with your download package under the "db_scripts" directory.
			First create your database, and locate all files named "*upgrade.sql" located under the directory for the database you are using under the "db_scripts" directory. Statements within these files contain the token "$px$" to enable table prefixes. Before you run the SQL files, replace all instances of the token "$px$" (without quotes) with a table prefix 6 characters or shorter (letters and underscores supported), or with blank.

			Then, in your SQL client of choice, execute the scripts in order of their version numbers. This should upgrade your schema to your target version.


	== Performing an Always On Cluster Upgrade ==		== Performing an Always On Cluster Upgrade ==