Re: [VOTE] PIP - Support pluggable entry filter in Dispatcher

[Enrico Olivelli]

+1 (binding)

great work !

Enrico

Il giorno mer 13 ott 2021 alle ore 08:34 linlin  ha
scritto:

> Hi Pulsar Community,
>
> I would like to start a VOTE for PIP - Support pluggable entry filter in
> Dispatcher.
>
> The issue for this PIP is here:
> https://github.com/apache/pulsar/issues/12269
>
> Please VOTE within 72 hours.
>
> Thanks,
> Lin Lin
>

Re: [VOTE] PIP - Support pluggable entry filter in Dispatcher

[Hang Chen]

+1 (binding)

Good job!

Thanks,
Hang

Enrico Olivelli  于2021年10月13日周三 下午5:04写道：
>
> +1 (binding)
>
> great work !
>
> Enrico
>
> Il giorno mer 13 ott 2021 alle ore 08:34 linlin  ha
> scritto:
>
> > Hi Pulsar Community,
> >
> > I would like to start a VOTE for PIP - Support pluggable entry filter in
> > Dispatcher.
> >
> > The issue for this PIP is here:
> > https://github.com/apache/pulsar/issues/12269
> >
> > Please VOTE within 72 hours.
> >
> > Thanks,
> > Lin Lin
> >

[GitHub] [pulsar-helm-chart] frankjkelly closed issue #158: Helm chart does not support Istio: Add support for Istio standard port naming

[GitBox]

frankjkelly closed issue #158:
URL: https://github.com/apache/pulsar-helm-chart/issues/158


   


-- 
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] frankjkelly commented on issue #158: Helm chart does not support Istio: Add support for Istio standard port naming

[GitBox]

frankjkelly commented on issue #158:
URL: 
https://github.com/apache/pulsar-helm-chart/issues/158#issuecomment-942538854


   Fixed by https://github.com/apache/pulsar-helm-chart/pull/162 


-- 
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] hangc0276 commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery

[GitBox]

hangc0276 commented on pull request #165:
URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-941868430


   > Just for my information can someone explain why Autorecovery should use 
the V2 protocol but the Broker V3? Thanks in advance!
   
   @frankjkelly I broker side, it has been set the bookie client use V2 
protocol by default.


-- 
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] frankjkelly closed issue #158: Helm chart does not support Istio: Add support for Istio standard port naming

[GitBox]

frankjkelly closed issue #158:
URL: https://github.com/apache/pulsar-helm-chart/issues/158


   


-- 
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] frankjkelly commented on issue #158: Helm chart does not support Istio: Add support for Istio standard port naming

[GitBox]

frankjkelly commented on issue #158:
URL: 
https://github.com/apache/pulsar-helm-chart/issues/158#issuecomment-942538854


   Fixed by https://github.com/apache/pulsar-helm-chart/pull/162 


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

[OUTREACH] ApacheCon @home 2021 videos have been posted

[Aaron Williams]

Here is a link to blurb that we created:
https://apache-pulsar-neighborhood.medium.com/apachecon-2021-videos-are-posted-59639bdcdbd6

Here is the text, but I am not sure if the links will work.

Hello Neighbors,

Just a quick note. We have had people asking about the Apache Pulsar videos
from ApacheCon @Home 2021 and when would they be posted? And we now have an
answer, *today*. You can find all of the sessions here
. But we did make a playlist of the Apache Pulsar
videos on the Apache Pulsar Neighborhood YouTube

channel. (We will update the resources page soon). Each of the videos have
a lot of good information in them. If you like the video, please click on
the like button. It will help highlight the great work our neighbors are
doing.

Thanks.

Links: Medium , Meetups
, YouTube
, and Twitter
.

[DISCUSSION] PIP-104: Add new consumer type: TableView

[Matteo Merli]

https://github.com/apache/pulsar/issues/12356

--- Pasted here for quoting convenience ---





## Motivation

In many use cases, applications are using Pulsar consumers or readers to fetch
all the updates from a topic and construct a map with the latest value of each
key for the messages that were received. This is very common when constructing
a local cache of the data.

We want to offer support for this access pattern directly in the Pulsar client
API, as a way to encapsulate the complexities of setting this up.


## Goal

Provide a view of the topic data in the form of a read-only map that is
constantly updated with the latest version of each key.

Additionally, let the application specify a listener so that it can perform
a scan of the map and then receive notifications when new messages are
received and applied.

## API Changes

This proposal will only add a new API on the client side.

A new type of consumer will be added, the `TableView`.

Example:

```java
TableView tableView = pulsarClient.newTableView(Schema.INT32)
.topic(topic)
.create();

tableView.get("my-key"); // --> 5
tableView.get("my-other-key"); // --> 7
```

When a `TableView` instance is created, it will be guaranteed to already have
the latest value for each key, for the current time.

### API additions

```java
interface PulsarClient {
// 
 TableViewBuilder newTableView(Schema schema);
}

interface TableViewBuilder {
TableViewBuilder loadConf(Map config);
TableView create() throws PulsarClientException;
CompletableFuture> createAsync();
TableViewBuilder topic(String topic);
TableViewBuilder autoUpdatePartitionsInterval(int interval,
TimeUnit unit);
}

interface TableView extends Closeable {

// Similar methods as java.util.Map
int size();
boolean isEmpty();
boolean containsKey(String key);
T get(String key);
Set> entrySet();
Set keySet();
Collection values();
void forEach(BiConsumer action);

/**
 * Performs the given action for each entry in this map until all entries
 * have been processed or the action throws an exception.
 *
 * When all the entries have been processed, the action will be invoked
 * for every new update that is received from the topic.
 *
 * @param action The action to be performed for each entry
 */
void forEachAndListen(BiConsumer action);

/**
 * Close the table view and releases resources allocated.
 *
 * @return a future that can used to track when the table view has
been closed
 */
CompletableFuture closeAsync();
}
```

## Implementation

The `TableView` will be implemented using multiple `Reader` instances, one
per each partition and will always specify to read starting from the compacted
view of the topic.

The creation time of a table view can be controlled by configuring the
topic compaction policies for the given topic or namespace. More frequent
compaction can lead to very short startup times, as in less data will be
replayed to reconstruct the `TableView` of the topic.



--
Matteo Merli

Re: [VOTE] PIP - Support pluggable entry filter in Dispatcher

[PengHui Li]

+1 (binding)

Penghui

On Wed, Oct 13, 2021 at 5:19 PM Hang Chen  wrote:

> +1 (binding)
>
> Good job!
>
> Thanks,
> Hang
>
> Enrico Olivelli  于2021年10月13日周三 下午5:04写道：
> >
> > +1 (binding)
> >
> > great work !
> >
> > Enrico
> >
> > Il giorno mer 13 ott 2021 alle ore 08:34 linlin  ha
> > scritto:
> >
> > > Hi Pulsar Community,
> > >
> > > I would like to start a VOTE for PIP - Support pluggable entry filter
> in
> > > Dispatcher.
> > >
> > > The issue for this PIP is here:
> > > https://github.com/apache/pulsar/issues/12269
> > >
> > > Please VOTE within 72 hours.
> > >
> > > Thanks,
> > > Lin Lin
> > >
>

[REPORT] Pulsar - October 2021

[Matteo Merli]

## Description:

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

## Issues:
 - There are no issues requiring board attention at this time.

## Project Activity:
  - 2.7.3 was released on July 27th 2021
  - 2.8.0 was released on June 12th 2021
  - 2.8.1 was released on September 10th 2021
  - Pulsar Client Go 0.6.0 was released on July 25th 2021
  - Pulsar Client Node 1.4.0 was released on August 2nd 2021
  - Pulsar Client Node 1.3.1 was released on September 17th 2021

  - There were a lot of improvement proposals discussed this quarter:
* PIP 104: Add new consumer type: TableView
* PIP 101: Add seek by index feature for consumer
* PIP 100: Pulsar pluggable topic factory
* PIP 97: Asynchronous Authentication Provider
* PIP 95: Smart Listener Selection with Multiple Bind Addresses
* PIP 94: Support level increment delay for ReconsumerLater interface
* PIP 93: Transaction performance tools
* PIP 92: Topic policy across multiple clusters
* PIP 91: Separate lookup timeout from operation timeout
* PIP 90: Expose broker entry metadata to the client
* PIP 89: Structured document logging
* PIP 88: Replicate schemas across multiple
* PIP 87: Pulsar Website Redesign
* PIP 86: Pulsar Functions: Preload and release external resources

  - Pulsar has reached 452 contributors on the main Github repo (10%
increase since June 2021 when there were 408 contributors)

  - The second edition of Pulsar Summit North America was held on
June 16, 17 2021, the first edition on Pulsar Summit EU was on October 6th,
and the 2nd edition of Pulsar Summit Asia will be on November 20-21.

  - There were several talks on Pulsar at ApacheCon and other virtual
conferences and new meetups dedicated to Pulsar were created.

  - Next release 2.9.0 is in preparation and expected to be ready
within a week.

## Health report:
  - There is healthy grow in the community, several users are starting to
become contributors to the project and engaging more and more with
the community. In this quarter 8 contributors were invited as
committers to the project.

## Membership Data:
  Apache Pulsar was founded 2018-09-18 (3 years ago)

  There are currently 46 committers and 28 PMC members in this project.
  The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
 - Hang Chen was added to the PMC on 2021-08-01
 - Enrico Olivelli was added to the PMC on 2021-08-01
 - Lin Lin was added to the PMC on 2021-07-28
 - David Kjerrumgaard was added as committer on 2021-09-30
 - Rui Fu was added as committer on 2021-08-09

## Community Health:

 - Activity on the mailing lists remains high with a mixture of new users,
   contributors, and deeper more experienced users and contributors sparking
   discussion and questions and filing bugs or new features.

 - us...@pulsar.apache.org:
- 4% increase in traffic in the past quarter (94 emails compared to 90)

 - dev@pulsar.apache.org:
- 19% increase in traffic in the past quarter (921 emails compared to 769)


## Slack activity:
  - 4393 Members (3256 in June 2021)
  - 252  Active weekly users (496 in June 2021)


## GitHub activity:
 - 1066 commits in the past quarter (-8% decrease)
 - 121 code contributors in the past quarter (-10% change)
 - 730 PRs opened on GitHub, past quarter (-12% change)
 - 670 PRs closed on GitHub, past quarter (-16% change)
 - 422 issues opened on GitHub, past quarter (1% increase)
 - 213 issues closed on GitHub, past quarter (-11% change)


--
Matteo Merli

[GitHub] [pulsar-dotpulsar] ZamTheman opened a new issue #91: Usage of System.Diagnostics.DiagnosticsSource (5.0.1) break Azure Insights

[GitBox]

ZamTheman opened a new issue #91:
URL: https://github.com/apache/pulsar-dotpulsar/issues/91


   After implementing the package in our project the Azure Insights stopped 
working. After some investigations there seems to be known known conflict when 
using System.Diagnostics.DiagnosticsSource.
   I tested with a poc app and when bringing in just that dll (5.0.1) the 
insights directly stopped working in Azure.
   
   See: 
https://docs.microsoft.com/en-us/azure/azure-monitor/app/status-monitor-v2-troubleshoot
   
   Would it be possible to remove that dependancy?
   


-- 
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: [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1

[Hiroyuki Sakai]

+1 (binding)

* check the license headers
* install the npm package
* build the source and run producer/consumer
* verify checksum and signatures

==
Hiroyuki Sakai
Yahoo Japan Corp.
E-mail: hsa...@yahoo-corp.jp

From: Masahiro Sakamoto 
Sent: Tuesday, October 12, 2021 19:26
To: dev@pulsar.apache.org 
Subject: [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1

This is the first release candidate for Apache Pulsar Node.js client, version 
1.4.1.

The artifacts are exactly the same as the first vote, but I didn't upload them 
and the signature
to the staging repository of dist, so I'll run the vote again.

It fixes the following issues:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Fmilestone%2F10%3Fclosed%3D1&data=04%7C01%7Chsakai%40yahoo-corp.jp%7Ce96d8ccb9bdf4ddad16608d98d6ac32c%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637696311939247791%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=kRxPDdqrbVRZo29t%2BAx79lUK6SkH8ZfBosgqSvCq0KE%3D&reserved=0

*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***

Note that we are voting upon the source (tag), the npm package is provided
for convenience.

Source files:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-client-node-1.4.1-candidate-1%2F&data=04%7C01%7Chsakai%40yahoo-corp.jp%7Ce96d8ccb9bdf4ddad16608d98d6ac32c%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637696311939257745%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=F1l%2Bp2fS6yN0ixzhdMz07HJHgQlik2AMownaL2Ph5ZA%3D&reserved=0

SHA-512 checksum:
b011b20e337af01542e2d9d3f6e74b8f506fab9b29227c8447f263e15103944bcb37a14643e4bcfa3286ec05c4d00f2d210708d6c06cb5851004ce099f77fcaf
  v1.4.1-rc.1.tar.gz

The tag to be voted upon:
v1.4.1-rc.1
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Freleases%2Ftag%2Fv1.4.1-rc.1&data=04%7C01%7Chsakai%40yahoo-corp.jp%7Ce96d8ccb9bdf4ddad16608d98d6ac32c%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637696311939257745%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XNgrb%2BpPg8XywNDVm2Nbr%2Bay5QCPweEr1k1Tu%2Fkw1A8%3D&reserved=0

The npm package:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2Fpulsar-client%2Fv%2F1.4.1-rc.1&data=04%7C01%7Chsakai%40yahoo-corp.jp%7Ce96d8ccb9bdf4ddad16608d98d6ac32c%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637696311939257745%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=b7BTcrBMwbh8p18NNLYwzPQkz6xJe4bajF2S7fypzps%3D&reserved=0

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS&data=04%7C01%7Chsakai%40yahoo-corp.jp%7Ce96d8ccb9bdf4ddad16608d98d6ac32c%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637696311939257745%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yKDZ6R6Qq6RUyscgr8IhYHnv1JG%2FmWpQa5bjaISeQaM%3D&reserved=0

Please download the source files, and follow the README to build
and run the Pulsar Node.js client.

Masahiro Sakamoto
Yahoo Japan Corp.
E-mail: massa...@yahoo-corp.jp