GitHub user raunakagrawal47 edited a discussion: Not able to run pulsar
function locally
I have tried everything to package and run my python function locally.
I tried to run the pulsar standalone on my laptop (v. 2.9.1) as well as tried
to run pulsar in docker (latest image).
Here is the re
GitHub user raunakagrawal47 edited a discussion: Not able to run pulsar
function locally
I have tried everything to package and run my python function locally.
I tried to run the pulsar standalone on my laptop (v. 2.9.1) as well as tried
to run pulsar in docker (latest image).
Here is the re
+1
Thanks,
Mattison
On Sat, 19 Nov 2022 at 15:07, Michael Marshall wrote:
> I agree with removing these labels.
>
> Thanks,
> Michael
>
> On Thu, Nov 17, 2022 at 9:29 PM Yunze Xu
> wrote:
> >
> > +1
> >
> > Thanks,
> > Yunze
> >
> > On Fri, Nov 18, 2022 at 3:12 AM Enrico Olivelli
> wrote:
> >
+1
Best,
Xiaoyu Hou
tison 于2022年11月17日周四 23:32写道：
> Hi,
>
> When squashing issue backlog, I noticed there're a number of "legacy" tags
> in series "traige/week-x".
>
> It seems the initiative has been halted and those labels don't provide
> continuous value. Thus I suggest we remove "triage" se
FYI - these labels are removed now.
FWIW, I'm doing this with GitHub CLI:
for i in {1..53}; do
gh label delete "triage/week-$i" --confirm
done
Best,
tison.
houxiaoyu 于2022年11月21日周一 09:22写道：
> +1
>
> Best,
> Xiaoyu Hou
>
> tison 于2022年11月17日周四 23:32写道：
>
> > Hi,
> >
> > When squashing issu
Thanks for taking care of labels!
Sent from my iPhone
> On Nov 20, 2022, at 5:25 PM, tison wrote:
>
> FYI - these labels are removed now.
>
> FWIW, I'm doing this with GitHub CLI:
>
> for i in {1..53}; do
> gh label delete "triage/week-$i" --confirm
> done
>
> Best,
> tison.
>
>
> houxia
Hi, Devin
Thanks for raising the great discussion. It looks like the salient point is
that Pulsar
doesn't support native JSON schema. Instead, the schema is defined in the
Avro
standard but serialized to JSON format.JSON Schema combines aspects of
type-based and rule-based. As this article[1] said
GitHub user Raunak-Agrawal added a comment to the discussion: Not able to run
pulsar function locally
@Jason918 can you please help with this?
GitHub link:
https://github.com/apache/pulsar/discussions/18552#discussioncomment-4191516
This is an automatically sent email for dev@pulsar.apa
The Project Management Committee (PMC) for Apache Pulsar has invited
Cong Zhao (https://github.com/coderzc)
to become a committer and we are pleased to announce that he has accepted.
Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission
Congrats! Cong
Best,
Xiaoyu Hou
Haiting Jiang 于2022年11月21日周一 12:10写道：
> The Project Management Committee (PMC) for Apache Pulsar has invited
> Cong Zhao (https://github.com/coderzc)
> to become a committer and we are pleased to announce that he has accepted.
>
> Being a committer enables easier
Congrats! Cong
Best Regards,
Zixuan
houxiaoyu 于2022年11月21日周一 12:24写道：
> Congrats! Cong
>
> Best,
> Xiaoyu Hou
>
> Haiting Jiang 于2022年11月21日周一 12:10写道：
>
> > The Project Management Committee (PMC) for Apache Pulsar has invited
> > Cong Zhao (https://github.com/coderzc)
> > to become a committe
Hi -
Is it possible to identify PRs and issues from people who are new to Pulsar? If
so then it might be good to maintain labels.
Knowing and helping new contributors to pulsar benefits us all.
Regards,
Dave
Sent from my iPhone
Hi Dave,
Interesting. I found @labuladong's related proposal[1] days before.
There can be two ways to identify such contributions:
1. Running CI tasks to label them when a new issue/PR is opened. Existing
actions[2] provide the functionality to comment but we can easily extend it
to label.
2. Pe
Hi,
Dave's email about first-time contributions reminds me of the idea to
acknowledge contributors for each release.
Let's see how the Flink community does it:
For each release blog, e.g. [1], in the last section "List of Contributors",
explicitly list out contributors and acknowledge their cont
14 matches
Mail list logo
