Advanced Cluster Options
Also available as:
PDF

Example 2: Other type

In this scenario, you start up with a special blueprint including JDBC property variables, and Cloudbreak replaces JDBC-related property variables in the blueprint.

  1. Prepare a blueprint blueprint that includes property variables. Use mustache template syntax. For example:
    ...
    "test-site": {
      "properties": {
       "javax.jdo.option.ConnectionURL":"{{{rds.test.connectionString}}}"
      }
    ...
  2. Register an existing external database of some “Other” type. For example:
    1. Property variable Example value
      rds.hive.connectionString jdbc:postgresql://ec2-54-159-202-231.compute-1.amazonaws.com:5432/hive
      rds.hive.connectionDriver org.postgresql.Driver
      rds.hive.connectionUserName myuser
      rds.hive.connectionPassword Hadoop123!
      rds.hive.subprotocol postgres
      rds.hive.databaseEngine POSTGRES
  3. Create a cluster by using your custom blueprint and by attaching the external database configuration.
  4. Upon cluster create, Cloudbreak replaces JDBC-related property variables in the blueprint.