GitHub user michaeljmarshall added a comment to the discussion: Test /
Experiment Batching locally
> How do I confirm the messages are batched ?
There are a few details here. First, message batching is an internal pulsar
optimization that is transparent to the producer and consumer, so it
GitHub user michaeljmarshall added a comment to the discussion: Test /
Experiment Batching locally
Thank you for this sample code. The first thing to note is that using
synchronous sends by calling `.send()` will likely not result in batched
messages because the `send()` call returns only
GitHub user Shalima added a comment to the discussion: Test / Experiment
Batching locally
Producer.
```
Producer producer = client.newProducer().topic(topicName).create();
log.info("Created producer: " + topicName);
for (int i = 0; i < numMsgs; i++) {
+1 (binding) to the overall proposal. I also agree with the
clarifications/requests raised by Tison and Lari. I prefer the
abbreviated prefixes, and I think using a GitHub Action to enforce the
formatting would guarantee that the formatting is correct. For
example, when I review PRs and merge
GitHub user michaeljmarshall added a comment to the discussion: Test /
Experiment Batching locally
Hi @Shalima, would you mind sharing a sample of your producer and consumer
code? That will likely be an efficient way to help answer your question. Thanks.
GitHub link:
+1 - thanks for a great write up Matteo, it looks like it'll be a
great improvement!
(Sorry for casting a late vote, but I figure it's worth affirming the
PIP even if we've already closed the vote.)
Thanks,
Michael
On Sun, Jul 24, 2022 at 9:32 PM Matteo Merli wrote:
>
> Closing this vote with
casuallc commented on issue #38:
URL: https://github.com/apache/pulsar-adapters/issues/38#issuecomment-1210083991
#37
--
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
Hi,
Not sure if this is too late or not, I replied in the discussion thread
about some thinking.
Whether we tweak the sink connector or we allow a flexible and general
function creation.
On Mon, Aug 1, 2022 at 5:03 PM mattison chao
wrote:
> +1 (non-binding)
>
> Best,
> Mattison
>
> On Tue, 2
GitHub user Shalima created a discussion: Test / Experiment Batching locally
Hi,
I am trying to experiment with batching parameters in Producer configuration
locally. Since batching is enabled by default, I tried to set maxMessages to 3.
I have a consumer listening to the topic. I am using
To my understanding, the Pulsar IO Connectors (i.e. Sources/Sinks) are
quite self-contained. They move data around.
If we want to enable functionality described inside the PIP (process ->
write to otherplace), can we think in another way -- allow flexible
configuring of a Pulsar Function?
Details in https://github.com/apache/pulsar/issues/17024 . Appreciate if any
Pulsar experts could spare some pointers.
Best regards,
Raven
- -
Raven TanMEng (Hons)
Software Development
Research Engineer
FootfallCam
51-2, Jalan SL 1/4, Bandar Sg Long,
43000 Kajang, Malaysia
Website:
A good example is Apache SkyWalking who has less than 100 issues. If we
reach similar status, we don't have to worry about stale bot at all and
even simply remove it - our committers should be able to handle such
traffic.
Best,
tison.
tison 于2022年8月9日周二 23:18写道：
> After a discussion with
After a discussion with @codelipenghui we agree that spending time on
handling issues is better than writing more automation or rules.
One thing to help us handle the backlog is close stale issues directly as
not planned[1]. As committers can be confident close stale issues, we can
significantly
+1 (non-binding)
Thanks,
Xiaoyu Hou
Yu 于2022年8月4日周四 16:13写道：
> Hi team,
>
> It has been 4 months since we discussed the [Guideline] Pulsar PR Naming
> Convention [1].
>
> Nowadays, when reading the PR list [2], you’ll find more and more people
> follow and get used to this rule.
>
> It
+1
Regards
Jiwei Guo (Tboy)
On Tue, Aug 9, 2022 at 3:12 PM Qiang Huang
wrote:
> +1 (non-binding)
>
> Kai Wang 于2022年8月5日周五 10:18写道：
>
> > +1 (non-binding)
> >
> > Thanks,
> > Kai
> >
> > Heesung Sohn 于2022年8月2日周二
> 08:50写道：
> >
> > > Dear Pulsar Community,
> > >
> > > Please review and vote
casuallc opened a new issue, #38:
URL: https://github.com/apache/pulsar-adapters/issues/38
**Reproduce**
- create non-paritioned topic
- send message to this topic
**error**
+1, with some conditions about the details of PIP 198 that are listed below:
Would it be possible to improve the proposal in a way that the valid prefixes
for type and component are in a file in the repository and the possible checker
would use this file as the source of truth? Tison already
Hi Yu,
To be clear, the candidates of types and components are a bit long which
may waste space for meaningful information.
For example, Angular names feature as feat to save letters. GitHub only
shows the first 50 characters for PR title.
I'd like to confirm that the name of types and
+1 (non-binding)
Thanks,
Zixuan
Qiang Huang 于2022年8月9日周二 15:12写道：
> +1 (non-binding)
>
> Kai Wang 于2022年8月5日周五 10:18写道：
>
> > +1 (non-binding)
> >
> > Thanks,
> > Kai
> >
> > Heesung Sohn 于2022年8月2日周二
> 08:50写道：
> >
> > > Dear Pulsar Community,
> > >
> > > Please review and vote on this PIP.
Hi Michael,
Thank you for bringing up this topic.
I was just running into an issue that prevented me from using the standard
Pulsar image in Testcontainers and found this discussion.
In my opinion, refactoring the docker builds to allow us to use the ASF
infra is a great idea.
I'm also looping
+1 (non-binding)
Kai Wang 于2022年8月5日周五 10:18写道：
> +1 (non-binding)
>
> Thanks,
> Kai
>
> Heesung Sohn 于2022年8月2日周二 08:50写道：
>
> > Dear Pulsar Community,
> >
> > Please review and vote on this PIP.
> >
> > PIP link: https://github.com/apache/pulsar/issues/16691
> >
> > Thank you,
> > -Heesung
>
urfreespace merged PR #159:
URL: https://github.com/apache/pulsar-site/pull/159
--
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:
+1 (non-binding) I like the idea of check PR title as a job.
Good job, Yu.
tison 于2022年8月8日周一 22:07写道：
> +1 (non-binding) to the proposal itself.
>
> Although, we should later move the standard to our website where the whole
> project can easily contribute to and follow the general contribution
23 matches
Mail list logo
