[GitHub] [pulsar-helm-chart] michaeljmarshall commented on a change in pull request #150: added additionalCommand parameter

[GitBox]

michaeljmarshall commented on a change in pull request #150:
URL: https://github.com/apache/pulsar-helm-chart/pull/150#discussion_r697152552



##
File path: charts/pulsar/templates/bookkeeper-statefulset.yaml
##
@@ -162,6 +162,9 @@ spec:
 command: ["sh", "-c"]
 args:
 - >
+{{- if .Values.bookkeeper.additionalCommand }}
+  {{ .Values.bookkeeper.additionalCommand }}
+{{- end }}

Review comment:
   I tested this properly, and I can see that it works. Thanks for 
confirming things on your end, @acjohnson.




-- 
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] michaeljmarshall commented on pull request #150: added additionalCommand parameter

[GitBox]

michaeljmarshall commented on pull request #150:
URL: https://github.com/apache/pulsar-helm-chart/pull/150#issuecomment-906921598


   @acjohnson - are you only looking to supply the a custom trust store to the 
JVM? If so, it is possible to configure the JVM's keystore and truststore using 
the following jvm args: `-Djavax.net.ssl.keyStore` and 
`-Djavax.net.ssl.trustStore`, respectively. These can be added to the 
proxy/function worker/broker command via the `PULSAR_EXTRA_OPTS`environment 
variable. They need to be formatted as `.jks` files, and it is possible to put 
them in a secret then mount them into the pod as files for use by the JVM.


-- 
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-client-node] codelipenghui merged pull request #169: [Build] Add windows building configurations

[GitBox]

codelipenghui merged pull request #169:
URL: https://github.com/apache/pulsar-client-node/pull/169


   


-- 
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-client-node] nkurihar edited a comment on pull request #168: Branch 1.3

[GitBox]

nkurihar edited a comment on pull request #168:
URL: 
https://github.com/apache/pulsar-client-node/pull/168#issuecomment-906907615


   @Liapin 
   Finally we decide to backport the patches to branch-1.3 and release 1.3.1.
   Since we think for now it is better to support users using Node.js Client 
1.3.x with C++ Client 2.7.x as well as users using latest versions.
   
   We're still discussing our future backporting policy and later the 
conclusion will be appeared on README or wiki.
   
   Thank you again for your contribution!


-- 
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-client-node] nkurihar commented on pull request #168: Branch 1.3

[GitBox]

nkurihar commented on pull request #168:
URL: 
https://github.com/apache/pulsar-client-node/pull/168#issuecomment-906907615


   @Liapin 
   Finally we decide to backport the patches to 1.3 and release 1.3.1.
   Since we think for now it is better to support users using Node.js Client 
1.3.x with C++ Client 2.7.x as well as users using latest versions.
   
   We're still discussing our future backporting policy and later the 
conclusion will be appeared on README or wiki.
   
   Thank you again for your contribution!


-- 
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-manager] beyondyinjl2 opened a new issue #410: How to use the userId and password authentication of AuthenticationProviderBasic

[GitBox]

beyondyinjl2 opened a new issue #410:
URL: https://github.com/apache/pulsar-manager/issues/410


   The pulsar cluster opens the authentication method of 
AuthenticationProviderBasic, how to use pulsar-manager to pass the 
authentication


-- 
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-client-node] codelipenghui commented on pull request #169: [Build] Add windows building configurations

[GitBox]

codelipenghui commented on pull request #169:
URL: 
https://github.com/apache/pulsar-client-node/pull/169#issuecomment-906843727


   @ryansealy @Anonymitaet Could you please help review the PR again?


-- 
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-manager] tuteng commented on issue #409: Option to view Schema registered with topic

[GitBox]

tuteng commented on issue #409:
URL: https://github.com/apache/pulsar-manager/issues/409#issuecomment-906796673


   Welcome to contribute it, thanks


-- 
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] acjohnson commented on pull request #150: added additionalCommand parameter

[GitBox]

acjohnson commented on pull request #150:
URL: https://github.com/apache/pulsar-helm-chart/pull/150#issuecomment-906774294


   I've experimented with a couple alternatives including simply mounting an 
already updated copy of `/etc/ssl/certs/ca-certificates.crt` via a secret 
volume file but that didn't work...
   
   If non-root container is the future, I might be forced to build new docker 
images with every pulsar release unless someone comes up with a work around...
   


-- 
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: [Proposal] Creating an Apache Pulsar Outreach Working Group

[Dave Fisher]

Hi -

Even without an official group it should be possible to discuss improvements to 
outreach here on the dev@ mailing list.

There is a page full of logos (some missing) at 
https://pulsar.apache.org/powered-by/  
While that is a good starting place there is no information on that page about 
how to request addition to that page. I’m not clear that the PMC has a policy 
or rule.

> On Aug 24, 2021, at 5:30 PM, Aaron Williams  wrote:
> 
> Hello Apache Pulsar Community,
> 
> I would like to propose that the PMC create an Outreach Working Group.
> 
> Here’s why it is needed:
> 
> The Apache Pulsar community currently doesn't have community-driven content
> channels that are unaffiliated with any vendor. We also don't have an
> active effort to help identify people/organizations who are using Pulsar,
> nor do we have resources who are helping to tell their stories and educate
> the broader industry about these users and organizations where Pulsar is
> being used successfully.  In my experience, this is the single most
> important factor in helping a new infrastructure “cross the chasm” from
> early adopters who are willing to roll up their sleeves, do their own
> research and help find bugs, to “early majority” where people feel
> confident in adopting it because peer groups that they trust have already
> done that research and hardening.
> 
> In other words, there are many great things happening around the Apache
> Pulsar community, but there is no unified effort to push that information
> out.
> 
> For example, we could do a LOT more to publicize the Pulsar Summit Europe.
> Instead of a website going live a month before the event with no awareness,
> the working group would be responsible for having the webpage go live well
> in advance, for contacting the relevant press to set up interviews with
> Pulsar Summit speakers, for helping the PMC define a theme of the event,
> for setting up social media & targeted ad campaigns, and for engaging with
> content creators like podcast interviews.  Blogs and interviews would be
> completed in advance and set to roll out on a predetermined cadence.
> 
> During the event, social media posts will be ready to go and augmented with
> news made the day of the event.  Afterwards, there needs to be follow up
> blogs, pointing people to the content that they missed and how to get to
> it.  Then this same content can be placed in the newsletter and recycled in
> other posts later on.  This is a lot of work that doesn’t “just happen”; it
> takes a lot of volunteers to get everything done.  And right now it doesn’t
> look like it is getting done, or at least the community has no insight into
> the current status of the event.  Thus, community members who want to
> volunteer, don’t know how to start.
> 
> I hope this helps illustrate how an Outreach Working Group could help
> organize and promote the community.
> 
> I look forward to hearing from the community about this proposal.
> 
> Thank you,
> 
> Aaron Williams

All The Best,
Dave

Debezium Oracle Source Connector

[Andrey Yegorov]

Hello,

I added a Debezium Oracle Source Connector and would appreciate feedback.
The PR is https://github.com/apache/pulsar/pull/11520
All tests/integration tests pass.

Due to the licensing of the Oracle jdbc driver, the jdbc driver is not
included into the nar file and the users will have to download and package
it. Example:
https://github.com/apache/pulsar/blob/7b97af9f1b2dec354a189aaa5d551dc865214e56/tests/docker-images/latest-version-image/Dockerfile#L110-L122

I am open to ideas on making it more user-friendly while keeping it
compatible Apache-license.

-- 
Andrey Yegorov

Pulsar Summit Asia 2021 CFP Is Open!

[Dianjin Wang]

Hi, all Pulsar community members,

Pulsar Summit Asia 2021 CFP is open now! We’re glad to invite you to share
your experience and add up to the wonderfulness. **Pulsar Summit Asia 2021
will be hosted on November 20-21, 2021** by StreamNative hybridly both
online and offline.

As a speaker, you will receive the chance to demonstrate your experience
and deep knowledge, and your bio and session featured among the Apache
Pulsar community. We would also like you to help us make Pulsar Summit Asia
2021 a big success by spreading the word on Twitter, LinkedIn, and other
social media.

Please submit your talks[1] by September 8th, GMT+8. We welcome submissions
from around the globe. Also, first-time speakers are welcomed. For more
details, please check the CFP blog[2], and do not hesitate to contact us at
organiz...@pulsar-summit.org if you have any questions.

We look forward to your participation!

[1] Submission link: https://sessionize.com/pulsar-summit-asia-2021/
[2] CFP blog: https://pulsar.apache.org/blog/2021/08/18/asia-cfp/

Best,
Dianjin Wang

[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #143: ZooKeeper HTTP port should be exposed by service so we can use promet…

[GitBox]

frankjkelly commented on pull request #143:
URL: https://github.com/apache/pulsar-helm-chart/pull/143#issuecomment-906307680


   Thanks @sijie I forgot to ask if I needed to bump the chart version 
https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/Chart.yaml#L24
 as part of this change


-- 
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-manager] GPrabhudas opened a new issue #409: Option to view Schema registered with topic

[GitBox]

GPrabhudas opened a new issue #409:
URL: https://github.com/apache/pulsar-manager/issues/409


   - It is better to have option to view schema registered with topic on pulsar 
manager UI.
   
   If indeed it makes sense to have option to view schema, I'll  go ahead raise 
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: dev-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org