You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "guankai (via GitHub)" <gi...@apache.org> on 2023/11/06 09:27:35 UTC
[I] [Bug] Calling Sources in pulsar's java client prompts that Built-in source is not available [pulsar]
guankai opened a new issue, #21522:
URL: https://github.com/apache/pulsar/issues/21522
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
windows 10
pulsar 3.0.0
### Minimal reproduce step
I am currently using apache/pulsar version 3.0 and need to use the sources function. I see the corresponding calling path in the api is /admin/v3/sources/ but in the java sdk org.apache.pulsar.client In the SourcesImpl of .admin.internal, I see that the built path is admin/v3/source. Is this a problem with the SDK? Or am I calling the wrong method?
### What did you expect to see?
It is expected that the interface /admin/v3/sources/{tenant}/{namespace}/{sourceName} can be used
### What did you see instead?
Built-in source is not available
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Calling Sources in pulsar's java client prompts that Built-in source is not available [pulsar]
Posted by "merlimat (via GitHub)" <gi...@apache.org>.
merlimat closed issue #21522: [Bug] Calling Sources in pulsar's java client prompts that Built-in source is not available
URL: https://github.com/apache/pulsar/issues/21522
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug] Calling Sources in pulsar's java client prompts that Built-in source is not available [pulsar]
Posted by "merlimat (via GitHub)" <gi...@apache.org>.
merlimat commented on issue #21522:
URL: https://github.com/apache/pulsar/issues/21522#issuecomment-6381712687
Thanks @guankai for the report. The path isn't the problem: the broker and function worker serve both the deprecated `/admin/v3/source` and `/admin/v3/sources` endpoints from the same implementation, so the Java admin client reaches the right code. The error "Built-in source is not available" means the source's archive is `builtin://<name>` but that connector isn't installed in the function worker's `connectorsDirectory`, so the worker can't find it (see `SourcesImpl` in pulsar-functions/worker). The `apachepulsar/pulsar` image doesn't include connectors; on current releases you add the connector NAR to the connectors directory (or build an image with the connectors you need, see https://github.com/apache/pulsar-connectors), or pass the NAR file/URL as the archive instead of `builtin://`. I'm closing this. If it still happens on a currently supported release (4.0.x, 4.2.x or 5.0.x) with the connector installed, please reopen with the source config and the output of `pulsar-admin s
ources available-sources`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org