anchor.diff:            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].
  ++
  +You can pass additional JDBC parameters using the `spec.hive.config.url`. For more details, see the link:https://jdbc.postgresql.org/documentation/head/connect.html#connection-parameters[PostgreSQL JDBC driver documentation].
  
positive.code:           create: false
        config:
          db:
            url: "jdbc:mysql://mysql.example.com:3306/hive_metastore"
            driver: "com.mysql.jdbc.Driver"
            secretName: "REPLACEME" <1>
  ----
  <1> The name of the secret containing the base64-encrypted username and password database credentials.
  
  You can pass additional JDBC parameters using the `spec.hive.config.url`. For more details see the https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html[MySQL Connector/J documentation].
  
  Use the example configuration file below to use a PostgreSQL database for Hive:
  
  [source,yaml]
  ----
  spec:
  
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
  