Re: [PR] pulsar-adapters: remove Flink adapter

2022-02-03 Thread Enrico Olivelli
The patch is merged. Thank you Andrey, removing dead code is a good thing, as it allows the community to not waste energy. Enrico Il Ven 4 Feb 2022, 06:04 Devin Bost ha scritto: > I support this change. Having different connectors in each project is > actually really confusing for new folks

Re: [PR] pulsar-adapters: remove Flink adapter

2022-02-03 Thread Devin Bost
I support this change. Having different connectors in each project is actually really confusing for new folks since it's not automatically clear which adapter they should be using. -- Devin G. Bost On Thu, Feb 3, 2022, 1:17 PM Andrey Yegorov wrote: > Hello, > > I created a PR to remove Flink fr

[GitHub] [pulsar-adapters] michaeljmarshall merged pull request #34: Removing Flink adapter in favor of the one included with Flink

2022-02-03 Thread GitBox
michaeljmarshall merged pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34 -- 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: d

[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #224: Allow us to turn on PodSecurityPolicy for Pulsar clusters with the same name deployed in different K8S namespaces in the same c

2022-02-03 Thread GitBox
frankjkelly commented on pull request #224: URL: https://github.com/apache/pulsar-helm-chart/pull/224#issuecomment-1029360884 @ckdarby good point `1.25` will be coming at some point later this year `1.24` looks due in April https://github.com/kubernetes/sig-release/tree/master/releases/re

[GitHub] [pulsar-helm-chart] ckdarby commented on pull request #224: Allow us to turn on PodSecurityPolicy for Pulsar clusters with the same name deployed in different K8S namespaces in the same clust

2022-02-03 Thread GitBox
ckdarby commented on pull request #224: URL: https://github.com/apache/pulsar-helm-chart/pull/224#issuecomment-1029349997 Just an FYI, from [the docs](https://kubernetes.io/docs/concepts/policy/pod-security-policy/): > PodSecurityPolicy is deprecated as of Kubernetes v1.21, and will be

[GitHub] [pulsar-adapters] dlg99 commented on pull request #34: Removing Flink adapter in favor of the one included with Flink

2022-02-03 Thread GitBox
dlg99 commented on pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34#issuecomment-1029332355 @merlimat I updated readme -- 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

[GitHub] [pulsar-adapters] dlg99 commented on a change in pull request #34: Removing Flink adapter in favor of the one included with Flink

2022-02-03 Thread GitBox
dlg99 commented on a change in pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34#discussion_r798905138 ## File path: examples/kafka-streams/src/main/java/org/apache/kafka/kafkastreams/pulsar/example/PageViewTypedDemo.java ## @@ -0,0 +1,279 @@ +/** + * Li

[GitHub] [pulsar-adapters] michaeljmarshall commented on a change in pull request #34: Removing Flink adapter in favor of the one included with Flink

2022-02-03 Thread GitBox
michaeljmarshall commented on a change in pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34#discussion_r798896872 ## File path: examples/kafka-streams/src/main/java/org/apache/kafka/kafkastreams/pulsar/example/PageViewTypedDemo.java ## @@ -0,0 +1,279 @@

[GitHub] [pulsar-adapters] dlg99 commented on a change in pull request #34: Removing Flink adapter in favor of the one included with Flink

2022-02-03 Thread GitBox
dlg99 commented on a change in pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34#discussion_r798893867 ## File path: examples/kafka-streams/src/main/java/org/apache/kafka/kafkastreams/pulsar/example/PageViewTypedDemo.java ## @@ -0,0 +1,279 @@ +/** + * Li

[GitHub] [pulsar-adapters] merlimat commented on pull request #34: Removing Flink adapter in favor of the one included with Flink

2022-02-03 Thread GitBox
merlimat commented on pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34#issuecomment-1029318181 We could also update the README to mention the adapters that are now developed somewhere else -- This is an automated message from the Apache Git Service. To respond to

[GitHub] [pulsar-adapters] michaeljmarshall commented on a change in pull request #34: Removing Flink in favor of the one included with Flink

2022-02-03 Thread GitBox
michaeljmarshall commented on a change in pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34#discussion_r798892369 ## File path: examples/kafka-streams/src/main/java/org/apache/kafka/kafkastreams/pulsar/example/PageViewTypedDemo.java ## @@ -0,0 +1,279 @@

[PR] pulsar-adapters: remove Flink adapter

2022-02-03 Thread Andrey Yegorov
Hello, I created a PR to remove Flink from the Pulsar adapters project: https://github.com/apache/pulsar-adapters/pull/34 Motivation is: * It is based on an old version of Flink (1.7.2, current is 1.14.3) which brings in dependencies with various CVEs. 1.7 is not maintained anymore. * Flink added

[GitHub] [pulsar-adapters] dlg99 opened a new pull request #34: Removing Flink in favor of the one included with Flink

2022-02-03 Thread GitBox
dlg99 opened a new pull request #34: URL: https://github.com/apache/pulsar-adapters/pull/34 ### Motivation Removing Flink in favor of https://github.com/apache/flink/tree/master/flink-connectors/flink-connector-pulsar This one is based on an old version of Flink which bring in dep

Re: Pulsar Flaky test report 2022-02-03 for PR builds in CI

2022-02-03 Thread Lari Hotari
I added the links to GitHub issues to the spreadsheet: https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit#gid=456314619 Let's focus fixing the top 10 most flaky tests asap. Please comment on the issue that you are working on it so that we don't unnecessarily do

Re: [DISCUSS] PIP-136: Sync Pulsar policies across multiple clouds

2022-02-03 Thread Joe F
>On my first reading, it wasn't clear if there was only one topic required for this feature. I now see that the topic is not tied to a specific tenant or namespace. As such, we can avoid complicated authorization questions by putting the required event topic(s) into a "system" tenant and namespace

Blocker issues on 'master' and 'branch-2.9' branches

2022-02-03 Thread Nicolò Boschi
Hi folks, Just want to make you notice that currently the master branch has two blocker issues: 1. https://github.com/apache/pulsar/issues/14104 2. https://github.com/apache/pulsar/pull/13891 Also the 2.9 branch has one blocker issue - a regression introduced with Pulsar 2.9.0. I believe it is be

Pulsar Flaky test report 2022-02-03 for PR builds in CI

2022-02-03 Thread Lari Hotari
Dear Pulsar community members, Here's a report of the flaky tests in Pulsar CI during the observation period of 2022-01-27 to 2022-02-03 . The full report is available as a Google Sheet, https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ There are a lot more flaky

Re: [VOTE] Pulsar Release 2.9.2 Candidate 2

2022-02-03 Thread Nicolò Boschi
Hi Ran, thanks for driving the release. I haven't tested the rc yet but I firmly believe we should include this pull [1] which fixes a regression introduced in Pulsar 2.9.0 [1] https://github.com/apache/pulsar/pull/14097 Il giorno mer 2 feb 2022 alle ore 08:34 Enrico Olivelli ha scritto: > (

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #92: Client usage

2022-02-03 Thread GitBox
blankensteiner commented on issue #92: URL: https://github.com/apache/pulsar-dotpulsar/issues/92#issuecomment-1028829037 You are most welcome .:-) -- 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 t

[GitHub] [pulsar-dotpulsar] VisualBean edited a comment on issue #92: Client usage

2022-02-03 Thread GitBox
VisualBean edited a comment on issue #92: URL: https://github.com/apache/pulsar-dotpulsar/issues/92#issuecomment-1028828300 Awesome, I will most likely contribute an OAuth factory within a couple of days then! -- This is an automated message from the Apache Git Service. To respond to t

[GitHub] [pulsar-dotpulsar] VisualBean closed issue #92: Client usage

2022-02-03 Thread GitBox
VisualBean closed issue #92: URL: https://github.com/apache/pulsar-dotpulsar/issues/92 -- 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-unsubsc

[GitHub] [pulsar-dotpulsar] VisualBean commented on issue #92: Client usage

2022-02-03 Thread GitBox
VisualBean commented on issue #92: URL: https://github.com/apache/pulsar-dotpulsar/issues/92#issuecomment-1028828300 Awesome, I will most likely contribute within a couple of days then! -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #92: Client usage

2022-02-03 Thread GitBox
blankensteiner commented on issue #92: URL: https://github.com/apache/pulsar-dotpulsar/issues/92#issuecomment-1028824684 Yeah, go nuts, you just need to implement IAuthentication :-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [pulsar-dotpulsar] VisualBean commented on issue #92: Client usage

2022-02-03 Thread GitBox
VisualBean commented on issue #92: URL: https://github.com/apache/pulsar-dotpulsar/issues/92#issuecomment-1028808586 Looks good. From my quick glance, it looks like we can simply implement a different authfactory for oauth/whatever we want? I see another issue has been created for OAuth

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

2022-02-03 Thread GitBox
goldenccargill commented on pull request #95: URL: https://github.com/apache/pulsar-dotpulsar/pull/95#issuecomment-1028759637 Fair enough, hadn't considered using the token for the previous tests. Agree merging Stress and Integration would be good. I think over time it might be har

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

2022-02-03 Thread GitBox
blankensteiner commented on pull request #95: URL: https://github.com/apache/pulsar-dotpulsar/pull/95#issuecomment-1028730259 We might need multiple instances in the future, but the old tests could just have a token added and then we only have to maintain one yml-file and only have to spin

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

2022-02-03 Thread GitBox
goldenccargill commented on pull request #95: URL: https://github.com/apache/pulsar-dotpulsar/pull/95#issuecomment-1028719172 Ok, I wanted separate instances as I wanted one instance that used token auth for the new stuff and one that didn't for all the current tests. As long as the

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

2022-02-03 Thread GitBox
blankensteiner commented on pull request #95: URL: https://github.com/apache/pulsar-dotpulsar/pull/95#issuecomment-1028705632 Hi @goldenccargill I couldn't run the tests, so I made some changes to the tests and also ensured that only one standalone instance is used for all the tests in