Archive
Archive
The features and capabilities described in this appendix are deprecated and may be removed in a future release of VoltDB. This information is provided for existing customers who wish to continue using application catalogs temporarily. However, we do recommend converting to use of interactive DDL at your earliest convenience (as described in Section C.5, “Converting Existing Catalogs for Use with Interactive DDL”).
In previous versions of VoltDB, the database schema and stored procedures had to be precompiled into an application catalog before starting the database. This catalog was then specified on the command line when issuing the voltdb create command.
Catalogs are no longer needed and you can enter schema DDL interactively using the sqlcmd utility. This makes both creating your database and updating much easier. However, use of an application catalog — although deprecated — is still supported in VoltDB V5 for backwards compatibility.
This appendix provides information for customers with existing catalogs who wish to continue using catalogs to start and run their databases. The topics covered in the appendix are:
When starting a VoltDB database, you must choose between using an application catalog or using interactive DDL. The
default is using interactive DDL. To use an application catalog, specify schema="catalog" in the <cluster> element of the
deployment file. For example:
V5.x Documentation<cluster hostcount=5
kfactor=2
schema="catalog"
/>Application catalogs and interactive DDL cannot be used together on the same running database. If you start a database using an application catalog, you cannot use interactive DDL to modify that catalog. You must use the voltadmin update command or the @UpdateApplicationCatalog system procedure. Similarly, if you start a database using interactive DDL, you must use interactive DDL to modify the schema. You cannot use voltadmin update or @UpdateApplicationCatalog to apply a compiled catalog.