-
Notifications
You must be signed in to change notification settings - Fork 922
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #4661 from martinwolst/pulsar-faq
FAQ for using data sources tools with Pulsar as default
- Loading branch information
Showing
2 changed files
with
29 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: Using data source tools with Pulsar | ||
area: deployment | ||
box_type: tip | ||
layout: faq | ||
contributors: [martinwolst] | ||
--- | ||
|
||
Data source tools such as UCSC Main will fail if Pulsar is the default destination. | ||
|
||
To fix this issue you can force individual tools to run on a specific destination or handler by adding to your job_conf file: | ||
|
||
For job_conf.xml | ||
```xml | ||
<tools> | ||
<tool id="ucsc_table_direct1" destination="my-local" /> | ||
</tools> | ||
``` | ||
For job_conf.yml | ||
```yml | ||
tools: | ||
- id: ucsc_table_direct1 | ||
handler: my-local | ||
``` |