t; On Wed, Dec 15, 2021 at 1:05 PM Michael Marshall
> wrote:
> >
> > I am +1 for closing PRs that are over a year old.
> >
> > Does anyone else in the community have thoughts on these old PRs?
> > Getting consensus and creating a process here could help make our
> > c
merge.
Recent example from Cassandra where reviewer Joey Lynch asked contributor
NV Harikrishna to do this:
https://issues.apache.org/jira/browse/CASSANDRA-14898
On Wed, Dec 15, 2021 at 3:21 PM Enrico Olivelli wrote:
> Jonathan,
>
> Il Mer 15 Dic 2021, 21:11 Jonathan Ellis ha scritto:
>
y miss
> important bug fixes that would improve dot release stability.
>
> I propose that we try to use pattern 1 (or something close to it) for
> our process.
>
> Thanks,
> Michael
>
> [0] https://github.com/apache/pulsar/wiki/Committer-Guide
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
er example [1]. I closed this one because it had merge
> >> conflicts with a commit that fixed the same underlying issue.
> >>
> >> Note that our committer guidelines [2] do not provide guidance on this
> >> subject.
> >>
> >> [0] - https://github.com/apache/pulsar/pull/11237
> >> [1] - https://github.com/apache/pulsar/pull/11162
> >> [2] - https://github.com/apache/pulsar/wiki/Committer-Guide
> >>
> >> Thanks,
> >> Michael
> >>
>
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
g the list of 300 PRs, it is a
> huge task.
>
> There is already much more work to do to get 2.9.0 completely released (and
> also PulsarAdapters) and we have to cut 2.9.1 as soon as possible due to a
> bad regression found in 2.9.0.
>
> Thanks
> Enrico
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
; > * Ensure ASF compliance
> >> > * Launch
> >> >
> >> > Design concepts here:
> >> > https://projects.invisionapp.com/freehand/document/jY5pEt6jQ?
> >> >
> >> > Please make your selection here by Sept. 15:
> >> > https://constantialabs.typeform.com/to/AJbOYCp3
> >> >
> >> > Any questions, just let me know. Thanks!
> >> >
> >> > Melissa Logan
> >> >
> >> > (1)
> >> >
> >> >
>
> https://lists.apache.org/thread.html/ra618c666d52f518741f64313969a9f16f20b8f06cd444f499f77cd93%40%3Cdev.pulsar.apache.org%3E
> >> >
> >
> >
> >
> > --
> > Melissa Logan (she/her)
> > Principal, Constantia.io
> > meli...@constantia.io
> > Cell: 503-317-8498
> > LinkedIn | Twitter
> >
>
>
> --
> Melissa Logan (she/her)
> Principal, Constantia.io
> meli...@constantia.io
> Cell: 503-317-8498
> LinkedIn | Twitter
>
>
>
> --
> Melissa Logan (she/her)
> Principal, Constantia.io
> meli...@constantia.io
> Cell: 503-317-8498
> LinkedIn | Twitter
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
Is this something that is interesting and useful to the
> >broader community?
> >2.
> >
> > More broadly, what policy do we want to establish for Pulsar protocol
> >handlers and other compatibility layers? As indicated above, I think
> that
> >we should provide Pulsar with “batteries included” to make it as easy
> as
> >possible for new users to get started.
> >
> >
> > Best regards.
> >
> > Christophe
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
> > > JDK11+ so that we can start using newer Java features in the Pulsar
> code
> > > base?
> > I think this is using jdk11+ for the build and the broker should be fine.
> > The client, and modules depended on by the client may be a different
> story.
> > Pe
all the k8s users that use ASF
> Pulsar Docker images run on JDK11
>
> We should ensure that Pulsar runs and builds well on JDK17 but currently
> there is no ongoing effort in the community
>
> Cheers
> Enrico
>
> Il giorno mar 31 ago 2021 alle ore 15:22 Jonathan Ellis >
ar:9.4.42.v20210604:compile
> [INFO] | | | \-
> org.eclipse.jetty:jetty-alpn-java-client:jar:9.4.42.v20210604:compile
>
> In order to solve this issue, I will use JDK11 to release Apache Pulsar
> 2.8.1 instead of JDK8. JDK11 is compatible with JDK8, and the release
> target i
Moving back to dev.
Since it seems like there's some confusion on this point, it's perfectly
normal for PMC discussions around new proposals with decision-making
authority by the PMC to take place on the public dev list. The private
list is only necessary when confidentiality is required, and the
lla is a good idea (or something that the ASF would be ok
> with).
>
> Finally, I find it a bit preposterous to now make it a proposal to the
> community, only after the above points were raised.
>
> Matteo
>
>
> --
> Matteo Merli
>
>
> On Wed, Aug 18, 2021 a
Hi all,
Meetups are an important part of community building and knowledge sharing
for open source projects like Apache Pulsar. At the same time, the work of
recruiting speakers and organizing sponsors [1] is both time consuming and
not core to project governance.
I propose that the PMC designate
apache.org/release-notes
>
> We would like to thank the contributors that made the release possible.
>
> Regards,
>
> The Pulsar Team
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
Update: We discussed this on today's contributor call -- consensus was that
this patch can go in if it can be rebased and merged before #10878 and RC3
is rolled.
On Thu, Jun 10, 2021 at 10:31 AM Jonathan Ellis wrote:
> Hi Sijie,
>
> This patch and the initial review was comple
"Code Freeze" in the time-based release plan.
>
> I think we should stick to this plan. Otherwise, everyone would try to
> include features for different requirements.
>
> - Sijie
>
> On Thu, Jun 10, 2021 at 7:32 AM Jonathan Ellis wrote:
>
> > As a heads up fo
s://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
Do we have consensus on metadata repo + generated docs page to start with?
On Sat, May 29, 2021 at 8:44 AM Jonathan Ellis wrote:
> On Fri, May 28, 2021 at 2:55 PM Sijie Guo wrote:
>
>> An alternative is to just add a table to the connectors documentation page
>> like how
On Fri, May 28, 2021 at 2:55 PM Sijie Guo wrote:
> An alternative is to just add a table to the connectors documentation page
> like how we add third-party clients.
> http://pulsar.apache.org/docs/en/client-libraries/#third-party-clients
>
> It only refers to the Github repos for those connectors
ppy to volunteer to help with any housekeeping
needed for this proposal that the PMC would like to delegate, from creating
a git repo to adding a script to the site builder to turn that into a page
to approving PRs that people submit.
On Thu, May 27, 2021 at 3:46 PM Sijie Guo wrote:
> On Th
On Thu, May 27, 2021 at 2:38 PM Sijie Guo wrote:
> Agreed that the main problem is about discovering the existing pre-built
> Pulsar connectors. I don't think the PMC should involve hosting and
> managing external connectors because it will put the PMC in the situation
> in handling licensing iss
> > > validated if the algorithm of the presented token is set to "none".
> > > This allows an attacker to connect to Pulsar instances as any user
> > > (incl. admins).
> > >
> > > Mitigation:
> > > Users of the affected versions should apply one of the following
> > > mitigations:
> > > Upgrade to Apache Pulsar 2.7.1 or later
> > >
> > > Credit:
> > > This issue was identified by Peter Stöckli
> > >
> >
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
On Wed, May 26, 2021 at 10:45 AM Andrey Yegorov
wrote:
> My notes from the community meeting. Jerry, Matteo, and I talked about this
> idea:
>
Thanks for the proposal and the notes, Andrey! I think a connector
registry will be very useful as Pulsar adoption grows.
* major problems are:
> --
ists, but I
> >> don't
> >> > > see
> >> > > > > one. For reference, the `PatternMultiTopicsConsumerImpl`
> currently
> >> > > polls
> >> > > > > for all topics in a namespace and then does set operations to
> >> compute
> >> > > the
> >> > > > > "new" topics to which it should subscribe. This client
> >> implementation
> >> > > > could
> >> > > > > possibly leverage the new feature.
> >> > > > >
> >> > > > > There are still details I need to work out, like how it will
> work
> >> for
> >> > > > > partitioned vs unpartitioned topics and what kind of guarantees
> we
> >> > have
> >> > > > > regarding messaging semantics (I think we'll want at least once
> >> > message
> >> > > > > delivery here). I plan to include these details in the PIP with
> >> > > > discussions
> >> > > > > about trade offs for different implementations.
> >> > > > >
> >> > > > > Does this feature sound helpful and reasonable to others? If so,
> >> is
> >> > the
> >> > > > > next step to formally write a proposal in a Google Doc or to put
> >> > > > together a
> >> > > > > doc on the Pulsar GitHub Wiki?
> >> > > > >
> >> > > > > Related and/or future work to consider in this design: I can see
> >> > adding
> >> > > > > different system topics for these types of auditable system
> >> events.
> >> > We
> >> > > > > currently rely on log lines as our primary way for end users to
> >> audit
> >> > > > > system events, e.g. a producer connecting to a broker or a
> >> > subscription
> >> > > > > getting created, but we could instead have topics that represent
> >> > > streams
> >> > > > of
> >> > > > > these different kinds of events. A persistent topic could make
> >> these
> >> > > > audit
> >> > > > > events more durable and more structured which should lend
> >> themselves
> >> > to
> >> > > > > being more easily analyzed. Further, users could choose to turn
> >> > on/off
> >> > > > > these audit events, perhaps at the broker or namespace level, to
> >> fit
> >> > > > their
> >> > > > > own needs.
> >> > > > >
> >> > > > > Let me know what you think and how I should proceed.
> >> > > > >
> >> > > > > Regards,
> >> > > > > Michael Marshall
> >> > > >
> >> > >
> >> >
> >>
> >
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
rTopicByCustomTopicName(org.apache.pulsar.client.api.DeadLetterTopicTest)
> Time elapsed: 6.152 s <<< FAILURE!
> java.lang.AssertionError: expected [null] but found
> [org.apache.pulsar.client.impl.MessageImpl@7feabb64]
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
finally want to create a PR to apache/pulsar, it can be started
> from the command line (this will open a browser for filling in the PR
> details):
>
> gh pr create --repo=apache/pulsar --base master --head your-pr-branch --web
>
>
> I hope this helps in getting started with your personal Pulsar CI so that
> you can help reduce the load on actual Pulsar CI.
>
> Please continue sending a lot of PRs! :)
>
> BR, Lari
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
n via
> https://apache-pulsar.slack.com/archives/C01PGBZLGPN.
>
> If you need any help, feel free to reach out to me! I can help you with
> that.
>
>
> - Sijie
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
be
> > > > > > hiding other, more important logs.
> > > > > >
> > > > > > Does anyone know the reasoning for this level of detailed INFO
> > > logging
> > > > > from
> > > > > > this class? I can see that these logs have been in the class for
> > > over 4
> > > > > > years, but given that pulsar is supposed to scale to a million
> > topics
> > > > and
> > > > > > each producer/consumer needs its own connection to a broker, I
> > > wouldn't
> > > > > > expect this level of logging. If the community is open to it, I'd
> > be
> > > > > happy
> > > > > > to submit a PR demonstrating the logs that I'd like to switch
> from
> > > INFO
> > > > > to
> > > > > > DEBUG level.
> > > > > >
> > > > > > I recognize that it's possible to filter the logs for just that
> > > class,
> > > > > but
> > > > > > I also think it's possible that most users running pulsar don't
> > need
> > > > this
> > > > > > level of detailed logging about connections to brokers, which is
> > why
> > > I
> > > > > > wanted to start this discussion on the mailing list.
> > > > > >
> > > > > > It's relevant to note that the coding guide on the website (
> > > > > > https://pulsar.apache.org/en/coding-guide/#logging-levels)
> > mentions
> > > > the
> > > > > > following about logging:
> > > > > > "INFO is the level you should assume the software will be run in.
> > > INFO
> > > > > > messages are things which are not bad but which the user will
> > > > definitely
> > > > > > want to know about every time they occur."
> > > > > >
> > > > > > Personally, I don't "definitely want to know" a producer's or
> > > > consumer's
> > > > > > connection status "every time" it changes.
> > > > > >
> > > > > > Thanks!
> > > > > > Michael Marshall
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
On Sun, Feb 14, 2021 at 10:51 PM Sijie Guo wrote:
> Not sure about renaming the blog to announcements. Let's first leave the
> blog part unchanged and focus on the documentation site enhancement.
>
This isn't a big deal, but I don't see the downside to renaming it to
something that better reflec
her wrote:
> Inline
>
> Sent from my iPhone
>
> > On Feb 12, 2021, at 9:36 AM, Jonathan Ellis wrote:
> >
> >
> > To make a specific proposal, I've attached a mockup of what a
> streamlined home page would look like.
> >
> > Commentary:
&g
On Feb 12, 2021, at 9:36 AM, Jonathan Ellis wrote:
> >
> >
> > To make a specific proposal, I've attached a mockup of what a
> streamlined home page would look like.
> >
> > Commentary:
> > - Introduction and Quickstart will follow Kafka’s mod
happy to contribute as a technical writer as well.
>
> I think we have all the contributors we need listed here in this thread to
> make this happen quickly once it is approved.
>
> Thanks!
>
> > On Feb 10, 2021, at 9:24 AM, Jonathan Ellis wrote:
> >
> > I
rk we are using. If there is a way to improve this, that would be
> great.
>
> - Sijie
>
>
> On Tue, Feb 9, 2021 at 3:02 PM Jonathan Ellis wrote:
>
> > You're right, Kafka does a really good job here. Here's a proposal along
> > those lines:
> >
&g
e at the end
> of the day.
>
> My two cents would be to build out the Resources section to have unique
> content on pulsar.apache.org <http://pulsar.apache.org/> and have it take
> a 'Getting Started' approach.
>
> > On Feb 9, 2021, at 1:13 PM, Jonathan Ellis wro
e to go digging for that information elsewhere, we’ve already
> lost
> > the attention span of a significant number of potential users and
> > contributors.
> >
> > What does the rest of the community think about this?
> >
> > [1] https://github.com/apache
tial users and
contributors.
What does the rest of the community think about this?
[1] https://github.com/apache/pulsar/pull/9463
On Fri, Feb 5, 2021 at 1:06 PM Jonathan Ellis wrote:
>
>
>
>
>
>
> *I thank Sijie for the comment on my pull request [1]. I’m following up
>
sar/pull/9463>*
On Wed, Feb 3, 2021 at 5:18 PM Jonathan Ellis wrote:
> Hi all,
>
> I'd love to see more content on the Apache Pulsar blog showing how much
> traction this project and community have gotten recently. To that end,
> I've started collecting quick &
to getting more finished up!
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
; > - 2/2 (Tuesday): 4 PM - 5 PM PST / 8 AM - 9 AM China Time
> > - 2/4 (Thursday): 8 AM - 9 AM PST / 5 PM - 6 PM CET
> >
> > You can always find the meeting minutes & recordings on this wiki page:
> > https://github.com/apache/pulsar/wiki/Community-Meetings
> >
> > Looking forward to the first meeting!
> >
> > - Sijie
> >
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
> >>> make decisions.
> >>>
> >>> The Pulsar community is distributed all over the world, we have people
> >>> from
> >>> China, the US, Europe, it will be hard to find a good time for
> everyone.
> >>> I suggest for the first meeting to meet at 8:30 PST
> >>>
> >>> For reference, this is the link to the "minutes" of the Community
> >>> Meetings
> >>> in BK,
> >>> Sijie and Matteo will remember those days
> >>>
> https://cwiki.apache.org/confluence/display/BOOKKEEPER/Community+Meetings
> >>>
> >>>
> >>> Enrico
> >>>
> >>
>
--
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced
40 matches
Mail list logo
