Re: [ANNOUNCE] New Committer: Haiting Jiang

2022-01-21 Thread ZhangJian He 
Congratulations!

Thanks
ZhangJian He

Enrico Olivelli  于2022年1月21日周五 15:42写道：

> Congratulations!
>
>
> Enrico
>
> Il Ven 21 Gen 2022, 08:38 Aloys Zhang  ha scritto:
>
> > Congratulations!
> >
> > zhangao  于2022年1月21日周五 15:07写道：
> >
> > > Congratulations! 
> > >
> > >
> > > Best Regards,
> > > zhangao
> > > -- 原始邮件 --
> > > 发件人:
> > >   "dev"
> > > <
> > > zhai...@apache.org>;
> > > 发送时间: 2022年1月21日(星期五) 下午2:59
> > > 收件人: "Dev" > > us...@pulsar.apache.org>;
> > >
> > > 主题: [ANNOUNCE] New Committer: Haiting Jiang
> > >
> > >
> > >
> > > The Apache Pulsar Project Management Committee (PMC) has invited
> Haiting
> > > Jiang
> > > (https://github.com/jason918) to become a committer and we are pleased
> > to
> > >
> > > announce that he has accepted.
> > >
> > >
> > > Haiting contributed a lot of interesting additions to the project, and
> > > helped a lot to answer the user’s questions like in github issues,
> wechat
> > > groups and slack channels.  His full list of contributions in
> github
> > > can be
> > > found at https://github.com/apache/pulsar/commits?author=jason918.
> > >
> > >
> > > Welcome and Congratulations, Haiting! Please enjoy the journey as a
> > > committer :)
> > >
> > >
> > > Please join us in congratulating and welcoming Haiting onboard!
> > >
> > > Best Regards,
> > > Jia on behalf of the Pulsar PMC
> >
>

[GitHub] [pulsar-dotpulsar] blankensteiner commented on pull request #95: Add token factory support, respond to server auth challenge on token refresh

2022-01-21 Thread GitBox 


blankensteiner commented on pull request #95:
URL: https://github.com/apache/pulsar-dotpulsar/pull/95#issuecomment-1018321610


   Hi @goldenccargill 
   Thanks for the PR! :-) Could you make it pass the integration tests? Then I 
can merge it and create a new release :-)


-- 
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: [DISCUSSION] PIP-124: Create init subscription before sending message to DLQ

2022-01-21 Thread Zike Yang 
+1 for adding init_subscription filed to the metadata of CommandProducer.



On Thu, Jan 20, 2022 at 2:52 PM PengHui Li  wrote:
>
> > What is the justification for avoiding the new protobuf field? If we
> add a structured field to a map of , we are still
> modifying the protocol, even if we aren't modifying the protobuf.
>
> Not all cases need a new field named init_subscription when creating
> producer,
> and users will not touch the metadata of the producer of a DLQ, so I think
> we can use the metadata to achieve the purpose more flexibly.
>
> Yes, it modifies the protocol, but in different ways. It like the message
> properties,
> we also introduce some system message properties such as
> __original_message_id
> in retry letter topic.
>
> Penghui
>
> On Thu, Jan 20, 2022 at 2:05 PM Michael Marshall 
> wrote:
>
> > > I think that, good or bad, the impression that users have that the DLQ
> > > is not a "normal" topic
> >
> > Thanks for your perspective, Matteo. I still prefer my alternative
> > design that bypasses subscription creation, but it seems there
> > is insufficient interest in it, so we should move forward
> > discussing a DLQ specific feature and its implementation.
> >
> > > 1. Instead of modifying the current protocol, we can use producer
> > > metadata to carry the init subscription
> >
> > What is the justification for avoiding the new protobuf field? If we
> > add a structured field to a map of , we are still
> > modifying the protocol, even if we aren't modifying the protobuf.
> >
> > Thanks,
> > Michael
> >
> >
> > On Tue, Jan 18, 2022 at 8:38 AM PengHui Li  wrote:
> > >
> > > +1 for adding the DLQ_init_sub to producer metadata so that we don't
> > > need to introduce a new field in CommandProducer, and the new field
> > > looks a little confusing
> > >
> > > Thanks,
> > > Penghui
> > >
> > > On Mon, Jan 17, 2022 at 10:19 PM Hang Chen  wrote:
> > >
> > > > Thanks for creating this proposal Zike Yang. I have two ideas about it.
> > > > 1. Instead of modifying the current protocol, we can use producer
> > > > metadata to carry the init subscription
> > > > 2. Please add auth for subscription creation when create topic by
> > > > producer, otherwise, it will be easily attacked.
> > > >
> > > > Thanks,
> > > > Hang
> > > >
> > > > Matteo Merli  于2022年1月12日周三 15:13写道：
> > > > >
> > > > > > If we want to hold that the DLQ is not a normal topic, then I can
> > see
> > > > > > why we would have a DLQ specific feature here.
> > > > >
> > > > > I think that, good or bad, the impression that users have that the
> > DLQ
> > > > > is not a "normal" topic comes from 2 factors:
> > > > >  1. The experience with traditional messaging systems JMS and others
> > > > > where the DLQ are handled in slightly different ways, compared to
> > > > > other topics
> > > > >  2. The name "DLQ" which in a way it's implying a "queue"... which
> > can
> > > > > be implemented on topic, using a subscription..
> > > >
> >



--
Zike Yang

Re: [ANNOUNCE] New Committer: Haiting Jiang

2022-01-21 Thread Yu 
Congratulations! And thanks for contributing docs!

On Fri, Jan 21, 2022 at 4:36 PM ZhangJian He  wrote:

> Congratulations!
>
> Thanks
> ZhangJian He
>
> Enrico Olivelli  于2022年1月21日周五 15:42写道：
>
> > Congratulations!
> >
> >
> > Enrico
> >
> > Il Ven 21 Gen 2022, 08:38 Aloys Zhang  ha
> scritto:
> >
> > > Congratulations!
> > >
> > > zhangao  于2022年1月21日周五 15:07写道：
> > >
> > > > Congratulations! 
> > > >
> > > >
> > > > Best Regards,
> > > > zhangao
> > > > -- 原始邮件 --
> > > > 发件人:
> > > >   "dev"
> > > > <
> > > > zhai...@apache.org>;
> > > > 发送时间: 2022年1月21日(星期五) 下午2:59
> > > > 收件人: "Dev" > > > us...@pulsar.apache.org>;
> > > >
> > > > 主题: [ANNOUNCE] New Committer: Haiting Jiang
> > > >
> > > >
> > > >
> > > > The Apache Pulsar Project Management Committee (PMC) has invited
> > Haiting
> > > > Jiang
> > > > (https://github.com/jason918) to become a committer and we are
> pleased
> > > to
> > > >
> > > > announce that he has accepted.
> > > >
> > > >
> > > > Haiting contributed a lot of interesting additions to the project,
> and
> > > > helped a lot to answer the user’s questions like in github issues,
> > wechat
> > > > groups and slack channels.  His full list of contributions in
> > github
> > > > can be
> > > > found at https://github.com/apache/pulsar/commits?author=jason918.
> > > >
> > > >
> > > > Welcome and Congratulations, Haiting! Please enjoy the journey as a
> > > > committer :)
> > > >
> > > >
> > > > Please join us in congratulating and welcoming Haiting onboard!
> > > >
> > > > Best Regards,
> > > > Jia on behalf of the Pulsar PMC
> > >
> >
>

[GitHub] [pulsar-helm-chart] tuteng commented on a change in pull request #205: Tiered Storage config

2022-01-21 Thread GitBox 


tuteng commented on a change in pull request #205:
URL: https://github.com/apache/pulsar-helm-chart/pull/205#discussion_r789540140



##
File path: charts/pulsar/templates/broker-configmap.yaml
##
@@ -43,6 +43,62 @@ data:
   zooKeeperSessionTimeoutMillis: "3"
   statusFilePath: "{{ template "pulsar.home" . }}/status"
 
+  # Tiered storage settings
+  {{- if .Values.broker.storageOffload.driver }}
+  {{- if eq .Values.broker.storageOffload.driver "aws-s3" }}
+  managedLedgerOffloadDriver: "{{ .Values.broker.storageOffload.driver }}" 
+  s3ManagedLedgerOffloadBucket: "{{ .Values.broker.storageOffload.bucket }}" 
+  s3ManagedLedgerOffloadRegion: "{{ .Values.broker.storageOffload.region }}" 
+  AWS_ACCESS_KEY_ID: "{{ .Values.broker.storageOffload.accessKey }}" 
+  AWS_SECRET_ACCESS_KEY: "{{ .Values.broker.storageOffload.accessSecret }}"

Review comment:
   Consider putting it in k8s secret?




-- 
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] tuteng commented on a change in pull request #205: Tiered Storage config

2022-01-21 Thread GitBox 


tuteng commented on a change in pull request #205:
URL: https://github.com/apache/pulsar-helm-chart/pull/205#discussion_r789540423



##
File path: charts/pulsar/templates/broker-configmap.yaml
##
@@ -43,6 +43,62 @@ data:
   zooKeeperSessionTimeoutMillis: "3"
   statusFilePath: "{{ template "pulsar.home" . }}/status"
 
+  # Tiered storage settings
+  {{- if .Values.broker.storageOffload.driver }}
+  {{- if eq .Values.broker.storageOffload.driver "aws-s3" }}
+  managedLedgerOffloadDriver: "{{ .Values.broker.storageOffload.driver }}" 
+  s3ManagedLedgerOffloadBucket: "{{ .Values.broker.storageOffload.bucket }}" 
+  s3ManagedLedgerOffloadRegion: "{{ .Values.broker.storageOffload.region }}" 
+  AWS_ACCESS_KEY_ID: "{{ .Values.broker.storageOffload.accessKey }}" 
+  AWS_SECRET_ACCESS_KEY: "{{ .Values.broker.storageOffload.accessSecret }}"
+  {{- if 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}
+  PULSAR_PREFIX_managedLedgerOffloadThresholdInBytes: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}" 
+  {{- end }} 
+  {{- if .Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}
+  PULSAR_PREFIX_managedLedgerOffloadDeletionLagInMillis: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.maxBlockSizeInBytes }}
+  s3ManagedLedgerOffloadMaxBlockSizeInBytes: "{{ 
.Values.broker.storageOffload.maxBlockSizeInBytes }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.readBufferSizeInBytes }}
+  s3ManagedLedgerOffloadReadBufferSizeInBytes: "{{ 
.Values.broker.storageOffload.readBufferSizeInBytes }}" 
+  {{- end }}
+  {{- end }}
+  {{- if eq .Values.broker.storageOffload.driver "google-cloud-storage" }}
+  managedLedgerOffloadDriver: "{{ .Values.broker.storageOffload.driver }}" 
+  gcsManagedLedgerOffloadBucket: "{{ .Values.broker.storageOffload.bucket }}"
+  gcsManagedLedgerOffloadRegion: "{{ .Values.broker.storageOffload.region }}"
+  gcsManagedLedgerOffloadServiceAccountKeyFile: 
"/pulsar/gcp-service-account/{{ 
.Values.broker.storageOffload.gcsServiceAccountJsonFile }}"
+  {{- if 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}
+  PULSAR_PREFIX_managedLedgerOffloadThresholdInBytes: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}" 
+  {{- end }} 
+  {{- if .Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}
+  PULSAR_PREFIX_managedLedgerOffloadDeletionLagInMillis: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.maxBlockSizeInBytes }}
+  gcsManagedLedgerOffloadMaxBlockSizeInBytes: "{{ 
.Values.broker.storageOffload.maxBlockSizeInBytes }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.readBufferSizeInBytes }}
+  gcsManagedLedgerOffloadReadBufferSizeInBytes: "{{ 
.Values.broker.storageOffload.readBufferSizeInBytes }}" 
+  {{- end }}
+  {{- end }}
+  {{- if eq .Values.broker.storageOffload.driver "azureblob" }}
+  managedLedgerOffloadDriver: "{{ .Values.broker.storageOffload.driver }}" 
+  managedLedgerOffloadBucket: "{{ .Values.broker.storageOffload.bucket }}"
+  AZURE_STORAGE_ACCOUNT: "{{ .Values.broker.storageOffload.storageAccount }}"
+  AZURE_STORAGE_ACCESS_KEY: "{{ 
.Values.broker.storageOffload.storageAccountKey }}"

Review comment:
   Consider putting it in k8s secret?
   
   




-- 
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-dotpulsar] goldenccargill commented on pull request #95: Add token factory support, respond to server auth challenge on token refresh

2022-01-21 Thread GitBox 


goldenccargill commented on pull request #95:
URL: https://github.com/apache/pulsar-dotpulsar/pull/95#issuecomment-1018559184


   > Hi @goldenccargill Thanks for the PR! :-) Could you make it pass the 
integration tests? Then I can merge it and create a new release :-)
   
   Hi @blankensteiner thanks, we've been wanting something like this for a 
while and thought we'd try and see if a PR would be acceptable. 
   
   I added some more tests to coverage some failure scenarios, lets see if they 
pass.
   
   I'm pretty new to the codebase so if you see something that could be done 
better please let me know. 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

Architecture of function authorization for process mode

2022-01-21 Thread Devin Bost 
I discovered that all functions running in process mode inherit the same
role from the token specified in the functions_worker.yml file. So, that
means that all functions in process mode have the same authorization scope,
which must be broad enough to ensure that all functions have the required
permission to operate. Architecturally, this design limits the ability to
enable self-service/multi-tenant management of process-mode functions
because it means that functions in one tenant automatically have permission
to access topics in all other tenants.
Even if a custom PulsarAuthorizationProvider is used, there's no current
way to distinguish roles between functions in process mode because they all
share the same token. In the code path where authorization is checked (
https://github.com/apache/pulsar/blob/adcbe0f118ece0999b8603f37010194b44c241b4/pulsar-broker-common/src/main/java/org/apache/pulsar/broker/authorization/PulsarAuthorizationProvider.java#L90),
there's no way to see which function is originating the request.  The
original principal used for the authorization check (
https://github.com/apache/pulsar/blob/3e6fedf9b69758c13d92c6ff75a7bd779038543a/pulsar-broker/src/main/java/org/apache/pulsar/broker/rest/TopicsBase.java#L758)
is derived from the role (
https://github.com/apache/pulsar/blob/cba8800de1013d0e8ac81f43ecb040a55978c358/pulsar-proxy/src/main/java/org/apache/pulsar/proxy/server/AdminProxyHandler.java#L369),
so during the authorization check, it doesn't appear that there's any other
information about who is initiating the request that could be used. (It
appears that there's no way for us to securely know who the requester is
except via their token.)

This brings me to wondering what the vision is for functions in process
mode. Are they intended to only be managed by an operator with
administrative access to the cluster? If there's an interest in supporting
multi-tenant permission scoping for process mode functions, what's the
right way to do it?

Devin G. Bost

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on a change in pull request #205: Tiered Storage config

2022-01-21 Thread GitBox 


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



##
File path: charts/pulsar/templates/broker-configmap.yaml
##
@@ -43,6 +43,62 @@ data:
   zooKeeperSessionTimeoutMillis: "3"
   statusFilePath: "{{ template "pulsar.home" . }}/status"
 
+  # Tiered storage settings
+  {{- if .Values.broker.storageOffload.driver }}
+  {{- if eq .Values.broker.storageOffload.driver "aws-s3" }}
+  managedLedgerOffloadDriver: "{{ .Values.broker.storageOffload.driver }}" 
+  s3ManagedLedgerOffloadBucket: "{{ .Values.broker.storageOffload.bucket }}" 
+  s3ManagedLedgerOffloadRegion: "{{ .Values.broker.storageOffload.region }}" 
+  AWS_ACCESS_KEY_ID: "{{ .Values.broker.storageOffload.accessKey }}" 
+  AWS_SECRET_ACCESS_KEY: "{{ .Values.broker.storageOffload.accessSecret }}"
+  {{- if 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}
+  PULSAR_PREFIX_managedLedgerOffloadThresholdInBytes: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}" 
+  {{- end }} 
+  {{- if .Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}
+  PULSAR_PREFIX_managedLedgerOffloadDeletionLagInMillis: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.maxBlockSizeInBytes }}
+  s3ManagedLedgerOffloadMaxBlockSizeInBytes: "{{ 
.Values.broker.storageOffload.maxBlockSizeInBytes }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.readBufferSizeInBytes }}
+  s3ManagedLedgerOffloadReadBufferSizeInBytes: "{{ 
.Values.broker.storageOffload.readBufferSizeInBytes }}" 
+  {{- end }}
+  {{- end }}
+  {{- if eq .Values.broker.storageOffload.driver "google-cloud-storage" }}
+  managedLedgerOffloadDriver: "{{ .Values.broker.storageOffload.driver }}" 
+  gcsManagedLedgerOffloadBucket: "{{ .Values.broker.storageOffload.bucket }}"
+  gcsManagedLedgerOffloadRegion: "{{ .Values.broker.storageOffload.region }}"
+  gcsManagedLedgerOffloadServiceAccountKeyFile: 
"/pulsar/gcp-service-account/{{ 
.Values.broker.storageOffload.gcsServiceAccountJsonFile }}"
+  {{- if 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}
+  PULSAR_PREFIX_managedLedgerOffloadThresholdInBytes: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadAutoTriggerSizeThresholdBytes 
}}" 
+  {{- end }} 
+  {{- if .Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}
+  PULSAR_PREFIX_managedLedgerOffloadDeletionLagInMillis: "{{ 
.Values.broker.storageOffload.managedLedgerOffloadDeletionLagMs }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.maxBlockSizeInBytes }}
+  gcsManagedLedgerOffloadMaxBlockSizeInBytes: "{{ 
.Values.broker.storageOffload.maxBlockSizeInBytes }}" 
+  {{- end }}
+  {{- if .Values.broker.storageOffload.readBufferSizeInBytes }}
+  gcsManagedLedgerOffloadReadBufferSizeInBytes: "{{ 
.Values.broker.storageOffload.readBufferSizeInBytes }}" 
+  {{- end }}
+  {{- end }}
+  {{- if eq .Values.broker.storageOffload.driver "azureblob" }}
+  managedLedgerOffloadDriver: "{{ .Values.broker.storageOffload.driver }}" 
+  managedLedgerOffloadBucket: "{{ .Values.broker.storageOffload.bucket }}"
+  AZURE_STORAGE_ACCOUNT: "{{ .Values.broker.storageOffload.storageAccount }}"
+  AZURE_STORAGE_ACCESS_KEY: "{{ 
.Values.broker.storageOffload.storageAccountKey }}"

Review comment:
   +1 - all of these keys should be in secrets that are mounted into the 
broker pod. Great catch, @tuteng!




-- 
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: [DISCUSS] New repository for website - pulsar-site

2022-01-21 Thread Dave Fisher 
Hi Li Li,

Please see https://issues.apache.org/jira/browse/INFRA-22778 for further 
instructions.

All the best,
Dave

> On Jan 20, 2022, at 10:16 PM, Dave Fisher  wrote:
> 
> It’s a bit late in my evening.
> 
> You could access the-asf.slack.com #asfinfra and ask about saving/copying 
> these secrets from pulsar.git to pulsar-site.git.
> 
> All the best,
> Dave
> 
> Sent from my iPhone
> 
>> On Jan 20, 2022, at 9:14 PM, Leo  wrote:
>> 
>> Hi Dave,
>> 
>> We need add two secrets(PULSARBOT_TOKEN and 
>> PULSAR_CROWDIN_DOCUSAURUS_API_KEY) for pulsar-site repo, Here's the code link
>> 
>> https://github.com/apache/pulsar-site/blob/ffc2e424a7565584e58c1f5a10bb0b1253497f53/.github/workflows/ci-pulsar-website-next-build.yaml#L78-L79
>>  
>> 
>> 
>> 
>> Thanks,
>> Li Li
>> 
>> 
>>> On Jan 21, 2022, at 11:04 AM, Dave Fisher  wrote:
>>> 
>>> Hi Liu Yu,
>>> 
> On Jan 20, 2022, at 6:21 PM, Liu Yu  wrote:
 
 Hi Dave,
 
 Thanks for creating the pulsar-site repo [1]!
 
 We (urf...@apache.org) are working on PIP 87 [2] and want to build and 
 preview the Pulsar website with the new version of Docusarus. 
 
 As discussed before, our community has been considering bringing website 
 content out of the Pulsar repo. 
 
 So can we move all the content under the site2 folder to the pulsar-site 
 repo?
>>> 
>>> Yes!
>>> 
>>> We’ll need to create a new ‘main’ branch and ask Infra to make it the 
>>> default.
>>> 
>>> Also a new staging branch. From the PR it will be named ‘asf-site-next’
>>> 
>>> All the best,
>>> Dave
 
 Thanks!
 
 [1] https://github.com/apache/pulsar-site
 [2] 
 https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#heading=h.n6wibg4w77xk
 
> On 2021/11/17 23:57:58 Dave Fisher wrote:
> I’m going to work through 
> https://github.com/apache/pulsar/blob/master/site2/README.md
> 
> I’ll make sure that any changes related to the asf-site branch don’t have 
> issue with that.
> 
> We may want to be able to publish alternative web designs to a staging 
> sites.
> 
>>> On Nov 17, 2021, at 3:02 PM, Dave Fisher  wrote:
>> 
>> I’ve updated my fork of apache/pulsar
>> 
>> I’m not seeing how to run the workflow "CI - Pulsar Website build”. Any 
>> ideas?
>> 
>> If not then I’m going to need to test locally and it will take some time 
>> to ready it.
>> 
>> 
>>> On Nov 17, 2021, at 1:15 PM, Matteo Merli  
>>> wrote:
>>> 
>>> Yes, that should work.
>>> 
>>> After that we can go ahead and remove `asf-site` from the main repo,
>>> although we need to make it "unprotected" to be able to do so.
>> 
>> Yes once we have moved over to the new then we can ask Infra to take 
>> care of the branch protection along with deleting it.
>> 
>> When I create the new repository I will copy all of the asf-site branch 
>> which will take care of transferring the parts of the site not actively 
>> being built.
> 
> I have created the new repository and populated the asf-site branch: 
> https://github.com/apache/pulsar-site/tree/asf-site
> 
> It publishes to a staging url which you can see here: 
> https://pulsar.staged.apache.org
> 
> Once we are ready we alter: 
> https://github.com/apache/pulsar-site/blob/asf-site/.asf.yaml
> 
> Per: 
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> 
>> 
>> Regards,
>> Dave
>> 
>>> 
>>> 
>>> --
>>> Matteo Merli
>>> 
>>> 
>>> On Wed, Nov 17, 2021 at 12:46 PM Dave Fisher  wrote:
 
 If we change ORIGIN_REPO[1] to point to a new pulsar-site repos.
 Then with the correct .asf.yaml file changes we can remove the 
 asf-site branch.
 I see that the publish is run from this workflow [2]
 Let me think about a PR to make the move.
 
 Regards,
 Dave
 
 [1] 
 https://github.com/apache/pulsar/blob/7a34cebca25e6e584e8b758e6bd58c1c4fe8a58e/site2/tools/publish-website.sh#L25
 [2] 
 https://github.com/apache/pulsar/blob/master/.github/workflows/ci-pulsar-website-build.yaml
 
 
> On Nov 17, 2021, at 12:31 PM, Matteo Merli  
> wrote:
> 
> https://github.com/apache/pulsar/blob/master/site2/tools/publish-website.sh
> 
> 
> --
> Matteo Merli
> 
> 
> On Wed, Nov 17, 2021 at 12:29 PM Dave Fisher  wrote:
>> 
>> Show me where the code is that commits to the asf-site branch.
>> 
>>> On Nov 17, 2021, at 12:25 PM, Matteo Merli  
>>> wrote:
>>> 
>>> I ag

[VOTE] PIP-86: Pulsar Functions: Preload and release external resources

2022-01-21 Thread Neng Lu 
Hi All,

I would like to start a VOTE on the PIP 86. (If it's already been voted,
please let me know.)

The issue for PIP 86 is here:
https://github.com/apache/pulsar/wiki/PIP-86%3A-Pulsar-Functions%3A-Preload-and-release-external-resources
And the initial implementation is here:
https://github.com/apache/pulsar/pull/13205

Please VOTE within 48 hours.

Best Regards,
Neng Lu

Re: [VOTE] PIP-86: Pulsar Functions: Preload and release external resources

2022-01-21 Thread Jerry Peng 
+1

On Fri, Jan 21, 2022 at 12:07 PM Neng Lu  wrote:

> Hi All,
>
> I would like to start a VOTE on the PIP 86. (If it's already been voted,
> please let me know.)
>
> The issue for PIP 86 is here:
>
> https://github.com/apache/pulsar/wiki/PIP-86%3A-Pulsar-Functions%3A-Preload-and-release-external-resources
> And the initial implementation is here:
> https://github.com/apache/pulsar/pull/13205
>
> Please VOTE within 48 hours.
>
> Best Regards,
> Neng Lu
>

Re: [VOTE] PIP-86: Pulsar Functions: Preload and release external resources

2022-01-21 Thread Enrico Olivelli 
+1

Enrico

Il Ven 21 Gen 2022, 21:18 Jerry Peng  ha
scritto:

> +1
>
> On Fri, Jan 21, 2022 at 12:07 PM Neng Lu  wrote:
>
> > Hi All,
> >
> > I would like to start a VOTE on the PIP 86. (If it's already been voted,
> > please let me know.)
> >
> > The issue for PIP 86 is here:
> >
> >
> https://github.com/apache/pulsar/wiki/PIP-86%3A-Pulsar-Functions%3A-Preload-and-release-external-resources
> > And the initial implementation is here:
> > https://github.com/apache/pulsar/pull/13205
> >
> > Please VOTE within 48 hours.
> >
> > Best Regards,
> > Neng Lu
> >
>

Re: [VOTE] PIP-86: Pulsar Functions: Preload and release external resources

2022-01-21 Thread Niclas Hedhman 



+1, non-binding

On 2022-01-21 21:07, Neng Lu wrote:

Hi All,

I would like to start a VOTE on the PIP 86. (If it's already been 
voted,

please let me know.)

The issue for PIP 86 is here:
https://github.com/apache/pulsar/wiki/PIP-86%3A-Pulsar-Functions%3A-Preload-and-release-external-resources
And the initial implementation is here:
https://github.com/apache/pulsar/pull/13205

Please VOTE within 48 hours.

Best Regards,
Neng Lu

Re: [VOTE] PIP-86: Pulsar Functions: Preload and release external resources

2022-01-21 Thread 陳智弘 
+1

Niclas Hedhman  於 2022年1月22日 週六 05:27 寫道：

>
> +1, non-binding
>
> On 2022-01-21 21:07, Neng Lu wrote:
> > Hi All,
> >
> > I would like to start a VOTE on the PIP 86. (If it's already been
> > voted,
> > please let me know.)
> >
> > The issue for PIP 86 is here:
> >
> https://github.com/apache/pulsar/wiki/PIP-86%3A-Pulsar-Functions%3A-Preload-and-release-external-resources
> > And the initial implementation is here:
> > https://github.com/apache/pulsar/pull/13205
> >
> > Please VOTE within 48 hours.
> >
> > Best Regards,
> > Neng Lu
>

RE: [ANNOUNCE] New Committer: Haiting Jiang

2022-01-21 Thread Ruguo Yu 
Congratulations!

Thanks

Ruguo Yu

 

On 2022/01/21 06:59:08 Jia Zhai wrote:

> The Apache Pulsar Project Management Committee (PMC) has invited Haiting

> Jiang

> (https://github.com/jason918) to become a committer and we are pleased to

> 

> announce that he has accepted.

> 

> 

> Haiting contributed a lot of interesting additions to the project, and

> helped a lot to answer the user’s questions like in github issues, wechat

> groups and slack channels.  His full list of contributions in github can be

> found at https://github.com/apache/pulsar/commits?author=jason918.

> 

> 

> Welcome and Congratulations, Haiting! Please enjoy the journey as a

> committer :)

> 

> 

> Please join us in congratulating and welcoming Haiting onboard!

> 

> Best Regards,

> Jia on behalf of the Pulsar PMC

>