SQLJ.REPLACE_JAR

The SQLJ.REPLACE_JAR system procedure replaces an installed JAR file in GemFire XD.

Syntax

SQLJ.REPLACE_JAR(IN JAR_FILE_PATH VARCHAR(32672), 
                 IN QUALIFIED_JAR_NAME VARCHAR(32672))
JAR_FILE_PATH
The path and physical name of the JAR file to use as a replacement. For example:
d:/todays_build/tours.jar
Note: The JAR file path must be available on the specific GemFire XD data store to which the client is connected. If the client connects directly to a known GemFire XD server, then only that server requires the JAR file to be available at the specified path when the procedure executes. However, if a client connects using a locator then they may be connected to any available server in the distributed system. In this case, the JAR file path should be available to all members of the GemFire XD cluster (for example, from a fileshare location such as z:\) to ensure that the procedure can execute.
QUALIFIED_JAR_NAME
The GemFire XD name of the JAR file, qualified by the schema name. (This should correspond to the name that you specified in the SQLJ.INSTALL_JAR command.) Two examples:
MYSCHEMA.Sample1
 -- a delimited identifier.
MYSCHEMA."Sample2"

Example

-- SQL statement
CALL sqlj.replace_jar('c:\myjarfiles\newtours.jar', 'APP.Sample1')

GemFire XD unloads the JAR classes that were associated with the "APP.Sample1" installation, then installs and loads the classes in c:\myjarfiles\newtours.jar.