Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version r0811

...

The following types of jobs can be executed in

D s product
rtrue
:

  • Convert jobs: Some datasources, such as binary file or JSON formats, must be converted to a format that can be easily read by the 
    D s webapp
    . During data ingestion, the datasource is converted to a natively supported file format and stored on backend storage. 
  • Transform job: This type of job executes the steps in your recipe against the dataset to generate results in the specified format. When you configure your job, any set of selected output formats causes a transform job to execute according to the job settings.
  • Profile job: This type of job builds a visual profile of the generated results. When you configure your job, select Profile Results to generate a profile job.

...

  • Gather a new sample. In some cases, jobs can fail when run at scale because the sample displayed in the Transformer page did not include problematic data. If you have modified the number of rows or columns in your dataset, you can generate a new sample, which might illuminate the problematic data. However, gathering a new sample may fail as well, which can indicate a broader problem. See Samples Panel.

...

Download Error Report

When a job fails, you can download an error report, which can be useful for diagnosing issues:

Tip

Tip: If you are filing a request with

D s support
, please be sure to include this error report. Additionally, please provide the information available in the About > Report issue dialog.


  1. Login to the 
    D s webapp
     as an admin or the user who created the job.
  2. Click the Jobs link in the left navigation bar. 
  3. In the Jobs page, click the identifier for the job that failed. 
  4. In the Overview tab, review the Failed Stages entry or entries. 
  5. To acquire the error report, click Download error report. Review and forward the report as needed.

For each job in the failing job group, the error report contains:

ItemDescription
jobGroupId

The internal job identifier within the workspace where the error occurred. This value matches the job ID that is displayed in the

D s webapp

workspaceId

The identifier of the workspace where the error occurred

Tip

Tip: The workspace-person combination of identifiers provides a unique ID for the account where the error occurred.

jobId

The ID for the specific job in the job group. These jobs can include sampling, profiling, transformation, writing results, ingesting data, and more.

Tip

Tip: Individual job identifiers can be helpful in identifying specific problem areas.

personId

The internal identifier of the user within the workspace
status

The status of the job, such as "Failed", "Completed", "Pending".

errorMessageIdThe ID of the error message that is shown in the UI.
errorTimestampTimestamp of the job failure. Not included if no error occurs for the job.
uiErrorMessageError message that is shown in the job UI. Not included if no error occurs for the job.

...

Contact Support

If you are unable to diagnose your job failure, please contact 

D s support

Info

NOTE: When you contact support about a job failure, please be sure to download and include the entire zip file, your recipe, and (if possible) your dataset.

Report an Issue

If you believe that your job has failed due to an issue with

D s product
, select Help menu > Report issue. Copy your session information to the clipboard and paste it into an email to
D s support
.

Info

NOTE:

D s product
productgdple
customers must contact Google Support.

Learn More

D s also
inCQLtrue
label(label = "project_management_tasks")