[−][src]Struct rusoto_machinelearning::RDSDataSpec
The data specification of an Amazon Relational Database Service (Amazon RDS) DataSource.
Fields
data_rearrangement: Option<String>A JSON string that represents the splitting and rearrangement processing to be applied to a DataSource. If the DataRearrangement parameter is not provided, all of the input data is used to create the Datasource.
There are multiple parameters that control what data is used to create a datasource:
percentBeginUse
percentBeginto indicate the beginning of the range of the data used to create the Datasource. If you do not includepercentBeginandpercentEnd, Amazon ML includes all of the data when creating the datasource.percentEndUse
percentEndto indicate the end of the range of the data used to create the Datasource. If you do not includepercentBeginandpercentEnd, Amazon ML includes all of the data when creating the datasource.complementThe
complementparameter instructs Amazon ML to use the data that is not included in the range ofpercentBegintopercentEndto create a datasource. Thecomplementparameter is useful if you need to create complementary datasources for training and evaluation. To create a complementary datasource, use the same values forpercentBeginandpercentEnd, along with thecomplementparameter.For example, the following two datasources do not share any data, and can be used to train and evaluate a model. The first datasource has 25 percent of the data, and the second one has 75 percent of the data.
Datasource for evaluation:
{"splitting":{"percentBegin":0, "percentEnd":25}}Datasource for training:
{"splitting":{"percentBegin":0, "percentEnd":25, "complement":"true"}}strategyTo change how Amazon ML splits the data for a datasource, use the
strategyparameter.The default value for the
strategyparameter issequential, meaning that Amazon ML takes all of the data records between thepercentBeginandpercentEndparameters for the datasource, in the order that the records appear in the input data.The following two
DataRearrangementlines are examples of sequentially ordered training and evaluation datasources:Datasource for evaluation:
{"splitting":{"percentBegin":70, "percentEnd":100, "strategy":"sequential"}}Datasource for training:
{"splitting":{"percentBegin":70, "percentEnd":100, "strategy":"sequential", "complement":"true"}}To randomly split the input data into the proportions indicated by the percentBegin and percentEnd parameters, set the
strategyparameter torandomand provide a string that is used as the seed value for the random data splitting (for example, you can use the S3 path to your data as the random seed string). If you choose the random split strategy, Amazon ML assigns each row of data a pseudo-random number between 0 and 100, and then selects the rows that have an assigned number betweenpercentBeginandpercentEnd. Pseudo-random numbers are assigned using both the input seed string value and the byte offset as a seed, so changing the data results in a different split. Any existing ordering is preserved. The random splitting strategy ensures that variables in the training and evaluation data are distributed similarly. It is useful in the cases where the input data may have an implicit sort order, which would otherwise result in training and evaluation datasources containing non-similar data records.The following two
DataRearrangementlines are examples of non-sequentially ordered training and evaluation datasources:Datasource for evaluation:
{"splitting":{"percentBegin":70, "percentEnd":100, "strategy":"random", "randomSeed"="s3://mys3path/bucket/file.csv"}}Datasource for training:
{"splitting":{"percentBegin":70, "percentEnd":100, "strategy":"random", "randomSeed"="s3://mys3path/bucket/file.csv", "complement":"true"}}
data_schema: Option<String>A JSON string that represents the schema for an Amazon RDS DataSource. The DataSchema defines the structure of the observation data in the data file(s) referenced in the DataSource.
A DataSchema is not required if you specify a DataSchemaUri
Define your DataSchema as a series of key-value pairs. attributes and excludedVariableNames have an array of key-value pairs for their value. Use the following format to define your DataSchema.
{ "version": "1.0",
"recordAnnotationFieldName": "F1",
"recordWeightFieldName": "F2",
"targetFieldName": "F3",
"dataFormat": "CSV",
"dataFileContainsHeader": true,
"attributes": [
{ "fieldName": "F1", "fieldType": "TEXT" }, { "fieldName": "F2", "fieldType": "NUMERIC" }, { "fieldName": "F3", "fieldType": "CATEGORICAL" }, { "fieldName": "F4", "fieldType": "NUMERIC" }, { "fieldName": "F5", "fieldType": "CATEGORICAL" }, { "fieldName": "F6", "fieldType": "TEXT" }, { "fieldName": "F7", "fieldType": "WEIGHTEDINTSEQUENCE" }, { "fieldName": "F8", "fieldType": "WEIGHTEDSTRINGSEQUENCE" } ],
"excludedVariableNames": [ "F6" ] }
<?oxyinsertend>data_schema_uri: Option<String>The Amazon S3 location of the DataSchema.
database_credentials: RDSDatabaseCredentialsThe AWS Identity and Access Management (IAM) credentials that are used connect to the Amazon RDS database.
database_information: RDSDatabaseDescribes the DatabaseName and InstanceIdentifier of an Amazon RDS database.
resource_role: StringThe role (DataPipelineDefaultResourceRole) assumed by an Amazon Elastic Compute Cloud (Amazon EC2) instance to carry out the copy operation from Amazon RDS to an Amazon S3 task. For more information, see Role templates for data pipelines.
s3_staging_location: StringThe Amazon S3 location for staging Amazon RDS data. The data retrieved from Amazon RDS using SelectSqlQuery is stored in this location.
security_group_ids: Vec<String>The security group IDs to be used to access a VPC-based RDS DB instance. Ensure that there are appropriate ingress rules set up to allow access to the RDS DB instance. This attribute is used by Data Pipeline to carry out the copy operation from Amazon RDS to an Amazon S3 task.
select_sql_query: StringThe query that is used to retrieve the observation data for the DataSource.
service_role: StringThe role (DataPipelineDefaultRole) assumed by AWS Data Pipeline service to monitor the progress of the copy task from Amazon RDS to Amazon S3. For more information, see Role templates for data pipelines.
subnet_id: StringThe subnet ID to be used to access a VPC-based RDS DB instance. This attribute is used by Data Pipeline to carry out the copy task from Amazon RDS to Amazon S3.
Trait Implementations
impl PartialEq<RDSDataSpec> for RDSDataSpec[src]
fn eq(&self, other: &RDSDataSpec) -> bool[src]
fn ne(&self, other: &RDSDataSpec) -> bool[src]
impl Default for RDSDataSpec[src]
fn default() -> RDSDataSpec[src]
impl Clone for RDSDataSpec[src]
fn clone(&self) -> RDSDataSpec[src]
fn clone_from(&mut self, source: &Self)1.0.0[src]
Performs copy-assignment from source. Read more
impl Debug for RDSDataSpec[src]
impl Serialize for RDSDataSpec[src]
Auto Trait Implementations
impl Send for RDSDataSpec
impl Sync for RDSDataSpec
Blanket Implementations
impl<T> From for T[src]
impl<T, U> Into for T where
U: From<T>, [src]
U: From<T>,
impl<T> ToOwned for T where
T: Clone, [src]
T: Clone,
impl<T, U> TryFrom for T where
T: From<U>, [src]
T: From<U>,
type Error = !
try_from)The type returned in the event of a conversion error.
fn try_from(value: U) -> Result<T, <T as TryFrom<U>>::Error>[src]
impl<T> Borrow for T where
T: ?Sized, [src]
T: ?Sized,
impl<T> BorrowMut for T where
T: ?Sized, [src]
T: ?Sized,
fn borrow_mut(&mut self) -> &mut T[src]
impl<T, U> TryInto for T where
U: TryFrom<T>, [src]
U: TryFrom<T>,
type Error = <U as TryFrom<T>>::Error
try_from)The type returned in the event of a conversion error.
fn try_into(self) -> Result<U, <U as TryFrom<T>>::Error>[src]
impl<T> Any for T where
T: 'static + ?Sized, [src]
T: 'static + ?Sized,
fn get_type_id(&self) -> TypeId[src]
impl<T> Erased for T
impl<T> Same for T
type Output = T
Should always be Self