anchor.diff:    password: <BASE64_ENCODED_DATABASE_PASSWORD> <3>
   ----
   <1> The name of the secret.
  -<2> Base64 encoded database username.
  +<2> Base64 encoded database user name.
   <3> Base64 encoded database password.
   
  -Use the example configuration file below to use a MySQL database for Hive:
  -
  +. Create a configuration file to use a MySQL or PostgreSQL database for Hive:
  ++
  +* To use a MySQL database for Hive, use the example configuration file below. Metering supports configuring the internal Hive metastore to use the MySQL server versions 5.6, 5.7, and 8.0.
  ++
  +--
   [source,yaml]
   ----
   spec:
  
positive.code:           username: "REPLACEME"
            password: "REPLACEME"
  ----
  You can pass additional JDBC parameters using the URL. For more details see the https://jdbc.postgresql.org/documentation/head/connect.html#connection-parameters[PostgreSQL JDBC driver documentation].
  
negative.code: 
  The default installation of metering configures Hive to use an embedded Java database called Derby. This is unsuited for larger environments and can be replaced with either a MySQL or PostgreSQL database. Use the following example configuration files if your deployment requires a MySQL or PostgreSQL database for Hive.
  
  There are three configuration options you can use to control the database that is used by Hive metastore: `url`, `driver`, and `secretName`.
  
  Create your MySQL or Postgres instance with a user name and password. Then create a secret by using the OpenShift CLI (`oc`) or a YAML file. The `secretName` you create for this secret must map to the `spec.hive.spec.config.db.secretName` field in the `MeteringConfig` object resource.
  
  .Procedure
  
  . Create a secret using the OpenShift CLI (`oc`) or by using a YAML file:
  +
  * Create a secret by using the following command:
  +
  [source,terminal]
  ----
  $ oc --namespace openshift-metering create secret generic <YOUR_SECRETNAME> --from-literal=username=<YOUR_DATABASE_USERNAME> --from-literal=password=<YOUR_DATABASE_PASSWORD>
  ----
  +
  * Create a secret by using a YAML file. For example:
  +
  [source,yaml]
  ----
  apiVersion: v1
  