date:20220512

[DISCUSS] PIP-166: Function add NONE delivery semantics

2022-05-12 Thread Baozi

Hi Pulsar community,

I open a https://github.com/apache/pulsar/issues/15560 for Function add NONE 
delivery semantics

Let me know what you think.


Thanks,
Baodi Shi


## Motivation

Currently Function supports three delivery semantics, and also provides autoAck 
to control whether to automatically ack.
Because autoAck affects the delivery semantics of Function, it can be confusing 
for users to understand the relationship between these two parameters.

For example, when the user configures `Guarantees == ATMOST_ONCE` and `autoAck 
== false`, then the framework will not help the user to ack messages, and the 
processing semantics may become `ATLEAST_ONCE`.

The delivery semantics provided by Function should be clear. When the user sets 
the guarantees, the framework should ensure point-to-point semantic processing 
and cannot be affected by other parameters.

## Goal

Added `NONE` delivery semantics and delete `autoAck` config.

The original intention of `autoAck` semantics is that users want to control the 
timing of ack by themselves. When autoAck == false, the processing semantics 
provided by the framework should be invalid. Then we can add `NONE` processing 
semantics to replace the autoAck == false scenario.

When the user configuration `ProcessingGuarantees == NONE`, the framework does 
not help the user to do any ack operations, and the ack is left to the user to 
handle. In other cases, the framework guarantees processing semantics.

## API Changes
1. Add `NONE` type to ProcessingGuarantees
``` java
public enum ProcessingGuarantees {
  ATLEAST_ONCE,
  ATMOST_ONCE,
  EFFECTIVELY_ONCE,
  NONE
}
```

2. Delete autoAck config in FunctionConfig
``` java
public class FunctionConfig {
-private Boolean autoAck;
}
```

## Implementation

1. In `PulsarSinkAtLeastOnceProcessor` and 
`PulsarSinkEffectivelyOnceProcessor`, when `ProcessingGuarantees != NONE` can 
be ack.



2. When the delivery semantic is `ATMOST_ONCE`, the message will be acked 
immediately after receiving the message, no longer affected by the autoAck 
configuration.

https://github.com/apache/pulsar/blob/c49a977de4b0b525ec80e5070bc90eddcc7cddad/pulsar-functions/instance/src/main/java/org/apache/pulsar/functions/instance/JavaInstanceRunnable.java#L271-L276

3. When user call `record.ack()` in function, just  `ProcessingGuarantees == 
NONE` can be work.

## Plan test
The main test and assert is that when ProcessingGuarantees == NONE, the 
function framework will not do any ack operations for the user.

## Compatibility
1. This change will invalidate the user's setting of autoAck, which should be 
explained in the documentation and provide parameter verification to remind the 
user.
2. Runtimes of other languages need to maintain consistent processing logic 
(python, go).

Re: [DISCUSS] PIP-158: Split client TLS transport encryption from authentication

2022-05-12 Thread Zixuan Liu

Hi Michael,

Thanks for your feedback!

>  I notice that the PIP doesn't
mention documentation. Since we're adding another way to configure
mTLS, please make sure to document the recommended way that users
should take advantage of this feature and how this feature relates to the
existing AuthenticationTLS feature.

Good idea, let me add a simple document that how to use TLS transport and
TLS authentication.

> We are removing the client's need to use the AuthenticationTLS class
to perform TLS authentication of clients by the server.

We don't remove the use of the AuthenticationTLS.

> If a user wants to use TLS certificates for authorization, they can still
put
roles in their client certificates and continue to use the
AuthenticationProviderTLS class to map a TLS certificate to a role on
the server side.

You are right, the users still can use the AuthenticationTLS to perform the
TLS transport and TLS authentication.

Currently, the AuthenticationTLS includes TLS transport and TLS
authentication, if the user only uses the TLS transport, not use the TLS
authentication, it is confusing, so I want to add a TLS transport config in
`ClientBuilder`.

Thanks,
Zixuan


Michael Marshall  于2022年5月12日周四 01:51写道：

> I agree that the current state of this feature is a bit confusing, and
> I think the proposed changes make sense. I notice that the PIP doesn't
> mention documentation. Since we're adding another way to configure
> mTLS, please make sure to document the recommended way that users
> should take advantage of this feature and how this feature relates to the
> existing AuthenticationTLS feature.
>
> In order to make sure I understand the feature correctly, can you
> confirm that the following is correct?
>
> We are removing the client's need to use the AuthenticationTLS class
> to perform TLS authentication of clients by the server. If a user
> wants to use TLS certificates for authorization, they can still put
> roles in their client certificates and continue to use the
> AuthenticationProviderTLS class to map a TLS certificate to a role on
> the server side.
>
> Thanks,
> Michael
>
>
>
>
>
>
> On Mon, May 9, 2022 at 12:58 AM Yunze Xu 
> wrote:
> >
> > Thanks for your clarification. Let’s continue maintaining these configs
> in
> > `ClientBuilder`.
> >
> > Thanks,
> > Yunze
> >
> >
> >
> >
> > > 2022年5月9日 13:54，Zixuan Liu  写道：
> > >
> > > Hi Yunze,
> > >
> > > Thanks for your suggestion, your idea is great, but we have the
> > > `tlsProtocols()` and `tlsCiphers()` in `ClientBuilder`, so I use this
> style.
> > >
> > > Thanks,
> > > Zixuan
> > >
> > > Yunze Xu  于2022年5月9日周一 13:31写道：
> > >
> > >> It totally LGTM. I have a suggestion that it might be better to
> configure a
> > >> class like `TlsConfiguration` instead of multiple TLS related configs
> > >> added to
> > >> `ClientBuilder`.
> > >>
> > >> Thanks,
> > >> Yunze
> > >>
> > >>
> > >>
> > >>
> > >>> 2022年4月24日 14:15，Zixuan Liu  写道：
> > >>>
> > >>> Hi Pulsar community,
> > >>>
> > >>> I open a https://github.com/apache/pulsar/issues/15289 for Split
> client
> > >> TLS
> > >>> transport encryption from authentication.
> > >>>
> > >>> Let me know what you think.
> > >>>
> > >>> Thanks,
> > >>> Zixuan
> > >>>
> > >>> --
> > >>>
> > >>> Motivation
> > >>>
> > >>> The client supports TLS transport encryption and TLS authentication,
> this
> > >>> code so like:
> > >>>
> > >>> PulsarClient client = PulsarClient.builder()
> > >>>   .serviceUrl("pulsar+ssl://localhost:6651")
> > >>>   .tlsTrustCertsFilePath("/path/to/cacert.pem")
> > >>>   .authentication(AuthenticationTls.class.getName(),
> > >> authParams)
> > >>>   .build()
> > >>>
> > >>> This causes an issue that cannot use other authentication with TLS
> > >>> transport encryption, and also made our confusion if we use TLS
> transport
> > >>> encryption by setting authentication.
> > >>> Goal
> > >>>
> > >>> Split client TLS transport encryption from authentication is used to
> > >>> support TLS transport encryption with any authentication.
> > >>> API Changes
> > >>>
> > >>>  - Add new methods in org.apache.pulsar.client.api.ClientBuilder
> > >>>
> > >>> public interface ClientBuilder extends Serializable, Cloneable {
> > >>>   /** * Set the path to the TLS key file. * * @param
> > >>> tlsKeyFilePath * @return the client builder instance */
> > >>>   ClientBuilder tlsKeyFilePath(String tlsKeyFilePath);
> > >>>
> > >>>   /** * Set the path to the TLS certificate file. * *
> > >>> @param tlsCertificateFilePath * @return the client builder
> > >>> instance */
> > >>>   ClientBuilder tlsCertificateFilePath(String
> tlsCertificateFilePath);
> > >>> }
> > >>>
> > >>> ImplementationTLS transport encryption
> > >>>
> > >>> We can call the tlsKeyFilePath(), tlsCertificateFilePath() and
> > >>> tlsTrustCertsFilePath() to configurate the TLS transport encryption,
> the
> > >>> code so like:
> > >>>
> > >>> PulsarClient clien

Re: [DISCUSS] PIP-158: Split client TLS transport encryption from authentication

2022-05-12 Thread Zixuan Liu

You can see the code in the implementation part, this will be consistent
with the actual document.

Zixuan Liu  于2022年5月12日周四 17:03写道：

> Hi Michael,
>
> Thanks for your feedback!
>
> >  I notice that the PIP doesn't
> mention documentation. Since we're adding another way to configure
> mTLS, please make sure to document the recommended way that users
> should take advantage of this feature and how this feature relates to the
> existing AuthenticationTLS feature.
>
> Good idea, let me add a simple document that how to use TLS transport and
> TLS authentication.
>
> > We are removing the client's need to use the AuthenticationTLS class
> to perform TLS authentication of clients by the server.
>
> We don't remove the use of the AuthenticationTLS.
>
> > If a user wants to use TLS certificates for authorization, they can
> still put
> roles in their client certificates and continue to use the
> AuthenticationProviderTLS class to map a TLS certificate to a role on
> the server side.
>
> You are right, the users still can use the AuthenticationTLS to perform
> the TLS transport and TLS authentication.
>
> Currently, the AuthenticationTLS includes TLS transport and TLS
> authentication, if the user only uses the TLS transport, not use the TLS
> authentication, it is confusing, so I want to add a TLS transport config in
> `ClientBuilder`.
>
> Thanks,
> Zixuan
>
>
> Michael Marshall  于2022年5月12日周四 01:51写道：
>
>> I agree that the current state of this feature is a bit confusing, and
>> I think the proposed changes make sense. I notice that the PIP doesn't
>> mention documentation. Since we're adding another way to configure
>> mTLS, please make sure to document the recommended way that users
>> should take advantage of this feature and how this feature relates to the
>> existing AuthenticationTLS feature.
>>
>> In order to make sure I understand the feature correctly, can you
>> confirm that the following is correct?
>>
>> We are removing the client's need to use the AuthenticationTLS class
>> to perform TLS authentication of clients by the server. If a user
>> wants to use TLS certificates for authorization, they can still put
>> roles in their client certificates and continue to use the
>> AuthenticationProviderTLS class to map a TLS certificate to a role on
>> the server side.
>>
>> Thanks,
>> Michael
>>
>>
>>
>>
>>
>>
>> On Mon, May 9, 2022 at 12:58 AM Yunze Xu 
>> wrote:
>> >
>> > Thanks for your clarification. Let’s continue maintaining these configs
>> in
>> > `ClientBuilder`.
>> >
>> > Thanks,
>> > Yunze
>> >
>> >
>> >
>> >
>> > > 2022年5月9日 13:54，Zixuan Liu  写道：
>> > >
>> > > Hi Yunze,
>> > >
>> > > Thanks for your suggestion, your idea is great, but we have the
>> > > `tlsProtocols()` and `tlsCiphers()` in `ClientBuilder`, so I use this
>> style.
>> > >
>> > > Thanks,
>> > > Zixuan
>> > >
>> > > Yunze Xu  于2022年5月9日周一 13:31写道：
>> > >
>> > >> It totally LGTM. I have a suggestion that it might be better to
>> configure a
>> > >> class like `TlsConfiguration` instead of multiple TLS related configs
>> > >> added to
>> > >> `ClientBuilder`.
>> > >>
>> > >> Thanks,
>> > >> Yunze
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>> 2022年4月24日 14:15，Zixuan Liu  写道：
>> > >>>
>> > >>> Hi Pulsar community,
>> > >>>
>> > >>> I open a https://github.com/apache/pulsar/issues/15289 for Split
>> client
>> > >> TLS
>> > >>> transport encryption from authentication.
>> > >>>
>> > >>> Let me know what you think.
>> > >>>
>> > >>> Thanks,
>> > >>> Zixuan
>> > >>>
>> > >>> --
>> > >>>
>> > >>> Motivation
>> > >>>
>> > >>> The client supports TLS transport encryption and TLS
>> authentication, this
>> > >>> code so like:
>> > >>>
>> > >>> PulsarClient client = PulsarClient.builder()
>> > >>>   .serviceUrl("pulsar+ssl://localhost:6651")
>> > >>>   .tlsTrustCertsFilePath("/path/to/cacert.pem")
>> > >>>   .authentication(AuthenticationTls.class.getName(),
>> > >> authParams)
>> > >>>   .build()
>> > >>>
>> > >>> This causes an issue that cannot use other authentication with TLS
>> > >>> transport encryption, and also made our confusion if we use TLS
>> transport
>> > >>> encryption by setting authentication.
>> > >>> Goal
>> > >>>
>> > >>> Split client TLS transport encryption from authentication is used to
>> > >>> support TLS transport encryption with any authentication.
>> > >>> API Changes
>> > >>>
>> > >>>  - Add new methods in org.apache.pulsar.client.api.ClientBuilder
>> > >>>
>> > >>> public interface ClientBuilder extends Serializable, Cloneable {
>> > >>>   /** * Set the path to the TLS key file. * * @param
>> > >>> tlsKeyFilePath * @return the client builder instance */
>> > >>>   ClientBuilder tlsKeyFilePath(String tlsKeyFilePath);
>> > >>>
>> > >>>   /** * Set the path to the TLS certificate file. * *
>> > >>> @param tlsCertificateFilePath * @return the client builder
>> > >>> instance */
>> > >>>   ClientBuilder tlsCertificateFilePath(Stri

RE: [VOTE] PIP-156: Enable system topic by default

2022-05-12 Thread Dezhi Liu



+1  Regards, Dezhi

Re: [VOTE] Pulsar Manager Release 0.3.0 Candidate 3

2022-05-12 Thread Guangning E

+1(non-binding)
Validate checksum
Start pulsar-manager service
Create tenant and topic

Thanks,
Guangning

Li Li  于2022年5月10日周二 14:14写道：

> Hi everyone,
> Please review and vote on the release candidate #3 for the version 0.3.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
> * Release notes [1]
> * The official Apache source and binary distributions to be deployed to
> dist.apache.org  [2]
> * Source code tag "v0.3.0-candidate-3" [4] with git sha
> 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4
> apache-pulsar-manager-0.3.0-src.tar.gz
>
> PulsarManager's KEYS file contains PGP keys we used to sign this release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
>
> Please download these packages and review this release candidate:
>
> - Review release notes
> - Download the source package (verify shasum, and asc) and follow the
> instructions to build and run the pulsar-manager front end and back end
> service.
> - Download the binary package (verify shasum, and asc) and follow the
> instructions to run run the pulsar-manager front end and back end service.
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
>
> Source and binary files:
>
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz
> >
>
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz
> <
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz
> >
>
> SHA-512 checksums:
>
> 6ffa5921765ee94a404792e98eb4b3cbda9e016c6661ef12e4e873e7e452301bc05650709955b012d08048e418133948a628ad55bc91ac65836022e1ea426d6f
> apache-pulsar-manager-0.3.0-bin.tar.gz
> 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4
> apache-pulsar-manager-0.3.0-src.tar.gz
>
>
>
>

Re: New Pulsar Website is Live!

2022-05-12 Thread Guangning E

Cool, thanks Yu and Lili

Thanks,
Guangning

Dianjin Wang  于2022年5月12日周四 10:53写道：

> It looks much more modern! Thanks to all the contributors for making the
> new website live!
>
> Best,
> Dianjin Wang
>
>
> On Thu, May 12, 2022 at 10:46 AM Max Xu 
> wrote:
>
> > This new website looks awesome, love it!
> >
> > Thank you!
> > Max Xu
> >
> >
> >
> > On Thu, May 12, 2022 at 1:24 AM Aaron Williams  wrote:
> >
> > > Looks great! Thank you
> > >
> > >
> > > On Wed, May 11, 2022 at 10:19 AM Chris Latimer  >
> > > wrote:
> > >
> > > > It looks really good, thank you to everyone who worked on this!
> > > >
> > > > On Wed, May 11, 2022 at 1:31 AM Liu Yu  wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > As you may notice, the new Pulsar website goes live! [1]
> > > > >
> > > > > We hope you enjoy the new content and the fresh appearance!
> > > > >
> > > > > Do not hesitate to leave your comment here [2] if you have any
> > > > suggestions
> > > > > or concerns, thanks!
> > > > >
> > > > > [1] https://pulsar.apache.org/
> > > > > [2] https://github.com/apache/pulsar/issues/15538
> > > > >
> > > > > Yu and Lili
> > > > >
> > > > > On 2022/05/10 02:43:12 Yu wrote:
> > > > > > Hi everyone,
> > > > > >
> > > > > > The New Pulsar Website (beta) has been running for more than 3
> > > months.
> > > > > > We've optimized the website based on the feedback from the New
> > Pulsar
> > > > > > Website Survey [1].
> > > > > >
> > > > > > Now everything goes fine except few known issues:
> > > > > > - Search function may not work very well
> > > > > > - Some pages are not completely translated
> > > > > >
> > > > > > However, they do not block the switchover, and we're continually
> > > > > improving
> > > > > > them all the time.
> > > > > >
> > > > > > Consequently, we plan to launch the New Pulsar Website on May 11,
> > > > > Wednesday
> > > > > > (UTC+8).
> > > > > >
> > > > > > Feel free to comment if you have any suggestions or concerns on
> the
> > > > > > switchover, thanks!
> > > > > >
> > > > > > [1]
> > https://lists.apache.org/thread/xjccxbozlw7jqlldm2dw0yc74cydknvd
> > > > > >
> > > > > > Yu and Lili
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] [PIP-153] Optimize metadataPositions in MLPendingAckStore

2022-05-12 Thread mattison chao

+1 (non-binding)

Best,
Mattison

On Thu, 12 May 2022 at 12:15, Ran Gao  wrote:

> +1 (non-binding)
>
> Best,
> Ran
>
> On 2022/04/25 06:54:58 一苇以航 wrote:
> > Hi Pulsar Community.
> >
> > This is the voting thread for PIP-153. It will stay open for at least 48
> hours.
> >
> > The proposal can be found:https://github.com/apache/pulsar/issues/15073
> >
> > Discuss thread:
> > https://lists.apache.org/thread/svmbp8ybn6l8o0o8dmvsysnb86qj77r3
> >
> > Thanks,
> > Xiangying
> >
> >  
>

Re: New Pulsar Website is Live!

2022-05-12 Thread Yu

This new website could not be available without the help of Lili
(@urfreespace). I truly appreciate your GREAT contribution!!

And I'm indebted to the wonderfully wise communities of smart people who
talked, argued, and shared with us. Thank you!

On Thu, May 12, 2022 at 10:53 AM Dianjin Wang
 wrote:

> It looks much more modern! Thanks to all the contributors for making the
> new website live!
>
> Best,
> Dianjin Wang
>
>
> On Thu, May 12, 2022 at 10:46 AM Max Xu 
> wrote:
>
> > This new website looks awesome, love it!
> >
> > Thank you!
> > Max Xu
> >
> >
> >
> > On Thu, May 12, 2022 at 1:24 AM Aaron Williams  wrote:
> >
> > > Looks great! Thank you
> > >
> > >
> > > On Wed, May 11, 2022 at 10:19 AM Chris Latimer  >
> > > wrote:
> > >
> > > > It looks really good, thank you to everyone who worked on this!
> > > >
> > > > On Wed, May 11, 2022 at 1:31 AM Liu Yu  wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > As you may notice, the new Pulsar website goes live! [1]
> > > > >
> > > > > We hope you enjoy the new content and the fresh appearance!
> > > > >
> > > > > Do not hesitate to leave your comment here [2] if you have any
> > > > suggestions
> > > > > or concerns, thanks!
> > > > >
> > > > > [1] https://pulsar.apache.org/
> > > > > [2] https://github.com/apache/pulsar/issues/15538
> > > > >
> > > > > Yu and Lili
> > > > >
> > > > > On 2022/05/10 02:43:12 Yu wrote:
> > > > > > Hi everyone,
> > > > > >
> > > > > > The New Pulsar Website (beta) has been running for more than 3
> > > months.
> > > > > > We've optimized the website based on the feedback from the New
> > Pulsar
> > > > > > Website Survey [1].
> > > > > >
> > > > > > Now everything goes fine except few known issues:
> > > > > > - Search function may not work very well
> > > > > > - Some pages are not completely translated
> > > > > >
> > > > > > However, they do not block the switchover, and we're continually
> > > > > improving
> > > > > > them all the time.
> > > > > >
> > > > > > Consequently, we plan to launch the New Pulsar Website on May 11,
> > > > > Wednesday
> > > > > > (UTC+8).
> > > > > >
> > > > > > Feel free to comment if you have any suggestions or concerns on
> the
> > > > > > switchover, thanks!
> > > > > >
> > > > > > [1]
> > https://lists.apache.org/thread/xjccxbozlw7jqlldm2dw0yc74cydknvd
> > > > > >
> > > > > > Yu and Lili
> > > > > >
> > > > >
> > > >
> > >
> >
>

[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #75: Add line number in code blocks

2022-05-12 Thread GitBox



SignorMercurio opened a new pull request, #75:
URL: https://github.com/apache/pulsar-site/pull/75

   Implemented task 1 in apache/pulsar#15550. Screenshot:
   
   
![image](https://user-images.githubusercontent.com/32540679/168137971-879dc744-b7df-4ecd-bda2-266e7dc87751.png)
   


-- 
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

[jira] [Created] (PULSAR-20) Exception for "Topic not exist" should name the topic and server

2022-05-12 Thread Jason Kania (Jira)

Jason Kania created PULSAR-20:
-

 Summary: Exception for "Topic not exist" should name the topic and 
server
 Key: PULSAR-20
 URL: https://issues.apache.org/jira/browse/PULSAR-20
 Project: Pulsar
  Issue Type: Improvement
Reporter: Jason Kania


I am getting the following exception while using Flink with Pulsar where I 
believe the topic does not exist but I cannot determine which topic it is 
because the job is complicated. I get the following error:
org.apache.pulsar.client.admin.PulsarAdminException$NotFoundException: Topic 
not exist
    at 
org.apache.pulsar.client.admin.internal.BaseResource.getApiException(BaseResource.java:230)
    at 
org.apache.pulsar.client.admin.internal.TopicsImpl$7.failed(TopicsImpl.java:529)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.client.JerseyInvocation$1.failed(JerseyInvocation.java:882)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.client.JerseyInvocation$1.completed(JerseyInvocation.java:863)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:229)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime.access$200(ClientRuntime.java:62)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime$2.lambda$response$0(ClientRuntime.java:173)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors.process(Errors.java:292)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors.process(Errors.java:274)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.internal.Errors.process(Errors.java:244)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:288)
    at 
org.apache.pulsar.shade.org.glassfish.jersey.client.ClientRuntime$2.response(ClientRuntime.java:173)
    at 
org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$apply$1(AsyncHttpConnector.java:228)
    at 
java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
    at 
java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
    at 
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
    at 
java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
    at 
org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$retryOperation$4(AsyncHttpConnector.java:270)
    at 
java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
    at 
java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
    at 
java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
    at 
java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
    at 
org.apache.pulsar.shade.org.asynchttpclient.netty.NettyResponseFuture.loadContent(NettyResponseFuture.java:222)
    at 
org.apache.pulsar.shade.org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture.java:257)
    at 
org.apache.pulsar.shade.org.asynchttpclient.netty.handler.AsyncHttpClientHandler.finishUpdate(AsyncHttpClientHandler.java:241)
    at 
org.apache.pulsar.shade.org.asynchttpclient.netty.handler.HttpHandler.handleChunk(HttpHandler.java:114)
    at 
org.apache.pulsar.shade.org.asynchttpclient.netty.handler.HttpHandler.handleRead(HttpHandler.java:143)
    at 
org.apache.pulsar.shade.org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:78)
    at 
org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
    at 
org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
    at 
org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
    at 
org.apache.pulsar.shade.io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
    at 
org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
    at 
org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
    at 
org.apache.pulsar.shade.io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
    at 
org.apache.pulsar.shade.io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
    at 
org.apa

[jira] [Created] (PULSAR-21) "reconsumeLater method not support" exception using Pulsar client in Flink 1.15.0

2022-05-12 Thread Jason Kania (Jira)

Jason Kania created PULSAR-21:
-

 Summary: "reconsumeLater method not support" exception using 
Pulsar client in Flink 1.15.0
 Key: PULSAR-21
 URL: https://issues.apache.org/jira/browse/PULSAR-21
 Project: Pulsar
  Issue Type: Improvement
 Environment: Java 11 on Ubuntu 20.04
Reporter: Jason Kania


I have just upgraded from 1.12.7 to 1.15.0 of Flink. The installation is 
currently using the 2.9.2 version of Pulsar. Now, the code pulsar client is 
generating the following Exception:

 

2022-05-13 02:37:42,674 ERROR 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager [] - 
Received uncaught exception.
java.lang.RuntimeException: SplitFetcher thread 0 received unexpected exception 
while polling the records
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:150)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:105)
 [flink-connector-files-1.15.0.jar:1.15.0]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
[?:?]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
[?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.io.IOException: 
org.apache.pulsar.client.api.PulsarClientException: reconsumeLater method not 
support!
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:140)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.fetch(PulsarUnorderedPartitionSplitReader.java:55)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.FetchTask.run(FetchTask.java:58)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:142)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        ... 6 more
Caused by: org.apache.pulsar.client.api.PulsarClientException: reconsumeLater 
method not support!
        at 
org.apache.pulsar.client.impl.ConsumerBase.reconsumeLater(ConsumerBase.java:345)
 ~[pulsar-client-all-2.9.2.jar:2.9.2]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.lambda$pollMessage$1(PulsarUnorderedPartitionSplitReader.java:109)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneaky(PulsarExceptionUtils.java:60)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneakyClient(PulsarExceptionUtils.java:41)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.pollMessage(PulsarUnorderedPartitionSplitReader.java:107)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:115)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.fetch(PulsarUnorderedPartitionSplitReader.java:55)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[Discussion] Do you like the blue background of the New Pulsar Website?

2022-05-12 Thread Yu

Hi everyone,

For the new Pulsar website, we got much negative feedback about the
blue background
color, it decreases readability significantly.

They prefer the white background color as before, which looks more clearly.

Feel free to thumb up on this comment [1] if you feel the same.


We may change the background color to white based on your thoughts, thanks!


[1] https://github.com/apache/pulsar/issues/15538#issuecomment-1125602899


Anonymitaet

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

2022-05-12 Thread Dave Fisher

Hi -

The two most important issues are search and translations. I’d like to know 
when these will be fixed. Also, I’ve been trying google as an alternative to 
our broken search and it is giving me ancient docs instead of latest.

IMO - These graphical issues are comparatively trivial. That and there was a 
survey. Why weren’t these criticisms provided?

Regards,
Dave

Sent from my iPhone

> On May 12, 2022, at 8:23 PM, Yu  wrote:
> 
> Hi everyone,
> 
> For the new Pulsar website, we got much negative feedback about the
> blue background
> color, it decreases readability significantly.
> 
> They prefer the white background color as before, which looks more clearly.
> 
> Feel free to thumb up on this comment [1] if you feel the same.
> 
> 
> We may change the background color to white based on your thoughts, thanks!
> 
> 
> [1] https://github.com/apache/pulsar/issues/15538#issuecomment-1125602899
> 
> 
> Anonymitaet

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

2022-05-12 Thread Dave Fisher

In addition those who don’t like the light blue background have the dark option 
of a black background.

Sent from my iPhone

> On May 12, 2022, at 8:33 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> The two most important issues are search and translations. I’d like to know 
> when these will be fixed. Also, I’ve been trying google as an alternative to 
> our broken search and it is giving me ancient docs instead of latest.
> 
> IMO - These graphical issues are comparatively trivial. That and there was a 
> survey. Why weren’t these criticisms provided?
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On May 12, 2022, at 8:23 PM, Yu  wrote:
>> 
>> Hi everyone,
>> 
>> For the new Pulsar website, we got much negative feedback about the
>> blue background
>> color, it decreases readability significantly.
>> 
>> They prefer the white background color as before, which looks more clearly.
>> 
>> Feel free to thumb up on this comment [1] if you feel the same.
>> 
>> 
>> We may change the background color to white based on your thoughts, thanks!
>> 
>> 
>> [1] https://github.com/apache/pulsar/issues/15538#issuecomment-1125602899
>> 
>> 
>> Anonymitaet

[jira] [Updated] (PULSAR-21) "reconsumeLater method not support" exception using Pulsar client in Flink 1.15.0

2022-05-12 Thread Jason Kania (Jira)



 [ 
https://issues.apache.org/jira/browse/PULSAR-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Kania updated PULSAR-21:
--
Description: 
I have just upgraded from 1.12.7 to 1.15.0 of Flink. The installation is 
currently using the 2.9.2 version of Pulsar. Now, the pulsar client is 
generating the following exception:

 

2022-05-13 02:37:42,674 ERROR 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager [] - 
Received uncaught exception.
java.lang.RuntimeException: SplitFetcher thread 0 received unexpected exception 
while polling the records
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:150)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:105)
 [flink-connector-files-1.15.0.jar:1.15.0]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
[?:?]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
[?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.io.IOException: 
org.apache.pulsar.client.api.PulsarClientException: reconsumeLater method not 
support!
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:140)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.fetch(PulsarUnorderedPartitionSplitReader.java:55)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.FetchTask.run(FetchTask.java:58)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:142)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        ... 6 more
Caused by: org.apache.pulsar.client.api.PulsarClientException: reconsumeLater 
method not support!
        at 
org.apache.pulsar.client.impl.ConsumerBase.reconsumeLater(ConsumerBase.java:345)
 ~[pulsar-client-all-2.9.2.jar:2.9.2]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.lambda$pollMessage$1(PulsarUnorderedPartitionSplitReader.java:109)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneaky(PulsarExceptionUtils.java:60)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneakyClient(PulsarExceptionUtils.java:41)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.pollMessage(PulsarUnorderedPartitionSplitReader.java:107)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:115)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.fetch(PulsarUnorderedPartitionSplitReader.java:55)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]

  was:
I have just upgraded from 1.12.7 to 1.15.0 of Flink. The installation is 
currently using the 2.9.2 version of Pulsar. Now, the pulsar client is 
generating the following Exception:

 

2022-05-13 02:37:42,674 ERROR 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager [] - 
Received uncaught exception.
java.lang.RuntimeException: SplitFetcher thread 0 received unexpected exception 
while polling the records
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:150)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:105)
 [flink-connector-files-1.15.0.jar:1.15.0]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
[?:?]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
[?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.io.IOException: 
org.apache.pulsar.client.api.PulsarClientException: reconsumeLater method not 
support!
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:140)
 ~[flink-connector-pul

[jira] [Updated] (PULSAR-21) "reconsumeLater method not support" exception using Pulsar client in Flink 1.15.0

2022-05-12 Thread Jason Kania (Jira)



 [ 
https://issues.apache.org/jira/browse/PULSAR-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Kania updated PULSAR-21:
--
Description: 
I have just upgraded from 1.12.7 to 1.15.0 of Flink. The installation is 
currently using the 2.9.2 version of Pulsar. Now, the pulsar client is 
generating the following Exception:

 

2022-05-13 02:37:42,674 ERROR 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager [] - 
Received uncaught exception.
java.lang.RuntimeException: SplitFetcher thread 0 received unexpected exception 
while polling the records
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:150)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:105)
 [flink-connector-files-1.15.0.jar:1.15.0]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
[?:?]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
[?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.io.IOException: 
org.apache.pulsar.client.api.PulsarClientException: reconsumeLater method not 
support!
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:140)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.fetch(PulsarUnorderedPartitionSplitReader.java:55)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.FetchTask.run(FetchTask.java:58)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:142)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        ... 6 more
Caused by: org.apache.pulsar.client.api.PulsarClientException: reconsumeLater 
method not support!
        at 
org.apache.pulsar.client.impl.ConsumerBase.reconsumeLater(ConsumerBase.java:345)
 ~[pulsar-client-all-2.9.2.jar:2.9.2]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.lambda$pollMessage$1(PulsarUnorderedPartitionSplitReader.java:109)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneaky(PulsarExceptionUtils.java:60)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.common.utils.PulsarExceptionUtils.sneakyClient(PulsarExceptionUtils.java:41)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.pollMessage(PulsarUnorderedPartitionSplitReader.java:107)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:115)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarUnorderedPartitionSplitReader.fetch(PulsarUnorderedPartitionSplitReader.java:55)
 ~[flink-connector-pulsar-1.15.0.jar:1.15.0]

  was:
I have just upgraded from 1.12.7 to 1.15.0 of Flink. The installation is 
currently using the 2.9.2 version of Pulsar. Now, the code pulsar client is 
generating the following Exception:

 

2022-05-13 02:37:42,674 ERROR 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager [] - 
Received uncaught exception.
java.lang.RuntimeException: SplitFetcher thread 0 received unexpected exception 
while polling the records
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:150)
 ~[flink-connector-files-1.15.0.jar:1.15.0]
        at 
org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:105)
 [flink-connector-files-1.15.0.jar:1.15.0]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
[?:?]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
[?:?]
        at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.io.IOException: 
org.apache.pulsar.client.api.PulsarClientException: reconsumeLater method not 
support!
        at 
org.apache.flink.connector.pulsar.source.reader.split.PulsarPartitionSplitReaderBase.fetch(PulsarPartitionSplitReaderBase.java:140)
 ~[flink-connecto

Pulsar Community Meeting Notes 2022/05/12, (8:30 AM PST)

2022-05-12 Thread Michael Marshall

Hi Pulsar Community,

Here are the meeting notes from yesterday's community meeting. There
were many relevant comments, so the notes are particularly long.
Thanks to all who participated!

Disclaimer: If something is misattributed or misrepresented, please
send a correction to this list.

Source google doc:
https://docs.google.com/document/d/19dXkVXeU2q_nHmkG8zURjKnYlvD96TbKf5KjYyASsOE

Thanks,
Michael

2022/05/12, (8:30 AM PST)
-   Attendees:
-   Matteo Merli
-   Lari Hotari
-   Dave Fisher
-   Aaron Williams
-   Michael Marshall
-   Andrey Yegorov
-   Massimiliano Mirelli
-   Nicolò Boschi
-   Enrico Olivelli

-   Discussions

-   Enrico: discuss PIP 117. Matteo: can we pass a cli flag? Enrico:
that won’t work for the old version, but we can make it work with an
env var. They both agreed on that solution.

-   Matteo: asks about the JDK discussion from the mailing list.
Enrico: we are trying to understand the impact to customers if we have
a strict requirement for JDK 17. Pretty sure it is not the right time
to force users to upgrade to 17. Jumping from 8 to 17 is a really big
jump. Middle ground is to require 11. Matteo: JDK 11 doesn’t give us
any big source changes. There are some runtime improvements, though.
Switching to 11 is a hassle for users because they have to upgrade
from 8 to 11. OTOH, there are many new features from 8 to 17 that we
can start to use. There are also a lot of runtime improvements from 11
to 17. Yes, there are still people using 8. There are also people that
will delay adoption of Pulsar 2.11. We can give these users a 2.10
LTS, which brings back the other discussion on LTS and how to make
that work. Dave: one question to ask is if 2.10 is a feature complete
version. Will 2.11 have features we wish were in 2.10? Matteo: each
version is supposed to be feature complete. Michael: a nuance might be
transactions, which were not production ready until recently. Matteo:
non-production ready features would be a reason to upgrade. Dave: what
about new users that might only be using JDK 8? Note that Oracle
dropped commercial support recently. Matteo: thinks Java has taken
good steps to ensure users can upgrade. Michael: we’ll need to take
care to make sure that cherry picks are still easily applied.
Refactoring could prove problematic. Matteo: we should make sure to
update the contributor guide to document that we won’t accept
arbitrary refactoring to use JDK 17 specific language features. Dave:
how can CI help us? Matteo: ci will fail if cherry picked to recent
versions. When a committer merges to master, a committer should cherry
pick at that time. This way the release manager doesn’t have as much
work. Dave: how do we keep track of outstanding cherry picks? It can
definitely become unwieldy. Michael: local compilation could help to
prevent pushing unsupported language features to maintenance branches.
Matteo: yes, that’s true. Lari: I usually run "mvn
-Pcore-modules,-main -T 1C clean install -DskipTests
-Dspotbugs.skip=true" since it's fairly quick to run. Also, flaky
tests make it harder to trust the signals for a failed build on a
maintenance branch. Michael: I think it’s valuable that we’re going to
guide contributors to avoid code refactoring. Matteo: yes, are we able
to decide when we’ll start accepting those refactorings? New features
(net new code) will be fine for new language features because it won’t
get cherry picked. Is there a time limit for when we can start using
new language features? Dave: for now don’t do it and we can review
later. Lari: same issue about refactoring applies to more than just
JDK 17 features. Recently found PRs that make sense, but cause issues
because they have sprawling changes. High level guidance would be very
helpful. This raises the question of when we can do these kinds of
refactorings. For example, the Managed Ledger class is a huge class
and it’d be great to refactor, but we don’t because it’s more stable
to leave it as is for now. In this example, how can we redesign it in
a safe way? There are some thread safety issues that might be resolved
with a larger change. Matteo: would it make sense to start fresh?
There is an interface (possibly not well abstracted), but could we
have two implementations. Lari: I’ve had that thought, but maybe it’s
a Pulsar 3.0 type change. Larger refactorings could be done at that
time. Otherwise we’re stuck with the same code base. Matteo: I’m
saying we can use a different implementation because it is pluggable.
We do this for other classes, already. It’d probably be easier to
start from scratch and mature a prototype. This allows users to opt
into the new code. That gives contributors more freedom to move fast.
Lari: that’s probably the approach we’d take. This approach won’t work
for something like load manager, though because the code doesn’t have
a good abstraction. Matteo: yes, that is something we’ve been looking
into. It’d probably need a new abstraction. We are in the phase of
getting people to understan

[GitHub] [pulsar-site] Anonymitaet commented on pull request #75: Add line number in code blocks

2022-05-12 Thread GitBox



Anonymitaet commented on PR #75:
URL: https://github.com/apache/pulsar-site/pull/75#issuecomment-1125706490

   @urfreespace can you help review? 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-site] urfreespace commented on pull request #75: Add line number in code blocks

2022-05-12 Thread GitBox



urfreespace commented on PR #75:
URL: https://github.com/apache/pulsar-site/pull/75#issuecomment-1125709663

   Good job! LGTM, thanks @SignorMercurio 


-- 
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-site] urfreespace closed pull request #74: fix: blogs fix

2022-05-12 Thread GitBox



urfreespace closed pull request #74: fix: blogs fix
URL: https://github.com/apache/pulsar-site/pull/74


-- 
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

[DISCUSS] PIP-166: Function add NONE delivery semantics

Re: [DISCUSS] PIP-158: Split client TLS transport encryption from authentication

Re: [DISCUSS] PIP-158: Split client TLS transport encryption from authentication

RE: [VOTE] PIP-156: Enable system topic by default

Re: [VOTE] Pulsar Manager Release 0.3.0 Candidate 3

Re: New Pulsar Website is Live!

Re: [VOTE] [PIP-153] Optimize metadataPositions in MLPendingAckStore

Re: New Pulsar Website is Live!

[GitHub] [pulsar-site] SignorMercurio opened a new pull request, #75: Add line number in code blocks

[jira] [Created] (PULSAR-20) Exception for "Topic not exist" should name the topic and server

[jira] [Created] (PULSAR-21) "reconsumeLater method not support" exception using Pulsar client in Flink 1.15.0

[Discussion] Do you like the blue background of the New Pulsar Website?

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

Re: [Discussion] Do you like the blue background of the New Pulsar Website?

[jira] [Updated] (PULSAR-21) "reconsumeLater method not support" exception using Pulsar client in Flink 1.15.0

[jira] [Updated] (PULSAR-21) "reconsumeLater method not support" exception using Pulsar client in Flink 1.15.0

Pulsar Community Meeting Notes 2022/05/12, (8:30 AM PST)

[GitHub] [pulsar-site] Anonymitaet commented on pull request #75: Add line number in code blocks

[GitHub] [pulsar-site] urfreespace commented on pull request #75: Add line number in code blocks

[GitHub] [pulsar-site] urfreespace closed pull request #74: fix: blogs fix

20 matches

Site Navigation

Mail list logo

Footer information