xiaogang-sn opened a new pull request, #178:
URL: https://github.com/apache/pulsar-site/pull/178
The individual release notes are available as below while they are not
indexed at https://pulsar.apache.org/release-notes/.
https://pulsar.apache.org/release-notes/versioned/pulsar-2.7.0/
I have submitted a fix in https://github.com/apache/pulsar/pull/17273 .
The main motivation of this PR is to fix and restore broker cache eviction
of entries based on the earliest read position of active cursors
(consumers) and also handle this in an efficient and performant way so that
the origin
Thank you tison!
We don't explicitly set the rules for issue titles and force ppl to follow.
Just suggest you can follow the same rule to write issue titles if you
ensure the involved [type] and [scope] like this example [1].
Otherwise, you can write as usual.
[1] https://github.com/apache/pulsa
GitHub user Nintorac added a comment to the discussion: Presto connector schema
issue
Got the logs to work now something weird about the config I was using was
killing the logs I think?
eg. `# pulsar.nar-extraction-directory=System.getProperty("java.io.tmpdir")`
anyway logs like this
```
20
tisonkun opened a new pull request, #179:
URL: https://github.com/apache/pulsar-site/pull/179
This refers to https://github.com/apache/pulsar/pull/17265.
--
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
tisonkun commented on PR #179:
URL: https://github.com/apache/pulsar-site/pull/179#issuecomment-1227054329
cc @Anonymitaet @urfreespace
--
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 specif
urfreespace opened a new pull request, #180:
URL: https://github.com/apache/pulsar-site/pull/180
https://github.com/apache/pulsar-site/issues/173
--
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 t
urfreespace merged PR #180:
URL: https://github.com/apache/pulsar-site/pull/180
--
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: dev-unsubscr...@pulsar.a
urfreespace closed issue #173: Improve color shades for dark mode
URL: https://github.com/apache/pulsar-site/issues/173
--
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 unsub
urfreespace commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1227088190
fixed with this PR https://github.com/apache/pulsar-site/pull/180
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
tisonkun commented on code in PR #180:
URL: https://github.com/apache/pulsar-site/pull/180#discussion_r954807271
##
site2/website-next/static/swagger/restApiVersions.json:
##
@@ -81,7 +81,7 @@
]
}
],
-"2.4.0": [
+"2.4.1": [
Review Comment:
tisonkun commented on issue #177:
URL: https://github.com/apache/pulsar-site/issues/177#issuecomment-1227107016
@SignorMercurio the link is broken for me. I don't find the referred
discussion.
--
This is an automated message from the Apache Git Service.
To respond to the message, please l
tisonkun commented on PR #68:
URL: https://github.com/apache/pulsar-test-infra/pull/68#issuecomment-1227119268
**NOTE** With composite action, we always check out the master branch of
`apache/pulsar-test-infra` to get the code. If we use Docker action, we can
deliver the code along with eac
tisonkun commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1227129477
Thanks! Although the color series seems can be continuously improved, now
the content can be read clearly.
--
This is an automated message from the Apache Git Service.
To respon
tisonkun commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1227137697
@urfreespace found one case inconsistent: https://pulsar.apache.org/versions/
https://user-images.githubusercontent.com/18818196/186653261-503b381d-e7d4-4d62-9965-f15c7aa83ac
urfreespace commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1227144181
> @urfreespace found one case inconsistent:
https://pulsar.apache.org/versions/
>
> https://user-images.githubusercontent.com/18818196/186653261-503b381d-e7d4-4d62-9965-f
> I think that the main problem is that in our community we have plenty
of Java developers and there are a few committers that review
the patches on non-Java client.
Yes. The primary purpose of this project is to keep track of many
uncaught-up features of other languages clients. And there will be
urfreespace merged PR #181:
URL: https://github.com/apache/pulsar-site/pull/181
--
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: dev-unsubscr...@pulsar.a
urfreespace commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1227157172
fixed https://github.com/apache/pulsar-site/pull/181, @tisonkun PTAL after
some time, if it works well, pls help close this issue, thanks
--
This is an automated message from
tisonkun closed issue #173: Improve color shades for dark mode
URL: https://github.com/apache/pulsar-site/issues/173
--
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 unsubscr
tisonkun commented on issue #173:
URL: https://github.com/apache/pulsar-site/issues/173#issuecomment-1227182203
Looks good now. And verify no regression on the original reported page.
https://user-images.githubusercontent.com/18818196/186662554-afa1b3ad-599b-449f-8ce7-4d8b9ff60e16.png"
SignorMercurio commented on issue #177:
URL: https://github.com/apache/pulsar-site/issues/177#issuecomment-1227197195
@tisonkun Sorry, perhaps due to it's a private discussion. I believe
@Anonymitaet has sent an email asking for thoughts on this issue?
--
This is an automated message from
+1
Thanks,
Xiaoyu Hou
Haiting Jiang 于2022年8月23日周二 22:10写道：
> Hello, Pulsar community:
>
> I'd like to propose to release Apache Pulsar 2.10.2
>
> Currently, we have 189 commits [0] labeled with `release/2.10.2`,
> And 39 of them are not cherry-picked yet [1].
>
> And there are 39 open PRs [2],
Hi jiwei
Sorry for late reply. I'd like to add PIP189 to 2.11.0, is it possible now
- PIP 189: No batching if only one message in batch.
https://github.com/apache/pulsar/pull/16605
Thanks,
Xiaoyu Hou
guo jiwei 于2022年8月24日周三 10:16写道：
> Hi all,
>We have merged all the blocker patches, and
Hi Pulsar Community,
This is a PIP discussion on extending the BrokerInterceptor.
Details can be found in the issue:
https://github.com/apache/pulsar/issues/17267
Copying the content here for convenience, any suggestions are welcome and
appreciated.
Motivation
Currently, we have a reconciliation
> On Aug 23, 2022, at 10:22 AM, Rajan Dhabalia wrote:
>
> Hi,
>
I think we can move all the PIPs to the codebase and the new proposal
> and proposal without any reviews should happen with a PR first. So that we
> can review and comment easily.
>
> I didn't understand this part. You want
jakiuncle opened a new pull request, #484:
URL: https://github.com/apache/pulsar-manager/pull/484
Motivation
Update support for casdoor, because casdoor has updated.
*(If this PR fixes a github issue, please add `Fixes #`.)*
Fixes #<446>
*(or if this PR is one task
After doing more testing I have updated the patch with a small change
but very effective
https://github.com/apache/pulsar/pull/17241
With the latest commit now we are able to attach to pending requests
for ranges that are "larger" than the requested range.
So if you have 100...200 in pending state
hsluoyz commented on PR #484:
URL: https://github.com/apache/pulsar-manager/pull/484#issuecomment-1227458873
@tuteng plz review
--
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 commen
Hi Dave,
> Let’s outline how PIPs are currently working and then discuss changes.
Yes, I will prepare for the changes.
This is the documentation for how PIPs are currently working:
https://github.com/apache/pulsar/pull/17270/files#diff-a56445d038f8a3df4c74724076c62437915f091437b4e26a1c5aada7184dc
GitHub user rillo-carrillo created a discussion: Zookeeper lose cluster
information
I have a zookeeper cluster on kubernetes.
Each zookeeper has it's own persistent storage.
Once zookeeper cluster is enabled I execute initialize-cluster-metadata command:
```
pulsar initialize-cluster-metadata
Anonymitaet commented on issue #177:
URL: https://github.com/apache/pulsar-site/issues/177#issuecomment-1227853742
ML:
https://lists.apache.org/thread/1g8nxqg4gdw3obq4wfgv442hvspk7ovy
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
+1 on this,
I think helm chart should not be a big issue, we can just upgrade the chart
and provide necessary doc on how to upgrade.
tison 于2022年8月24日周三 16:41写道：
> Hi Enrico and Qiang,
>
> The issue description was updated. Picked here:
>
> > upgrade and downgrade doc
>
> This change should not
Thanks for your input!
I update the prototype as described in the proposal:
https://github.com/apache/pulsar/pull/17062
Will initialize a vote for PIP-200 soon.
Best,
tison.
Zhengxin Cai 于2022年8月26日周五 08:36写道：
> +1 on this,
> I think helm chart should not be a big issue, we can just upgrade
GitHub user tisonkun added a comment to the discussion: Flink Connector
Exception: Failed to list subscribed topic partitions due to
@BohanZhang0222 code rendered informally. Could you quote code in a [fenced
block](https://www.markdownguide.org/extended-syntax/#fenced-code-blocks)?
cc @syhil
GitHub user abcMH1966 added a comment to the discussion: I encountered a port
error when using pulsar to integrate etcd
> I have tests on the docker image of `docker pull lypgcs/pulsar:2022-08-23`
> and it's working for etcd cluster.
>
> You need Change `etcd:node01:2379,node02:2379,node03:23
Hi Penghui
Thanks for you start this discussion. IMO, It is also a good way for
beginners to learn the design and implementation of each module of Pulsar.
> 3. /wiki/pip/accepted - for PIPs that have been accepted and are works in
progress
> 4. /wiki/pip/complete - for PIPs that have been completed
GitHub user BohanZhang0222 edited a discussion: Flink Connector Exception:
Failed to list subscribed topic partitions due to
## Env
Pulsar Version: 2.9.2
Flink Version: 1.14
##Source Conf
```
{"topicNames":["persistent://autopilot/x01/autopilot-filter-iot-signal-canlog-x01-testtwo-partition-0"
+1
Thanks,
Haiting
On Thu, Aug 25, 2022 at 9:52 AM Baodi Shi
wrote:
> +1
>
> Thanks,
> Baodi Shi
>
> > On Aug 24, 2022, at 20:1312, Qiang Huang
> wrote:
> >
> > +1
> >
> > Zike Yang 于2022年8月22日周一 15:32写道：
> >
> >> +1
> >>
> >> Thanks,
> >> Zike Yang
> >>
> >> On Mon, Aug 22, 2022 at 3:16 PM m
Hi Anon
After we cut the branch, the code freezed.
Regards
Jiwei Guo (Tboy)
On Thu, Aug 25, 2022 at 9:45 PM Anon Hxy wrote:
> Hi jiwei
>
> Sorry for late reply. I'd like to add PIP189 to 2.11.0, is it possible now
>
> - PIP 189: No batching if only one message in batch.
> https://github.
Hi Mingyu,
About the use case of this feature, I have some concerns.
Changing the message routing strategy in the producer may cause a message
ordering issue.
But if you don't have message ordering requirements, you can use SHARE
subscription mode,
and we can increase the consumer number of one
Hi Xiangying,
> We can classify the pips under these folders according to the pulsar
modules, instead of just placing these pips under these folders in an
incrementing sequence number.
I think it's not easy to do this. A proposal can have changes related to
multiple
modules(Broker, Metadata, Clie
Looks good to me.
I just have one suggestion.
Maybe using `onMessagePublish` is more clear than `beforeMessagePersistent`.
`beforeMessagePersistent` it is not very intuitive to understand the
starting point
of the interception position, maybe from the managed-ledger or before call
bookkeeper
clien
GitHub user BohanZhang0222 created a discussion: delete partitioned-topic
failed and the broker exits abnormally
### Version
2.9.2
pulsar on k8s
### Exception
https://user-images.g
Thanks for your suggestion.
`onMessagePublish` is more precise for understanding.
PengHui Li 于2022年8月26日周五 10:30写道：
> Looks good to me.
> I just have one suggestion.
>
> Maybe using `onMessagePublish` is more clear than
> `beforeMessagePersistent`.
> `beforeMessagePersistent` it is not very intu
> We should move to the codebase 100% the same as the original documentation.
> And use another PR to make improvements for it. If it is needed, we should
> start with an email.
> We need to have historical records.
+1 I think this is a great idea. It makes sense to copy them verbatim
and then wor
michaeljmarshall opened a new pull request, #182:
URL: https://github.com/apache/pulsar-site/pull/182
I ran the following commands to generate these docs:
```
$ PULSAR_VERSION=2.9.2 ./site2/tools/api/python/build-docs-in-docker.sh
$ PULSAR_VERSION=2.9.3 ./site2/tools/api/python/b
Makes sense
+1
Enrico
Il giorno ven 26 ago 2022 alle ore 05:17 Aloys Zhang
ha scritto:
>
> Thanks for your suggestion.
> `onMessagePublish` is more precise for understanding.
>
> PengHui Li 于2022年8月26日周五 10:30写道：
>
> > Looks good to me.
> > I just have one suggestion.
> >
> > Maybe using `onMes
48 matches
Mail list logo
