Re: Pulsar Server on JDK11 - initial discussion

[Renkai Ge]

LGTM if I don’t understand wrong.

The key point is to build docker image in Java 11 so that new Pulsar users can 
start with Java 11 easier, but existing users can still have freedom to choose 
Java 8 or 11 as they wish.

> 2021年2月9日 下午5:41，Enrico Olivelli  写道：
> 
> Yunze,
> It's not exactly as you write.
> 
> We will be building and testing on JDK11.
> 
> Binaries, both server and client, will be able to run on jdk8
> 
> Building on jdk11 targeting jdk8 does not bring much benefit as you cannot
> use jdk11 features and also the byte code will look like the jdk8 version
> (for instance no NestMates)
> 
> Currently Pulsar 2.6 and Pulsar 2.7 run well on jdk11
> 
> 
> But is the first step towards moving to jdk11 as primary jdk
> 
> I hope that helps
> Enrico
> 
> Il Mar 9 Feb 2021, 10:18 Yunze Xu  ha scritto:
> 
>> LGTM if I don’t understand wrong.
>> 
>> In short, there’re two key points:
>> 
>> 1. Keep the code compatible with Java 8.
>> 2. Release the binaries that are built on JDK 11 to get the benefit.
>> 
>> So Java 8 users can still build Pulsar with JDK 8 but the default releases
>> are built on JDK 11.
>> 
>> - Yunze
>> 
>> 

Re: [PIP-78] Reduce redundant producers from partitioned producer

[Yuri Mizushima]

Sijie,

> If the lazy-loading approach sounds attractive to you and you like it,
> maybe the next step is to update the PIP, what do you think?

I think so too. I will update the PIP after discussing the authn/authz issue.

Regards,
-- 
Yuri Mizushima
yumiz...@yahoo-corp.jp
 

"Sijie Guo"  wrote:

Hi Yuri,

Regarding the authn/authz issue, @Matteo Merli  can
probably chime in more about that part.

If the lazy-loading approach sounds attractive to you and you like it,
maybe the next step is to update the PIP, what do you think?

- Sijie

On Mon, Feb 8, 2021 at 6:57 PM Yuri Mizushima 
wrote:

> Michael,
>
> Thank you for your comment!
>
> > Which Pulsar Clients will benefit from this proposal?
> I think that this proposal will be useful to any clients.
> In my schedule, if this proposal is accepted then I will implement this
> feature to Java client.
> If needed, then implement same feature to other clients such as C++, Go,
> etc.
>
> Regards,
> --
> Yuri Mizushima
> yumiz...@yahoo-corp.jp
>
>
> "Michael Marshall"  wrote:
>
> Hi Yuri and Sijie,
>
> I definitely like the idea of lazily creating producers as well as
> introducing a way to provide custom routing logic.
>
> Which Pulsar Clients will benefit from this proposal? I’d love to see
> this feature in the go client.
>
> Thanks,
> Michael Marshall
>
> > On Feb 7, 2021, at 9:53 PM, Yuri Mizushima 
> wrote:
> >
> > Sijie,
> >
> > Thank you for sharing!
> >
> > First, I considered your suggestion.
> > I think these implementations sound good.
> >
> > I think we should consider the State of partitioned producer: Ready,
> Connecting, etc.
> > Currently, partitioned producer gets "Ready" only when all producers
> connect to Broker correctly.
> >
> 
https://github.com/apache/pulsar/blob/fa41d02bebfd841767846240f3ae574047f118f0/pulsar-client/src/main/java/org/apache/pulsar/client/impl/PartitionedProducerImpl.java#L146
> > It seems that we should change meaning of state (or change handling)
> if we introduce the lazy-load feature.
> > To guarantee the message ordering (e.g. using partitionKey),
> partitioned producer should stop (or don't send messages to be routed to
> unavailable partition) when producer can't connect to one of partition.
> >
> > Secondly, I considered Matteo's comments.
> > I couldn't understand well about issue of authn/authz. Please tell
> me more detail.
> >
> > I wrote "connection" as number of producers which connect to broker.
> Also, TCP connections between partitioned producer and broker will be less
> than or equal to current in some cases. I'll show a case below.
> >
> > Suppose
> > * cluster has Broker0, 1, 2
> > * partitioned topic has 5 partitions
> > * limit conf is 3 partitions
> > * loadbalance partitions as below
> > - Broker0: partition-0, partition-1
> > - Broker1: partition-2
> > - Broker2: partition-3, partition-4
> >
> > Currently, client will create 3 connections (Broker0, 1, 2). If
> client uses limit conf and elects partitions such as [0, 1, 2], then 
client
> will create 2 connections (Broker0, 1). Of course, if client elects
> partitions such as [0, 2, 3], then client will still create 3 connections.
> >
> > I'd like to decrease number of producers. I think that resources of
> broker will be improved slightly by this feature because broker has list 
of
> producers by some classes such as ServerCnx, AbstractTopic.
> >
> 
https://github.com/apache/pulsar/blob/fa41d02bebfd841767846240f3ae574047f118f0/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/ServerCnx.java#L1096-L1097
> >
> 
https://github.com/apache/pulsar/blob/fa41d02bebfd841767846240f3ae574047f118f0/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/AbstractTopic.java#L577
> >
> > In my case, unspecified number of producers will connect to the same
> partitioned topic with different rate. We need to set the number of
> partitions according to the high-rate producer.
> > However, on the other hand, this number is excessively large for
> low-rate producers.
> > I want to reduce such redundant producers for resource efficiency.
> >
> > Regards,
> > --
> > Yuri Mizushima
> > yumiz...@yahoo-corp.jp
> >
> >
> > "Sijie Guo"  wrote:
> >
> >  Hi Yuri,
> >
> >  In today's community meeting, Matteo shared some of his thoughts
> about this
> >  PIP.
> >
> >  You can find some meeti

Re: Pulsar Server on JDK11 - initial discussion

[Enrico Olivelli]

Renkai,

Il giorno mer 10 feb 2021 alle ore 09:35 Renkai Ge 
ha scritto:

> LGTM if I don’t understand wrong.
>
> The key point is to build docker image in Java 11 so that new Pulsar users
> can start with Java 11 easier, but existing users can still have freedom to
> choose Java 8 or 11 as they wish.
>

Yes this is one of the main point,
the second point to be implemented in the short term is to make the build
and test work on Java 11 (and switch most of CI jobs on Java 11)


If there are no other points/objections I will start to send a first set of
patches, the first thing (and the hardest one) to do is to see all tests
passing on Java 11

Thank you all for this discussion

Enrico


>
> > 2021年2月9日 下午5:41，Enrico Olivelli  写道：
> >
> > Yunze,
> > It's not exactly as you write.
> >
> > We will be building and testing on JDK11.
> >
> > Binaries, both server and client, will be able to run on jdk8
> >
> > Building on jdk11 targeting jdk8 does not bring much benefit as you
> cannot
> > use jdk11 features and also the byte code will look like the jdk8 version
> > (for instance no NestMates)
> >
> > Currently Pulsar 2.6 and Pulsar 2.7 run well on jdk11
> >
> >
> > But is the first step towards moving to jdk11 as primary jdk
> >
> > I hope that helps
> > Enrico
> >
> > Il Mar 9 Feb 2021, 10:18 Yunze Xu  ha
> scritto:
> >
> >> LGTM if I don’t understand wrong.
> >>
> >> In short, there’re two key points:
> >>
> >> 1. Keep the code compatible with Java 8.
> >> 2. Release the binaries that are built on JDK 11 to get the benefit.
> >>
> >> So Java 8 users can still build Pulsar with JDK 8 but the default
> releases
> >> are built on JDK 11.
> >>
> >> - Yunze
> >>
> >>
>
>

Re: Five minute interview blog posts

[Sijie Guo]

Thanks, everyone for the input!

I think there are two different things mixing together here. One is the
improvement on the documentation which provides more information about use
cases and makes the Pulsar documentation site more searchable; the other
one is what content to be hosted on the project side.

I would suggest separating these two things in the discussion.

For the first part of the improvement, I think it is a great idea to have a
better "Get Started" section to include "Use Cases". Jennifer, Huanli, and
Yu are the main committers driving the development of the documentation.
They can provide some of the insights from a technical writing perspective.

> Clean up the header by folding Clients, REST APIs, and Cli into Docs

One of the reasons that why "Clients, REST APIs, and CLI" are added to the
menu, not the sidebar is due to the limitation of the documentation
framework 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:
>
> 1. Add a Get Started section to the site modeled on Kafka's
>a. Introduction
>b. Quickstart
>c. Use cases -- this would be a blog-like section
>
> Not included:
>d. books&papers and podcasts we can ignore for now
>e. videos we could do but I feel like it's hard to create an objective
> measure for what should be included, Kafka uses ratings from Kafka Summit
> and I don't think we have something similar.  As an alternative we could
> just link the most recent full Pulsar Summit archive.
>
> 2. Clean up the header by folding Clients, REST APIs, and Cli into Docs
> (Clients is already just a deep link to a docs page)
>
> 3. Rename Blog to Announcements
>
> 4. Remove Community -> Resources as obsoleted by the new Get Started
>
> I'm happy to volunteer to draft content for the new Get Started sections.
>
>
>
> On Tue, Feb 9, 2021 at 3:45 PM Joshua Odmark 
> wrote:
>
> > For me this gets into a bigger issue. That issue for me is that right
> now,
> > I need to visit half a dozen sites to get the full picture of Pulsar.
> >
> > Putting content like this on a separate site and linking to it from
> Pulsar
> > doesn’t create the proper journey in my mind.
> >
> > I don’t know if it should be necessarily in the blog or not, but I think
> > it makes sense to create an entirely new section of the Pulsar website,
> > similar to how Kafka’s does it. Take the concept of Resources, but turn
> it
> > into a journey and put the content right on the Pulsar website. Possibly
> > get rid of the blog and name it something more precise if the wish was to
> > focus on specific project releases and milestones.
> >
> > Part of what is missing is just words on a page for SEO value 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  and have it
> take
> > a 'Getting Started' approach.
> >
> > > On Feb 9, 2021, at 1:13 PM, Jonathan Ellis  wrote:
> > >
> > > I agree that SEO is an important aspect here.
> > >
> > > When I google [apache pulsar use cases], here are the top ten, with
> > actual
> > > case studies marked with *.  (If I leave out Apache, the results are
> > > similar but a Confluent article creeps into the top 5.)
> > >
> > > 1. kesque.com 7 Reasons We Chose Apache Pulsar
> > > 2. *InfoQ article on Iterable
> > > 3. DataBricks Spark Summit session on Pulsar
> > > 4. *StreamNative blog post on Yahoo! Japan
> > > 5. StreamNative blog post on Pulsar vs Kafka
> > > 6. pulsar.apache.org/blog
> > > 7. pulsar.apache.org/resources
> > > 8. manning.com introduction to Apache Pulsar in Action
> > > 9. xenonstack.com The Ultimate Guide to Apache Pulsar
> > > 10. *medium.com  Why Nutanix Beam went ahead with Apache Pulsar
> > >
> > > So 3 of the top 10 are actual case studies.  That's not great.  We want
> > > people looking for proof that Pulsar is ready for mainstream use to be
> > able
> > > to easily find relevant use cases.
> > >
> > > Fortunately, Google already recognizes that the Apache Pulsar web site
> > > should rank highly here, so the easiest way (the only realistic way?)
> for
> > > us to fix this is to post them ourselves.
> > >
> > >
> > > On Mon, Feb 8, 2021 at 1:02 PM Devin Bost 
> wrote:
> > >
> > >> Hi Jonathan,
> > >>
> > >> Thanks for giving thought to this subject. I think we can all agree
> that
> > >> increasing public awareness of the momentum and community strength
> > behind
> > >> Pulsar is a common goal among members of the Pulsar community. I'm
> sure
> > >> many of us have run into similar challenges with increasing adoption
> of
> > >> Pulsar.
> > >>
> > >> I personally have had success with my videos on Pulsar, but I found
> that
> > >> broadcasting my videos to a wide list of channels was critical to
> > getting
> > >> good visibility. (My video where I put th

Re: [VOTE] Pulsar Client Go Release 0.4.0 Candidate 1

[Yuri Mizushima]

+1 (non-binding)

* check shasum
* run simple producer/consumer/reader

and found no problem.
Thank you for your work!

nits:
Is this signature right? In my environment, checked it and found "No public 
key" error.
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.4.0-candidate-1/apache-pulsar-client-go-0.4.0-src.tar.gz.asc

Regards,
-- 
Yuri Mizushima
yumiz...@yahoo-corp.jp
 

"xiaolong ran"  wrote:

Hi everyone,

Please review and vote on the release candidate #1 for the version 0.4.0,
as follows:

[ ] +1, Approve the release

[ ] -1, Do not approve the release (please provide specific comments)


This is the first release candidate for Apache Pulsar Go client, version
0.4.0.


It fixes the following issues:

https://github.com/apache/pulsar-client-go/milestone/5?closed=1


Pulsar Client Go's KEYS file contains PGP keys we used to sign this release:

https://dist.apache.org/repos/dist/release/pulsar/KEYS


Please download these packages and review this release candidate:

- Review release notes

- Download the source package (verify shasum, and asc) and follow the

README.md to build and run the pulsar-client-go.


The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.


Source file:


https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.4.0-candidate-1/apache-pulsar-client-go-0.4.0-src.tar.gz


The tag to be voted upon:

v0.4.0

https://github.com/apache/pulsar-client-go/tree/v0.4.0-candidate-1


SHA-512 checksums:


4ca22efb026f6a1248107d8e553c10e8ce2f22b5d624c719d8a50d49c4745df7b45ac5576c4f15a7cea6fcb963c6afd25e5e661f80e256f29b8eac4515aed3f5
 apache-pulsar-client-go-0.4.0-src.tar.gz


--

Thanks

Xiaolong Ran

Re: Five minute interview blog posts

[Anonymitaet _]

- Agree that we can add "case study" since it takes the attention off Pulsar 
itself and focuses on the users' perspectives (e.g. how Pulsar can be used, how 
Pulsar fits their situation, etc.).

- Besides, do we consider adding "Book and Paper" section? It is one way to 
demonstrate that Pulsar is popular and the community is thriving.
Pulsar book: https://www.manning.com/books/apache-pulsar-in-action 
Search "Apache Pulsar" in Google Scholar: 
https://scholar.google.com/scholar?hl=en&as_sdt=0%2C5&q=apache+pulsar&btnG= 

On 2021/2/10, 17:58, "Sijie Guo"  wrote:

Thanks, everyone for the input!

I think there are two different things mixing together here. One is the
improvement on the documentation which provides more information about use
cases and makes the Pulsar documentation site more searchable; the other
one is what content to be hosted on the project side.

I would suggest separating these two things in the discussion.

For the first part of the improvement, I think it is a great idea to have a
better "Get Started" section to include "Use Cases". Jennifer, Huanli, and
Yu are the main committers driving the development of the documentation.
They can provide some of the insights from a technical writing perspective.

> Clean up the header by folding Clients, REST APIs, and Cli into Docs

One of the reasons that why "Clients, REST APIs, and CLI" are added to the
menu, not the sidebar is due to the limitation of the documentation
framework 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:
>
> 1. Add a Get Started section to the site modeled on Kafka's
>a. Introduction
>b. Quickstart
>c. Use cases -- this would be a blog-like section
>
> Not included:
>d. books&papers and podcasts we can ignore for now
>e. videos we could do but I feel like it's hard to create an objective
> measure for what should be included, Kafka uses ratings from Kafka Summit
> and I don't think we have something similar.  As an alternative we could
> just link the most recent full Pulsar Summit archive.
>
> 2. Clean up the header by folding Clients, REST APIs, and Cli into Docs
> (Clients is already just a deep link to a docs page)
>
> 3. Rename Blog to Announcements
>
> 4. Remove Community -> Resources as obsoleted by the new Get Started
>
> I'm happy to volunteer to draft content for the new Get Started sections.
>
>
>
> On Tue, Feb 9, 2021 at 3:45 PM Joshua Odmark 
> wrote:
>
> > For me this gets into a bigger issue. That issue for me is that right
> now,
> > I need to visit half a dozen sites to get the full picture of Pulsar.
> >
> > Putting content like this on a separate site and linking to it from
> Pulsar
> > doesn’t create the proper journey in my mind.
> >
> > I don’t know if it should be necessarily in the blog or not, but I think
> > it makes sense to create an entirely new section of the Pulsar website,
> > similar to how Kafka’s does it. Take the concept of Resources, but turn
> it
> > into a journey and put the content right on the Pulsar website. Possibly
> > get rid of the blog and name it something more precise if the wish was 
to
> > focus on specific project releases and milestones.
> >
> > Part of what is missing is just words on a page for SEO value 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  and have it
> take
> > a 'Getting Started' approach.
> >
> > > On Feb 9, 2021, at 1:13 PM, Jonathan Ellis  wrote:
> > >
> > > I agree that SEO is an important aspect here.
> > >
> > > When I google [apache pulsar use cases], here are the top ten, with
> > actual
> > > case studies marked with *.  (If I leave out Apache, the results are
> > > similar but a Confluent article creeps into the top 5.)
> > >
> > > 1. kesque.com 7 Reasons We Chose Apache Pulsar
> > > 2. *InfoQ article on Iterable
> > > 3. DataBricks Spark Summit session on Pulsar
> > > 4. *StreamNative blog post on Yahoo! Japan
> > > 5. StreamNative blog post on Pulsar vs Kafka
> > > 6. pulsar.apache.org/blog
> > > 7. pulsar.apache.org/resources
> > > 8. manning.com introduction to Apache Pulsar in Action
> > > 9. xenonstack.com The Ultimate Guide to Apache Pulsar
> > > 10. *medium.com  Why Nutanix Beam went ahead with Apache Pulsar
> > >
> > > So 3 of the top 10 are actual case studies.  That's not great.  We 
want
> > > people looking for proof t

[GitHub] [pulsar-dotpulsar] oven-baked opened a new issue #68: Consuming a Message generated by a Python Pulsar Function puts Consumer in Faulted state.

[GitBox]

oven-baked opened a new issue #68:
URL: https://github.com/apache/pulsar-dotpulsar/issues/68


   I've been generating messages in a Python Pulsar function and spitting them 
out a receiving topic.
   
   When I consume from that topic using the client app bundled with Pulsar, 
everything works okay and I can pull down and see my resulting messages.
   
   If the DotPulsar consumer tries to pick up any of those messages from the 
function, it immediately enters a faulted state. 
   
   The exception message is "{"Specified argument was out of the range of valid 
values. (Parameter 'length')"}"
   
   I've been able to pull the following stack trace from the library:
   `System.ThrowHelper.ThrowStartOrEndArgumentValidationException(Int64 start)
  at System.Buffers.ReadOnlySequence`1.Slice(Int64 start, Int64 length)
  at DotPulsar.Internal.BatchHandler.Add(MessageIdData messageId, UInt32 
redeliveryCount, MessageMetadata metadata, ReadOnlySequence`1 data) in 
C:\Users\X2012039\source\repos\pulsar-dotpulsar\src\DotPulsar\Internal\BatchHandler.cs:line
 51
  at DotPulsar.Internal.ConsumerChannel.d__9.MoveNext() in 
C:\Users\X2012039\source\repos\pulsar-dotpulsar\src\DotPulsar\Internal\ConsumerChannel.cs:line
 89
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task 
task)
  at 
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
 task)
  at System.Threading.Tasks.ValueTask`1.get_Result()
  at 
System.Runtime.CompilerServices.ConfiguredValueTaskAwaitable`1.ConfiguredValueTaskAwaiter.GetResult()
  at DotPulsar.Internal.Consumer.d__17.MoveNext() in 
C:\Users\X2012039\source\repos\pulsar-dotpulsar\src\DotPulsar\Internal\Consumer.cs:line
 99
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task 
task)
  at 
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
 task)
  at System.Threading.Tasks.ValueTask`1.get_Result()
  at 
System.Runtime.CompilerServices.ConfiguredValueTaskAwaitable`1.ConfiguredValueTaskAwaiter.GetResult()
  at DotPulsar.Internal.Executor.d__9`1.MoveNext() in 
C:\Users\X2012039\source\repos\pulsar-dotpulsar\src\DotPulsar\Internal\Executor.cs:line
 136`



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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Five minute interview blog posts

[Jonathan Ellis]

I'd also like to figure out how we can get the TGI Pulsar videos featured
more prominently.  Those are really well done.

On Wed, Feb 10, 2021 at 3:58 AM Sijie Guo  wrote:

> Thanks, everyone for the input!
>
> I think there are two different things mixing together here. One is the
> improvement on the documentation which provides more information about use
> cases and makes the Pulsar documentation site more searchable; the other
> one is what content to be hosted on the project side.
>
> I would suggest separating these two things in the discussion.
>
> For the first part of the improvement, I think it is a great idea to have a
> better "Get Started" section to include "Use Cases". Jennifer, Huanli, and
> Yu are the main committers driving the development of the documentation.
> They can provide some of the insights from a technical writing perspective.
>
> > Clean up the header by folding Clients, REST APIs, and Cli into Docs
>
> One of the reasons that why "Clients, REST APIs, and CLI" are added to the
> menu, not the sidebar is due to the limitation of the documentation
> framework 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:
> >
> > 1. Add a Get Started section to the site modeled on Kafka's
> >a. Introduction
> >b. Quickstart
> >c. Use cases -- this would be a blog-like section
> >
> > Not included:
> >d. books&papers and podcasts we can ignore for now
> >e. videos we could do but I feel like it's hard to create an objective
> > measure for what should be included, Kafka uses ratings from Kafka Summit
> > and I don't think we have something similar.  As an alternative we could
> > just link the most recent full Pulsar Summit archive.
> >
> > 2. Clean up the header by folding Clients, REST APIs, and Cli into Docs
> > (Clients is already just a deep link to a docs page)
> >
> > 3. Rename Blog to Announcements
> >
> > 4. Remove Community -> Resources as obsoleted by the new Get Started
> >
> > I'm happy to volunteer to draft content for the new Get Started sections.
> >
> >
> >
> > On Tue, Feb 9, 2021 at 3:45 PM Joshua Odmark 
> > wrote:
> >
> > > For me this gets into a bigger issue. That issue for me is that right
> > now,
> > > I need to visit half a dozen sites to get the full picture of Pulsar.
> > >
> > > Putting content like this on a separate site and linking to it from
> > Pulsar
> > > doesn’t create the proper journey in my mind.
> > >
> > > I don’t know if it should be necessarily in the blog or not, but I
> think
> > > it makes sense to create an entirely new section of the Pulsar website,
> > > similar to how Kafka’s does it. Take the concept of Resources, but turn
> > it
> > > into a journey and put the content right on the Pulsar website.
> Possibly
> > > get rid of the blog and name it something more precise if the wish was
> to
> > > focus on specific project releases and milestones.
> > >
> > > Part of what is missing is just words on a page for SEO value 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  and have it
> > take
> > > a 'Getting Started' approach.
> > >
> > > > On Feb 9, 2021, at 1:13 PM, Jonathan Ellis 
> wrote:
> > > >
> > > > I agree that SEO is an important aspect here.
> > > >
> > > > When I google [apache pulsar use cases], here are the top ten, with
> > > actual
> > > > case studies marked with *.  (If I leave out Apache, the results are
> > > > similar but a Confluent article creeps into the top 5.)
> > > >
> > > > 1. kesque.com 7 Reasons We Chose Apache Pulsar
> > > > 2. *InfoQ article on Iterable
> > > > 3. DataBricks Spark Summit session on Pulsar
> > > > 4. *StreamNative blog post on Yahoo! Japan
> > > > 5. StreamNative blog post on Pulsar vs Kafka
> > > > 6. pulsar.apache.org/blog
> > > > 7. pulsar.apache.org/resources
> > > > 8. manning.com introduction to Apache Pulsar in Action
> > > > 9. xenonstack.com The Ultimate Guide to Apache Pulsar
> > > > 10. *medium.com  Why Nutanix Beam went ahead with Apache Pulsar
> > > >
> > > > So 3 of the top 10 are actual case studies.  That's not great.  We
> want
> > > > people looking for proof that Pulsar is ready for mainstream use to
> be
> > > able
> > > > to easily find relevant use cases.
> > > >
> > > > Fortunately, Google already recognizes that the Apache Pulsar web
> site
> > > > should rank highly here, so the easiest way (the only realistic way?)
> > for
> > > > us to fix this is to post them ourselves.
> > > >
> > > >
> > > > On Mon, Feb 8, 2021 at 1:02 PM Devin Bost 
> > wrote:
> > > >
> > > >> Hi Jonathan,
> > > >>
> > > >> Thanks for giving thought to this subject. I think we can all agree
> > that
> > > >> increasing public awareness of the momentum and community str

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #68: Consuming a Message generated by a Python Pulsar Function puts Consumer in Faulted state.

[GitBox]

blankensteiner commented on issue #68:
URL: https://github.com/apache/pulsar-dotpulsar/issues/68#issuecomment-776893360


   Hi @oven-baked 
   Thanks for the bug report, I'll look into this tomorrow.
   Can you confirm that the Python function is batching messages?



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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #68: Consuming a Message generated by a Python Pulsar Function puts Consumer in Faulted state.

[GitBox]

blankensteiner commented on issue #68:
URL: https://github.com/apache/pulsar-dotpulsar/issues/68#issuecomment-777258631


   I tried producing some messages from a java client with batching enabled, 
creating batches containing 1 to multiple messages. I was able to read the 
messages just fine from DotPulsar.
   Maybe the Python function is creating batched messages in a way that 
DotPulsar doesn't expect.
   What version of DotPulsar are you using?
   And what version of Pulsar are the functions running on?



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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org