[GitHub] [pulsar-manager] aileen5150 commented on issue #383: Failed to get failureDomains list
aileen5150 commented on issue #383: URL: https://github.com/apache/pulsar-manager/issues/383#issuecomment-871892775 ./bin/pulsar-admin clusters get standalone 执行返回 null Reason: java.util.concurrent.CompletionException: org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector$RetryException: Could not complete the operation. Number of retries has been exhausted. Failed reason: Remotely closed -- 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: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] tech4gk commented on issue #91: Helm chart doesn't work with older Pulsar versions
tech4gk commented on issue #91: URL: https://github.com/apache/pulsar-helm-chart/issues/91#issuecomment-871836164 Hi @yabinmeng I am also bumping into the same issue. Can you share what was wrong with the customized values.yaml file ? Thanks a lot... -- 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: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] ckdarby opened a new pull request #137: Bump containers to sync with Streamnative & Pulsar version to 2.8.0
ckdarby opened a new pull request #137: URL: https://github.com/apache/pulsar-helm-chart/pull/137 ### Motivation 2.8.0 has been released for two weeks and it is probably time to bump the versions here. ### Modifications Bump versions of containers for Pulsar v2.8. Also bump the grafana dashboards to be in sync with the streamnative ones and there is a newer tag of pulsar manager. ### Verifying this change - [ ] Make sure that the change passes the CI checks. -- 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: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PIP] Expose Pulsar-Client via Function/Connector BaseContext
Hi Neng, Thank you for starting the discussion! I have assigned PIP-85 to your PIP. https://github.com/apache/pulsar/wiki/PIP-85:-Expose-Pulsar-Client-via-Function-Connector-BaseContext The proposal looks good to me. +1 - Sijie On Wed, Jun 30, 2021 at 12:40 PM Neng Lu wrote: > > Hi All, > > I've prepared a brief PIP for the pulsarclient changes we have discussed. > Please take a look and let me know what you think. > > I would really appreciate it. > > Best Regards, > Neng Lu
Re: [PIP] Expose Pulsar-Client via Function/Connector BaseContext
Thank you Neng Can you please put it inside a google document in order to allow people to add comments? Regards Enrico Il Mer 30 Giu 2021, 21:40 Neng Lu ha scritto: > Hi All, > > I've prepared a brief PIP for the pulsarclient changes we have discussed. > Please take a look and let me know what you think. > > I would really appreciate it. > > Best Regards, > Neng Lu >
Re: [VOTE] Apache Pulsar Adapters Release 2.8.0 Candidate 1
Please take a look We are still missing at least 2 PMC votes Any feedback from the community is really appreciated Enrico Il Mar 29 Giu 2021, 12:46 Enrico Olivelli ha scritto: > Penghui, > I created an issue for the problem you reported > https://github.com/apache/pulsar-adapters/issues/25 > > thank you very much for testing the RC > > Enrico > > Il giorno mar 29 giu 2021 alle ore 12:35 PengHui Li > ha scritto: > >> +1 for me. >> >> we can fix the directory name in the next release, >> it's not a big problem for the first release. >> >> Thanks, >> Penghui >> >> PengHui Li 于2021年6月29日周二 下午6:27写道： >> >> > Hi Enrico, >> > sorry for the late reply >> > >> > 1. Checked the signature >> > 2. Build via the source code >> > 3. Passed all the tests locally >> > >> > The only one I found is when I unzip the package, it shows me an >> > apache-pulsar-2.8.0-src directory, >> > Looks a little wired, I think it should be >> > apache-pulsar-adaptors-2.8.0-src? >> > >> > Thanks, >> > Penghui >> > >> > Enrico Olivelli 于2021年6月29日周二 下午1:55写道： >> > >> >> Hi everyone, >> >> please take a look. >> >> If you want to build the source package locally you have to follow the >> >> steps in the README >> >> https://github.com/apache/pulsar-adapters >> >> >> >> Enrico >> >> >> >> Il giorno sab 26 giu 2021 alle ore 13:51 Enrico Olivelli < >> >> eolive...@gmail.com> ha scritto: >> >> >> >> > This is the first release candidate for Apache Pulsar Adapters, >> version >> >> > 2.8.0. >> >> > >> >> > It fixes the following issues: >> >> > https://github.com/apache/pulsar-adapters/milestone/2?closed=1 >> >> > >> >> > *** Please download, test and vote on this release. This vote will >> stay >> >> > open >> >> > for at least 72 hours *** >> >> > >> >> > Note that we are voting upon the source (tag), binaries are provided >> for >> >> > convenience and are released only to Maven Central. >> >> > >> >> > Source and binary files: >> >> > >> >> > >> >> >> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-adapters-2.8.0-candidate-1/ >> >> > >> >> > SHA-512 checksums: >> >> > >> >> > >> >> >> 6f1f34fc454fdaa9b5065d0dce96d468d8b5081cff333564cb88dca7e9c9aba828bb7469bb8c3aa4d23fe653d1a03285418d9ba36d5617a39a783e0433d01dba >> >> > apache-pulsar-adapters-2.8.0-src.tar.gz >> >> > >> >> > Maven staging repo: >> >> > >> >> >> https://repository.apache.org/content/repositories/orgapachepulsar-1091/ >> >> > >> >> > The tag to be voted upon: >> >> > v2.8.0-candidate-1 (581fee3b68caaf74122e7051e9741494b57fcbd7) >> >> > >> >> >> https://github.com/apache/pulsar-adapters/releases/tag/v2.8.0-candidate-1 >> >> > >> >> > Pulsar's KEYS file containing PGP keys we use to sign the release: >> >> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS >> >> > >> >> > Please download the source package, and follow the README to build >> the >> >> > Pulsar Adapters code >> >> > >> >> > Enrico Olivelli >> >> > >> >> >> > >> >
[PIP] Expose Pulsar-Client via Function/Connector BaseContext
Hi All,
I've prepared a brief PIP for the pulsarclient changes we have discussed.
Please take a look and let me know what you think.
I would really appreciate it.
Best Regards,
Neng Lu
# PIP: Expose Pulsar-Client via Function/Connector BaseContext
- Status: Proposal
- Authors: Neng Lu
- Pull Request: https://github.com/apache/pulsar/pull/11056Mailing
- List discussion:
- Release:
## Motivation
Providing Functions/Connectors the ability to securely and easily access the underlying Pulsar Cluster is very useful in many scenarios. It enables functions/connectors to utilize Pulsar Cluster as an backend store in addition to normally data processing path.
Currently, in order to access the pulsar cluster, users have to create the pulsar client on their own and provide all the auth parameters. This way is complicated, insecure and unnecessary.
Instead, we should have a standard way to allow user access the pulsar client easily and securely.
## API and Implementation Changes
As we have refactored the organization of function's context object hierachy, it currently looks as the right side of following graph:
[](https://user-images.githubusercontent.com/16407807/118730483-8ebf5200-b7ec-11eb-9220-d41261f148bb.png)
To allow Function, Source Connector and Sink Connector all have the ability to access the pulsar cluster, we need to introduce a new api in the `BaseContext` object:
```java
/**
* Get the pulsar client.
*
* @return the instance of pulsar client
*/
default PulsarClient getPulsarClient() {
throw new UnsupportedOperationException("not implemented");
}
```
And for the implementation, the `ContextImpl` object should return the `PulsarClient` it's using for various purposes:
```java
@Override
public PulsarClient getPulsarClient() {
return client;
}
```
Notice, this return `PulsarClient` connects to the underlying pulsar cluster already and has auth parameters inherited from function/source/sink submitter. So it should be properly scoped and will only be able to perform operations that it's authorized to do.
To utilize the client in function/source/sink code is fairly straightforward.
```java
public String func(String input, Context context) {
PulsarClient client = context.getPulsarClient();
return ...;
}
```
Re: [Doc] Label Your PR
very good. I appreciate very much your efforts in improving the docs and checking on every PR if the change needs updates to the docs Enrico Il giorno mer 30 giu 2021 alle ore 14:43 Anonymitaet _ < anonymita...@hotmail.com> ha scritto: > Hi all, > > > > Recently, our community is on the way to the next milestone and has merged > plenty of codes, some engineers proactively add the docs with the code, > that is **GREAT**, thank you all! > > > > To **improve the productivity and effectiveness of developing contents**, > I've added the label `no-need-doc`. > > Now we have the following doc-related labels in total: > >- `component/documentation`: if a PR updates doc or an issue is >related to doc, you can use this label. >- `doc-required`: if a PR / issue needs to update doc, you can use >this label. After finishing the doc, remove this label from the original PR >/ issue. >- `no-need-doc`: if a PR does not need to update doc, please help >label it. It saves the efforts for others to check and ask whether your PR >needs to update doc, which allows engineers and technical writers to work >more efficiently. > > > > If you have any comments or questions about the Pulsar docs, we would love > to hear from you, thanks. > > > > Anonymitaet > > >
[Doc] Label Your PR
Hi all, Recently, our community is on the way to the next milestone and has merged plenty of codes, some engineers proactively add the docs with the code, that is *GREAT*, thank you all! To *improve the productivity and effectiveness of developing contents*, I've added the label `no-need-doc`. Now we have the following doc-related labels in total: * `component/documentation`: if a PR updates doc or an issue is related to doc, you can use this label. * `doc-required`: if a PR / issue needs to update doc, you can use this label. After finishing the doc, remove this label from the original PR / issue. * `no-need-doc`: if a PR does not need to update doc, please help label it. It saves the efforts for others to check and ask whether your PR needs to update doc, which allows engineers and technical writers to work more efficiently. If you have any comments or questions about the Pulsar docs, we would love to hear from you, thanks. Anonymitaet
