Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Currently, the Data Prep Wrangler front-end makes a GET call with all the directives in the query arguments. This causes issues on some browsers as there are limits as to how much data can be pushed using this approach. This document describes the format that is used for sending a request to the back-end.

...

This section of the specification provides information about the workspace that directives are being applied in and the number of records (the results) that the request should return when the results are computed.

FieldMandat

oryMandatory?

Description

name

Yes

Name of the workspace that Data Prep Wrangler should operate on

resu ltsresults

Yes

Number of records that should be returned in response to execution of the directives

...

This section of the specification contains all of the directives that are to be applied on the data in the workspace, with an option to save the directives as a recipe with a name.

FieldManda

toryMandatory?

Description

direc tivesdirectives

Yes

List of directives to be applied on the data

save

No

If true, specifies that the directives should be saved. If so, then name should also be specified.

name

No

Name of the recipe. This option is valid only when save is set to true.

...

This section of the specification provides information about how the input data is to be sampled.

FieldMandat

oryMandatory?

Description

met hodmethod

Yes

Type of sampling to be applied while selecting input data. Currently only supports first.

see dseed

No

The random seed to be used when sampling data

lim itlimit

Yes

The number of input records to be read from the source when applying directives

...