Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ for using data sources tools with Pulsar as default #4661

Merged
merged 4 commits into from
Jan 19, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CONTRIBUTORS.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1239,6 +1239,11 @@ mwolfien:
name: Markus Wolfien
joined: 2017-09

martinwolst:
name: Martin Wolstencroft
joined: 2024-01
orcid: 0000-0002-6080-1710
elixir_node: uk
smza:
name: Munazah Andrabi
joined: 2023-09
Expand Down
24 changes: 24 additions & 0 deletions topics/admin/faqs/data-source-with-pulsar.md
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
```
Loading