create table new_emr_clusters (
  name text not null,
  release_label text references emr_release_labels not null default 'emr-5.10.0',
  applications ,
  s3_log_uri text not null,
  master_instance ,
  core_instance ,
  task_instance ,
  ec2_subnet text,
  emr_service_role ,
  emr_job_flow_role ,
  visible_to_all_users boolean not null default false,
  configurations ,
  security_configuration text
);
comment on table new_emr_clusters is '
  New EMR cluster configuration object
';

comment on column new_emr_clusters.ec2_subnet is '
  To be set in case the EMR cannot be launched in the `default VPC`
';
comment on column new_emr_clusters.emr_service_role is '
  role to be assigned to the service, the default one should cover most of the cases
';
comment on column new_emr_clusters.emr_job_flow_role is '
  role to be assigned to the ec2 instances composing the EMR cluster. The default one should cover most of the cases
';
comment on column new_emr_clusters.visible_to_all_users is '
  whether or not to show the new cluster in the list of clusters. For more details see [emr docs](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-emr-cluster.html#cfn-emr-cluster-visibletoallusers)
';
comment on column new_emr_clusters.configurations is '
  Extra configuration to be applied to cluster, see https://docs.aws.amazon.com/emr/latest/APIReference/API_Configuration.html
';
comment on column new_emr_clusters.security_configuration is '
  Allow you to specify a security configuration for the cluster
';