Skip to main content Skip to complementary content

Editing Route and data service tasks

Before you begin

If your task is running and you chose either the single node or parallel deployment strategies, you must undeploy the task, edit it, and then deploy it again.

Procedure

  1. Go to the task details page of the Route or Data service you want to edit.
  2. Click Edit in the top-right corner of the page.
  3. In the Artifact step, you can update the following information:
    • The artifact used in the task.
    • The artifact version used in the task.
  4. In the Parameters step, enter the value for the parameters of the data service.
    In this step, when the Show order as in Studio toggle is disabled, you can only set the values to parameters you have defined with the parameter_ prefix in Talend Studio.
    Information noteNote: Use \\ instead of \ when the value could be interpreted as a special character, for example, \t.
  5. Optional: If you have defined parameters without a prefix in the Route/data service in Talend Studio, you can change the values of the parameters in the Advanced parameters step. This section is available when the Show order as in Studio toggle is disabled. Otherwise, all parameters are in the Parameters step.

    Parameters with connection_ prefix whose values have not been defined in the data service/Route itself can also be changed in this section.

    Information noteNote: Use \\ instead of \ when the value could be interpreted as a special character, for example, \t.
  6. If you use connection in your data service/Route, you can change it in the Connection section.
  7. If you use an external resource in your data service/Route, you can update or change it in the Resources section.
  8. In the Processing step, you can change the Remote Engine or cluster on which you want to deploy the task, as well as the run profile, metric path, port selection, deployment strategy and impersonated user option.
  9. Save your changes.

In this section

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here