Fwd: [jira] [Resolved] (INFRA-14694) Enable Nexus Access For Pulsar

The Nexus project is already active and we're already pushing snapshots artifacts in the repo. -- Matteo Merli <mme...@apache.org> -- Forwarded message -- From: Chris Lambertus (JIRA) <j...@apache.org> Date: Fri, Jul 28, 2017 at 5:37 PM Subject: [jira] [Resolved]

Re: [DISCUSS] Pulsar release

(to have a flag that enable static linking, which is needed to create the self-contained python client dist file) After that, if there no objections, I'll start preparing the first candidate package. Matteo -- Matteo Merli <mme...@apache.org> On Tue, Jul 25, 2017 at 9:41 AM, Matteo Merl

Re: CI builds on Jenkins

amount of time rebuilding the same PRs to merge Cons: * We'll get acquainted with the failing tests and possibly never fix them. Any thoughts or preferences? -- Matteo Merli <mme...@apache.org> On Wed, Aug 2, 2017 at 12:22 PM, Matteo Merli <mme...@apache.org> wrote: > Reading

Re: [VOTE] Pulsar 1.19.0-incubating Release Candidate 0

://www.apache.org/dev/publishing-maven-artifacts.html -- Matteo Merli <mme...@apache.org> On Mon, Jul 31, 2017 at 2:39 PM, Matteo Merli <mme...@apache.org> wrote: > This is the first release candidate for Apache Pulsar, version > 1.19.0-incubating. > > Major changes included in this

Re: Pulsar End to End Encryption - Design review

(Did receive it the first time too ;) ) Thanks Andrews, the proposal seems very good and well detailed. I'll take a thorough look at it later today. On Thu, Aug 3, 2017 at 8:14 AM Sahaya Andrews wrote: > Resending since my yesterday's email did not seems to have delivered.

Feedback on release

is relative to the "bin" release. What do people would prefer there? Dropping the link to src release in the getting started page or add instructions to compile? Matteo -- Matteo Merli <mme...@apache.org>

Re: [VOTE] Pulsar 1.19.0-incubating Release Candidate 0

rd/conf/uwsgi_params" I wasn't sure if the uwsgi tools were handling comments correctly. I will test it out and and add headers if it works. Would it be ok to fix in next release? Matteo -- Matteo Merli <mme...@apache.org>

Re: [PROPOSAL] Move github notifications to a separate mailing list

f another name like notifications@ is > preferred then ask Infra to change the name. > > Either way make sure it is set to reply-to dev@. > > Regards, > Dave > > Sent from my iPhone > > > On Aug 10, 2017, at 3:35 PM, Matteo Merli <mme...@apache.org> wrote:

Re: [DISCUSS] Planning for next release 1.20.0-incubating

Nice, should we target for the first half of September? Also it would be good to have all major changes merged around ~1 week before the release, to avoid last-minute surprises. On Thu, Aug 10, 2017 at 5:58 PM Joe F <j...@apache.org> wrote: > I can fill in for one release > > J

[ANNOUNCE] Apache Pulsar 1.19.0-incubating released

The Apache Pulsar team is proud to announce Apache Pulsar version 1.19.0-incubating. This is the first Pulsar release after entering the Apache Incubator. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics,

Re: Committer info in commits

his case: > commit 2b63573eea220a8710a93d87f451188e0f253b22 > Author: Matteo Merli <mme...@apache.org> > Commit: GitHub <nore...@github.com> I submitted the PR and then merged it. Though if I merge someone else's PR, my name/email will appear in the "Commit" field. eg: > commit de24

Re: Rebase and merge

ce to keep > commits small. > > As long as commits in a pull request seem meaningful, I think we should > keep the commits separated. > > What do you think? > > [1] https://github.com/blog/2243-rebase-and-merge-pull-requests > > Masakazu > -- Matteo Merli <mme...@apache.org>

[DISCUSS] Planning for next release 1.20.0-incubating

a rotation between committers for the role of "release manager", the one who will help coordinate the whole process of the release. Since I've already done the first release, who wants to do next? Matteo -- Matteo Merli <mme...@apache.org>

[PROPOSAL] Move github notifications to a separate mailing list

org or git...@pulsar.incubator.apache.org ? I think that, from the ASF perspective, this shouldn't pose any problem, since the primary object is to archive these messages in an ASF list, not necessarily dev@. Mentors, please comment on this aspect. Thanks, Matteo -- Matteo Merli <mme...@apache.org>

Re: How should be the rule about merging?

t provides several benefits: * The reviewer gets more acquainted with the code base * If the change is cryptical, it's a good way to force to add more comments, documentation or context in the PR/commit log message * The more the eyes looking at the change, more chances to figure out bugs.

Re: [PROPOSAL] Created a Slack channel for Pulsar

on the website, so that users will be able to join as well. Matteo -- Matteo Merli <matteo.me...@gmail.com> On Thu, Jul 13, 2017 at 5:13 AM, Sebastián Schepens < sebastian.schep...@mercadolibre.com.invalid> wrote: > +1 > Sure > > On Thu, Jul 13, 2017, 05:18 Hiroyuki Sakai <

Re: Jenkins build is back to stable : pulsar-master » Pulsar Broker #5

I have created this Jenkins job at https://builds.apache.org/job/pulsar-master/ So far it's for testing purposes. It's only building the Java portion, we need a way to build the C++ and python part as well. -- Matteo Merli <matteo.me...@gmail.com> On Tue, Jul 11, 2017 at 1:04 PM, Apache J

Re: Apache rat and license headers

Ok, Thanks for the clarification. I still need to read thoroughly the release process documentation. Then I'll try to give it a shot at fixing the LICENSE and NOTICE files. -- Matteo Merli <mme...@apache.org> On Mon, Jul 10, 2017 at 2:28 PM, Dave Fisher <dave2w...@comcast.net>

Re: Apache rat and license headers

we should just need to list it in the NOTICE file and that should be all. -- Matteo Merli <matteo.me...@gmail.com> On Mon, Jun 26, 2017 at 12:14 PM, Matteo Merli <matteo.me...@gmail.com> wrote: > On Mon, Jun 26, 2017 at 11:49 AM, Dave Fisher <dave2w...@comcast.net> > wro

Re: [PROPOSAL] Created a Slack channel for Pulsar

Well, the subject of the thread should have started with "Creating..." :) On Wed, Jul 12, 2017 at 6:57 PM Yuki Shiga <yush...@yahoo-corp.jp> wrote: > I think it would be nice! > :+1: > > Best, > -- > Yuki > Email: yush...@yahoo-corp.jp > > 2017/07/

Re: Apache rat and license headers

proposal). -- Matteo Merli <matteo.me...@gmail.com> On Wed, Jul 12, 2017 at 10:53 AM, Joe F <j...@apache.org> wrote: > We will have to recursively analyze dependencies. Do we really have to > bundle the runtime dependency bits in the bin distribution? > > (quoting from h

Pulsar web site is online!

for information on how to test locally the changes to site Please submit PRs for anything out of place you see. Matteo -- Matteo Merli <mme...@apache.org>

Re: Pulsar web site is online!

ake a look. The Javadoc link was fixed and the C++ Doxygen and Python generated docs are still broken, though a fix is on the way: https://github.com/apache/incubator-pulsar/pull/585 -- Matteo Merli <matteo.me...@gmail.com> On Wed, Jul 19, 2017 at 1:20 AM, Nozomi Kurihara <nkuri...@yahoo-corp.j

Re: [DISCUSS] Make RocksDb dependency optional

I have just created a PR to upgrade RocksDB and resolve the license issue. https://github.com/apache/incubator-pulsar/pull/587 We don't need to wait on BK release, since we can force which RocksDB version we want to include. -- Matteo Merli <mme...@apache.org> On Tue, Jul 18, 2017 at 2

Re: [DISCUSS] Make RocksDb dependency optional

FYI: License change in RocksDB is already happening: https://github.com/facebook/rocksdb/pull/2589 -- Matteo Merli <mme...@apache.org> On Sat, Jul 15, 2017 at 3:56 PM, Matteo Merli <mme...@apache.org> wrote: > There have been some updates on this story: > > 1. This mornin

Re: [DISCUSS] Make RocksDb dependency optional

?focusedCommentId=16088730=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088730 In light of this, we should continue as we are right now and we should be able to keep using RocksDB. On Fri, Jul 14, 2017 at 3:26 PM Matteo Merli <mme...@apache.org> wrote: &

Re: Github documentation links

is included in the source distribution and it will not be anymore the project "homepage". -- Matteo Merli <matteo.me...@gmail.com> On Fri, Jul 21, 2017 at 2:22 PM, Sahaya Andrews <andr...@apache.org> wrote: > Did we link our GitHub page "Documentation" section

[DISCUSS] Pulsar release

shing.html - http://www.apache.org/dev/publishing-maven-artifacts.html Matteo -- Matteo Merli <mme...@apache.org>

Re: New Slack app installed

I'm trying to re-install the digest app, since I was receiving the digest myself instead of that getting sent here to the mailing list. -- Matteo Merli <mme...@apache.org> On Tue, Jul 25, 2017 at 9:39 AM, Slack <no-re...@slack.com> wrote: > Hi Apache Pulsar Admin, > &g

Re: [DISCUSS] Pulsar release

master/ If anyone has time to look into it.. welcome ;) So my take is, for now use Travis, since it's already in place and working and move to Jenkins once the build is setup there. Matteo -- Matteo Merli <mme...@apache.org> On Mon, Jul 24, 2017 at 3:41 PM, Sahaya Andrews <andr...@ap

Re: Apache rat and license headers

> > >> We cannot include Category X in required dependencies. > > The other thing about RocksDb in Cat-X is that I've been monitoring the dev lists of TLPs which are major users of RocksDb (Kafka, Samza, Flink) and couldn't find any discussion in how they're going to handle it, and in the meantime

Re: Apache rat and license headers

On Wed, Jul 12, 2017 at 11:30 AM, Dave Fisher wrote: > Instead of going through Sonatype we will need to go through the Apache > Distribution and release on Apache infrastructure. These can then be pushed > out through Maven Central and Sonatype. > > Other of the other

[DISCUSS] PIP-1 Pulsar proxy component

, it would be good to have some feedback on the format as well. Matteo -- Matteo Merli <mme...@apache.org>

Fwd: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration

re enabled. Visit https://gitbox.apache.org/setup/ to link the accounts. Notice that it might take a while to reflect the permission (I think there's a cron job that periodically syncs up the accounts permissions). -- Matteo Merli <mme...@apache.org> -- Forwarded message --

Re: Avoid duplicate notification

I think you can setup a filter in gmail and attach a label + skip the inbox for the github notifications to the mailing list. Example of gmail filter: from:(g...@git.apache.org) to:(dev@pulsar.incubator.apache.org,) Send to Pulsar/Git folder -- Matteo Merli <matteo.me...@gmail.com>

Re: Dependencies and Licenses

that other projects will adopt (like Flink, Samza and Kafka) that depend heavily on RocksDb and for which there is no current comparable replacement, unfortunately. So, short answer, we can easily turn it off, but I'd hope to see a common solution for all the Apache projects on this issue. Matteo

Re: [DISCUSS] PIP-1 Pulsar proxy component

For the SSL part, unless you have an L4 proxy such as a VIP, the SSL needs to be terminated at that layer. I think this fits well anyway for most deployment and has the advantage of offloading the SSL portion to the proxy compared to the broker. Matteo -- Matteo Merli <matteo.me...@gmail.com>

Re: Avoid duplicate notification

ls. I'm also a committer > > of Apache Traffic Server and the project uses GitHub but I only receive > > emails from g...@git.apache.org for Pulsar project. > > > > Masakazu > > > > On Fri, Jun 30, 2017 at 9:19 AM, Matteo Merli <matteo.me...@gmail.com> > >

Re: [DISCUSS] PIP-1 Pulsar proxy component

proxy, on the connection where the actual data is being sent, we just need to deserialize the initial Connect/Connected commands, and after that remove the deserialization logic. That makes the proxy very cheap in terms of memory allocated (GC rate is only 1 object per buffer transferred each way) and CPU. -- Matteo Merli <matteo.me...@gmail.com>

Re: [DISCUSS] PIP-1 Pulsar proxy component

I have updated the Wiki page with a section about TLS : https://github.com/apache/incubator-pulsar/wiki/PIP-1#tls-encryption-and-authentication Also, I just posted a PR with the implementation: https://github.com/apache/incubator-pulsar/pull/548 -- Matteo Merli <matteo.me...@gmail.

Re: [DISCUSS] PIP-1 Pulsar proxy component

-performant (the exchanges between client and server happen in JSON and the payloads are serialized in base64.. Matteo -- Matteo Merli <matteo.me...@gmail.com>

Re: [GitHub] rdhabalia commented on a change in pull request #514: Static link dependency libraries for C++ client lib and Python wrapper

On Wed, Jul 5, 2017 at 1:56 PM, wrote: > rdhabalia commented on a change in pull request #514: Static link > dependency libraries for C++ client lib and Python wrapper > URL: https://github.com/apache/incubator-pulsar/pull/514#discussi > on_r125755406 > >

[VOTE] Pulsar 1.19.0-incubating Release Candidate 0

(5125279b50f7a3da8c211b698580e1d2f4dd65e2) Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli <

Re: Aug Podling report - Draft

Draft looks good to me. Just one note: the release in the working is "1.19.0-incubating" -- Matteo Merli <matteo.me...@gmail.com> On Mon, Jul 31, 2017 at 3:02 PM, Joe F <j...@apache.org> wrote: > All, > > It's that time of the month again, the report is d

CI builds on Jenkins

orce a new sha hash. Then push --force to update the PR. If anyone knows or wants to take a look for a better solution.. :) -- Matteo Merli <mme...@apache.org>

Re: [DISCUSS][VOTE] Pulsar 1.19.0-incubating Release Candidate 0

On Wed, Aug 2, 2017 at 8:30 AM, Dave Fisher wrote: > > We use AspectJ to instrument ZooKeeper server and client, in order to > > collect and expose metrics that are not available in ZooKeeper itself. > > At this point is not optional and it's not possible to turn it off. >

Re: Migrating development to incubator

gt; > > > Please respond to emails here and discuss the podling. In order to move > to > > the incubator we need to start talking. > > > > > On Jun 5, 2017, at 1:15 PM, Matteo Merli <mme...@apache.org> wrote: > > > > > > Hi All, > > >

Re: Proposal for Pulsar "PIP"

architecture or a feature, so they can contribute back. > > Coming up with a list of such modules/features is not difficult. > > Andrews. > > > > > Thanks, > > Nozomi Kurihara > > > > 2017/06/09 5:13 に、"Matteo Merli" <mme...@apache.org> を書き込

Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration

;sahaya.andr...@gmail.com> > wrote: > > > I have updated my GitHub id in profile. > > > > What does the "reporeq" step meant to do? > > > > On Wed, Jun 21, 2017 at 2:56 PM, Matteo Merli <mme...@apache.org> wrote: > > > >> The rep

Renaming package names and license headers

I'm going to start to send out PRs to update the license headers and to rename the Package names. I believe that the renaming should not pose a big trouble on the currently opened PRs, since git is able to follow that without conflicts. For the license headers, there might be some conflicts

Re: Renaming package names and license headers

te: > Hi Matteo, > > No - the license header changes must be done by someone from Yahoo. That's > ASF policy that the changes are done from the SGA org. > > Package names are ok. > > Regards, > Dave > > > On Jun 22, 2017, at 10:48 AM, Matteo Merli <mme...@apache.org> w

Re: [jira] [Commented] (INFRA-14376) Pulsar GitHub Integration

n Admin privilege setup with Gitbox > > integration. What can the podling expect? How do we control the group? Do > > we do JIRA tickets? I know the Gitbox integration is new and the > > documentation that you pointed me to is out of date and not on point with > > the new. > > > &g

Re: [GitHub] incubator-pulsar issue #523: Max Payload size is validated before compressio...

des off. Typically most users don't care about latency of bigger messages, so we never really tested it, but at least at lower transfer rate, the latency shouldn't be too bad even for 1MB messages. -- Matteo Merli <matteo.me...@gmail.com> On Mon, Jun 26, 2017 at 1:42 PM, Sahaya Andrews <

Proposal for Pulsar "PIP"

So far the discussion for large code changes (new features, improvements) in the project has happened in a very informal way. As a way to improve community involvement and also to have a better internal documentation I would like to propose to adopt the PIP model that many projects follow. Here,

Re: Proposal for Pulsar "PIP"

should we also consider writing documents for the > features already present? > > Andrews. > > > On Thu, Jun 8, 2017 at 1:13 PM, Matteo Merli <mme...@apache.org> wrote: > > So far the discussion for large code changes (new features, improvements) > >

Re: Migrating development to incubator

2017, at 2:32 PM, Joe F <j...@apache.org> wrote: > > > > Mentors, > > > > I have got confirmation that Yahoo can give admin rights to the pulsar > > repo to someone in ASF infra team. Let me know who, and I will get it > going > > > > Joe >

[DRAFT] Podling report September 2017

? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-08-09, v 1.19.0-incubating When were the last committers or PPMC members elected? Matteo -- Matteo Merli

Re: Podling Report Reminder - September 2017

mplate. > > > > Mentors > > --- > > > > Mentors should review reports for their project(s) and sign them off on > > the Incubator wiki page. Signing off reports shows that you are > > following the project - projects that are not signed may raise alarms > > for the Incubator PMC. > > > > Incubator PMC > > -- Matteo Merli <mme...@apache.org>

[DISCUSS] PIP-6: Guaranteed Message Deduplication

I have added a new proposal to have guaranteed message de-duplication in Pulsar brokers. https://github.com/apache/incubator-pulsar/wiki/PIP-6:-Guaranteed-Message-Deduplication Matteo -- Matteo Merli <mme...@apache.org>

Re: [GitHub] merlimat commented on issue #742: Avoid huge backlog on topic reloading: due to large gap between markDelete-offset and read-position of cursor.

pped/alert generated and the the user fixes the > problem. In essence, deal with unacked messages as a first class user > resource limit, like backlog quota. > We could also do that once you reach the max number of "holes" the delivery stops. -- Matteo Merli <mme...@apache.org>

Re: [GitHub] merlimat commented on issue #742: Avoid huge backlog on topic reloading: due to large gap between markDelete-offset and read-position of cursor.

-- >> This is an automated message from the Apache Git Service. >> To respond to the message, please log on GitHub and use the >> URL above to go to the specific comment. >> >> For queries about this service, please contact Infrastructure at: >> us...@infra.apache.org >> >> >> With regards, >> Apache Git Services >> > > -- Matteo Merli <mme...@apache.org>

Re: [GitHub] merlimat commented on issue #742: Avoid huge backlog on topic reloading: due to large gap between markDelete-offset and read-position of cursor.

be big or small..) 2. Stop delivery after 1K holes 3. Have alerts that get triggered at 2/3 of the max number of "holes" so that user can be notified of abnormal acknowledging pattern Stopping delivery based on read position vs mark-delete position doesn't really address this problem. My personal preference would be to do 1 & 3. Same behavior as today with clear actionable metrics getting reported. -- Matteo Merli <mme...@apache.org>

Re: Next release of Pulsar 1.20

t; > > main feature additions that are completed/progressing for completion > for > > > the next release. > > > > > > Dispatch side throttling > > > End-to-end message encryption > > > Event-time & SequenceId for messages > > > C++ client support for Reader API > > > > > > > > > Let me know if this date seems unreasonable. > > > > > > Cheers. > > > Joe > > > > > > -- Matteo Merli <mme...@apache.org>

Re: Pulsar encryption, Bouncycastle and export license page

listed on the export license > page. Do we need to list it Pulsar on the export license page now? If so, > how do we get it into there? > > Or should we just remove the BouncyCastle jars from the distribution and > leave it optional, letting users install it if needed? Users will need > to install it for building Pulsar from source. They wont need it for > running Pulsar, unless they use encryption. > > What's the guidance on this? > > Cheers, > Joe > > > > -- Matteo Merli <mme...@apache.org>

Re: Pulsar encryption, Bouncycastle and export license page

export license page now? If > so, > > how do we get it into there? > > > > Or should we just remove the BouncyCastle jars from the distribution and > > leave it optional, letting users install it if needed? Users will > need > > to install it for buil

Re: Add EventTime to pulsar messages

't have any permissions on writing pulsar wiki pages, can > any pulsar committers help me add this PIP to the wiki pages if it is > accepted? > > - Sijie > -- Matteo Merli <mme...@apache.org>

Re: Add EventTime to pulsar messages

red by this proposal. > > > > Also there is another consideration - adding this field to message > metadata > > is more serialization friendly than putting it into key/value property. > > this is important for stream computing, > > because this field might be accessed when p

[DISCUSS] Log4J-2.x and defining acceptable breaking changes

of all the things that might be good to change in the APIs if we were to do a 2.0 release. I, for one, would vote to fix the MessageId in the C++ client lib to hide implementation and allow for further non-breaking changes. Please, everyone share you thoughts on this, Matteo -- Matteo Merli <

Re: [VOTE] Pulsar 1.20.0-incubating Release Candidate 0

lsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the README to build > and run the Pulsar standalone service. > > Joe > -- Matteo Merli <mme...@apache.org>

Re: [DISCUSS][VOTE] Pulsar 1.21.0-incubating Release Candidate 0

ke to get in. There's a PR on > yahoo/bookkeeper repo. Will update in few hours whether we can make it > through or skip. > > > Thank you for your notice. > > Please let me know when it has done. > > > Thanks, > > Nozomi > > >

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 2

ollow the README to build and > run the Pulsar standalone service. > > Thanks, > Nozomi > -- Matteo Merli <mme...@apache.org>

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 1

new candidate including them. > > > Thanks, > > Nozomi > > ____ > 差出人: Matteo Merli <mme...@apache.org> > 送信日時: 2017年11月30日 5:11:03 > 宛先: dev@pulsar.incubator.apache.org > 件名: Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 1 &

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 1

gfix. > > > Thanks, > > Nozomi > > ____ > 差出人: Matteo Merli <matteo.me...@gmail.com> > 送信日時: 2017年11月30日 9:47:54 > 宛先: dev@pulsar.incubator.apache.org > 件名: Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 1 > > Hi Nozomi, > > I've already merged t

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 1

Added one more PR with the removal of several RAT exclusions: https://github.com/apache/incubator-pulsar/pull/928 On Wed, Nov 29, 2017 at 10:41 AM Matteo Merli <mme...@apache.org> wrote: > Just submitted the PR https://github.com/apache/incubator-pulsar/pull/926 > > Please any

Re: [DISCUSS][VOTE] Pulsar 1.21.0-incubating Release Candidate 0

;> apache/incubator-pulsar< > https://github.com/apache/incubator-pulsar/milestone/10?closed=1> > >>> github.com > >>> incubator-pulsar - Pulsar - distributed pub-sub messaging system > >>> > >>> > >>> > >>> > >>> *** Please download, test and vote by November 13th 2017, 16:00 GMT. > >>> > >>> Note that we are voting upon the source (tag), binaries are provided > for > >>> convenience. > >>> > >>> Source and binary files: > >>> > https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-1.21.0-incubating-candidate-0/ > >>> > >>> Maven staging repo: > >>> > https://repository.apache.org/content/repositories/orgapachepulsar-1002/ > >>> > >>> The tag to be voted upon: > >>> v1.21.0-incubating-candidate-0 > (c9b6b5bde6ff29308d3c5b7fe292daa6346624df) > >>> > >>> Pulsar's KEYS file containing PGP keys we use to sign the release: > >>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > >>> > >>> Please download the the source package, and follow the README to build > >>> and run the Pulsar standalone service. > >>> > >>> > >>> Thanks, > >>> Nozomi > >> > > -- Matteo Merli <mme...@apache.org>

Re: Design Question About Client Limits

the limit on the number of simultaneously open topic producers on > a client node? > > Regards, > Dave > -- Matteo Merli <mme...@apache.org>

Pulsar talks at meetup next week

/BigDataApps/events/243529551 Workshop on Saturday 11/11 9:30am in Santa Clara https://www.meetup.com/datariders/events/243704410/ Matteo -- Matteo Merli <mme...@apache.org>

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 2

gt;>>>> https://github.com/apache/incubator-pulsar/milestone/10?closed=1 > >>>>> > >>>>> *** Please download, test and vote by December 5th 2017, 10:00 GMT. > >>>>> > >>>>> Note that we are voting upon the source (tag), binaries are provided > >>>>> for convenience. > >>>>> > >>>>> Source and binary files: > >>>>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/ > >>>>> pulsar-1.21.0-incubating-candidate-2/ > >>>>> > >>>>> Maven staging repo: > >>>>> > >>> https://repository.apache.org/content/repositories/orgapachepulsar-1 > >>>>> 004/ > >>>>> > >>>>> The tag to be voted upon: > >>>>> v1.21.0-incubating-candidate-2 (be96bd38b1f97b1b0888565196d774 > >>>> 19004abe88) > >>>>> https://github.com/apache/incubator-pulsar/releases/tag/ > >>>>> v1.21.0-incubating-candidate-2 > >>>>> > >>>>> Pulsar's KEYS file containing PGP keys we use to sign the release: > >>>>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > >>>>> > >>>>> Please download the the source package, and follow the README to > >>>>> build > >>>> and > >>>>> run the Pulsar standalone service. > >>>>> > >>>>> Thanks, > >>>>> Nozomi > >>>>> > >>>> > > -- Matteo Merli <mme...@apache.org>

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 2

netty/netty/3.10.1.Final/netty-3.10.1.Final.jar > > The discussion was a PM on slack. I wanted to confirm it wasn't a > known issue/configuration thing before going to list. > > -Ivan > > > On Tue, Dec 5, 2017 at 9:19 PM, Matteo Merli <mme...@apache.org> wrote: > > Confirm

Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

s://github.com/apache/incubator-pulsar/releases/tag/v1.21.0-incubating-candidate-3 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the READ

Fwd: Podling Report Reminder - December 2017

gt; > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that y

[DRAFT] Podling report

. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2017-10-13, 1.20.0-incubating When were the last committers or PPMC members elected? -- Matteo Merli <mme...@apache.org>

Re: [DRAFT] Podling report

Thanks, I have updated the wiki at https://wiki.apache.org/incubator/December2017 On Wed, Dec 6, 2017 at 10:33 AM Rajan Dhabalia <rdhaba...@apache.org> wrote: > Looks good. > > Thanks, > Rajan > > On Wed, Dec 6, 2017 at 10:10 AM, Matteo Merli <mme...@apache.org> w

Re: Embedded pulsar cluster?

ka to > > https://github.com/apache/kafka/blob/trunk/streams/src/test/java/org/apache/kafka/streams/integration/utils/EmbeddedKafkaCluster.java > > I'd like to play with pulsar by replacing our kafka stream app with it. > > -- > -jun > -- Matteo Merli <mme...@apache.org>

[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

the Pulsar standalone service. -- Matteo Merli <mme...@apache.org>

[CANCELED] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

source release [1] > - All source files have headers > > Thanks, > Justin > > > 1. pulsar-functions/utils/src/test/resources/multifunction.jar > --------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > -- Matteo Merli <mme...@apache.org>

[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4

the Pulsar standalone service. -- Matteo Merli <mme...@apache.org>

Planning for Pulsar 2.1 release

framework (with S3 as first supported backend) * Schema integration for unctions * Distributed state in functions * Avro schema support * Improvements in pulsar-admin cli tool The idea would be to have a 2.1 release in early June. What are the thoughts around this? Matteo -- Matteo Merli <

Pulsar Go client library

of best practices :) Ultimately, the library and the API needs to make sense and feel natural to Go developers. Matteo -- Matteo Merli <mme...@apache.org>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

Unexpected jar in source release [1] > > - All source files have headers > > > > Thanks, > > Justin > > > > > > 1. pulsar-functions/utils/src/test/resources/multifunction.jar > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- > Matt Sicker <boa...@gmail.com> > -- Matteo Merli <mme...@apache.org>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 2

sercontent.com/ivankelly/a93f06d2a3075575c43a0dd44165bac1/raw/83551daf958432f532ee53cccaa6397f0c1af7bf/pulsar-libs.org > > Some stuff is missing completely. Others are incomplete. > > Note that this only applies to the binary distribution. The source is > fine in this regard. > -- Matteo Merli <mme...@apache.org>

[CANCELED] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 2

Canceling vote to include license and notice fixes. On Tue, May 8, 2018 at 9:56 AM Matteo Merli <matteo.me...@gmail.com> wrote: > Thanks for checking thouroughly. > > Created PR at https://github.com/apache/incubator-pulsar/pull/1748 > > In some cases, the feedback for the

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 2

e, which netty integrates into its code, but which > is MIT/BSD license. These should be notes in the LICENSE. > See > https://github.com/apache/bookkeeper/blob/master/bookkeeper-dist/src/main/resources/LICENSE-all.bin.txt#L368-L416 > > -Ivan > -- Matteo Merli <mme...@apache.org>

[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 5

: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli <mme...@apache.org>

Re: [VOTE][DISCUSS] Pulsar Release 2.0.0-rc1-incubating Candidate 4

he plan for 2.1? > > Regards, > Dave > > > > On May 14, 2018, at 4:33 PM, Matteo Merli <mme...@apache.org> wrote: > > > > This is the fourth release candidate for Apache Pulsar, version > > 2.0.0-rc1-incubating. > > > > It fixes the following is

Re: [CANCELED] Pulsar Release 2.0.1-incubating Candidate 1

> commit d77833a479f203af3eeba3f2c97aefb8f818fcea > Author: massakam > Date: Fri Jun 8 01:02:12 2018 +0900 > -- > commit 54eb8a54ef9d5d527e9aa663de117c2fa93ea9a3 > Author: Matteo Merli > Date: Mon Jun 4 15:12:56 2018 -0700 > --

[VOTE] Pulsar Release 2.0.1-incubating Candidate 2

o sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli

Re: [DRAFT] Pulsar Podling report June 2018

> -Taylor > > > On Jun 7, 2018, at 1:03 AM, Matteo Merli wrote: > > > > Hi Taylor, > > > > The draft was obviously written before the issues were raised on the > > private list. I have already replied on the private@ list on the > specific > &

Planning for release 2.1

you want to include in 2.1. Also, is anyone volunteering as release manager for 2.1? Matteo -- Matteo Merli

Re: Pulsar meetup in June/July

t; > > In June, it going to be a year since Pulsar was accepted into the > > > > incubator. > > > > > > > > > > I'm thinking of a meetup, with a few in-depth talks/presentations, > > > what's > > > > > new in Pulsar 2.0 etc, from Pulsar users and developers. Are > > people > > > > > interested in a 1/2day event? I can arrange for the venue and > > > > logistics. > > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > -- Matteo Merli

  1   2   >