GitHub user tisonkun added a comment to the discussion: [Design] Pulsar All
Releases Page
I think the release manager could be included in the blog and we don't need to
highlight it. Highlight the release date is useful for users, though.
Generally the picture looks good :)
GitHub link:
htt
tisonkun commented on PR #187:
URL: https://github.com/apache/pulsar-site/pull/187#issuecomment-1231164990
cc @Anonymitaet
--
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.
When I build from the source (both for the git tag
`v2.7.5-candidate-3` and the extracted src tarball
`apache-pulsar-2.7.5-src.tar.gz`), I am getting an error when I run
the license check:
```
$ src/check-binary-license
distribution/server/target/apache-pulsar-2.7.5-bin.tar.gz
com.sun.activation-j
GitHub user Anonymitaet edited a discussion: [Design] Pulsar All Releases Page
Hi team,
1. How about providing more useful content to the [Pulsar Release Notes > All
Releases](https://pulsar.apache.org/release-notes/) page as
[below](https://docs.google.com/spreadsheets/d/1XHmzno-1kbHvPp7eogr
GitHub user Anonymitaet edited a discussion: [Design] Pulsar All Releases Page
Hi team,
Currently, we do not have a place showing the timeline for all Pulsar releases.
How about creating a Pulsar [Release Notes >
Timeline](https://pulsar.apache.org/release-notes/timeline) page along with the
tisonkun commented on code in PR #187:
URL: https://github.com/apache/pulsar-site/pull/187#discussion_r957944903
##
site2/website-next/docusaurus.config.js:
##
@@ -349,10 +349,17 @@ module.exports = {
Copyright © ${new Date().getFullYear()} The Apache Software
Foundation
Anonymitaet commented on PR #186:
URL: https://github.com/apache/pulsar-site/pull/186#issuecomment-1231064979
@mendonk thanks for your contribution! Please submit your PR to
https://github.com/apache/pulsar rather than here.
Details see
https://docs.google.com/document/d/1-1uJyd1k9_h56xi
tisonkun commented on code in PR #187:
URL: https://github.com/apache/pulsar-site/pull/187#discussion_r957942811
##
site2/website-next/docusaurus.config.js:
##
@@ -349,10 +349,17 @@ module.exports = {
Copyright © ${new Date().getFullYear()} The Apache Software
Foundation
tisonkun commented on code in PR #187:
URL: https://github.com/apache/pulsar-site/pull/187#discussion_r957941579
##
site2/website-next/docusaurus.config.js:
##
@@ -349,10 +349,17 @@ module.exports = {
Copyright © ${new Date().getFullYear()} The Apache Software
Foundation
tisonkun opened a new pull request, #187:
URL: https://github.com/apache/pulsar-site/pull/187
All changes to the `docs` folder should be carried to the main repo also.
cc @urfreespace @dave2wave
--
This is an automated message from the Apache Git Service.
To respond to the message,
urfreespace closed issue #177: Migrate all docs from `/tools` to `/reference`
URL: https://github.com/apache/pulsar-site/issues/177
--
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
urfreespace merged PR #184:
URL: https://github.com/apache/pulsar-site/pull/184
--
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 merged PR #183:
URL: https://github.com/apache/pulsar-site/pull/183
--
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
mendonk opened a new pull request, #186:
URL: https://github.com/apache/pulsar-site/pull/186
Corrects Elasticsearch `compatibilityMode` config values.
Motivation
Clarifies the values that a user expects from compatibilityMode
Modifications
required=false and default value
michaeljmarshall commented on PR #182:
URL: https://github.com/apache/pulsar-site/pull/182#issuecomment-1230861282
Thank you for catching my mistake @tisonkun. I fixed the script here
https://github.com/apache/pulsar-site/pull/185.
--
This is an automated message from the Apache Git Servi
michaeljmarshall merged PR #185:
URL: https://github.com/apache/pulsar-site/pull/185
--
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...@pul
michaeljmarshall commented on PR #185:
URL: https://github.com/apache/pulsar-site/pull/185#issuecomment-1230860667
I manually tested this change to verify its correctness.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
michaeljmarshall opened a new pull request, #185:
URL: https://github.com/apache/pulsar-site/pull/185
Put generated python docs into the `website-next` directory, as @tisonkun
explains in this comment
https://github.com/apache/pulsar-site/pull/182#issuecomment-1230199254.
--
This is an a
Hi Lari,
I had considered about the `remote write API`, but there will be some problems:
1. Does all the Metrics Systems support Prometheus format remote write protocol
2. How to resolve extra label(podName etc.), I don’t know if the extra labels
will be added atomically when write to TSDB
Than
Is there a specific reason to put the PIPs in the apache/pulsar repository?
I think that it will add unnecessary cruft to our core source code repository.
Could we instead create a separate repository to hold the PIP files? The
example of Rust lang has a separate repository too,
https://github.
master branch is broken once again. Here's the fix:
https://github.com/apache/pulsar/pull/17339
Please review and merge
-Lari
On 2022/08/26 12:00:20 Lari Hotari wrote:
> Hi,
>
> GitHub Actions builds have been piling up in the build queue in the last few
> days.
> I posted on bui...@apache.org
```
A sub-team makes final decisions about RFCs after the benefits and
drawbacks are well understood. These decisions can be made at any time, but
the sub-team will regularly issue decisions. When a decision is made, the
RFC pull request will either be merged or closed. In either case, if the
reaso
> The only point worth attending to while drafting the new process is how to
avoid neglected out-of-date proposals. If a proposal was declined, who is
in charge to update its status in the readme?
That is a good point. IMO, everyone is able to correct the proposal status.
It wasn't easy for us bef
+1 (non binding)
Checks:
- Checksum and signatures
- Apache Rat check passes
- Compile from source
- Run Pulsar standalone and produce-consume from CLI
- Tested K8S installation with Datastax Pulsar helm chart and verified TLS,
offloads and ElasticSearch sink
Nicolò Boschi
Il giorno lun
Hi everyone, there are already two binding +1. Could anyone else help verify it?
Thanks,
Yunze
> 2022年8月23日 21:26，PengHui Li 写道：
>
> +1 (binding)
>
> - Start the standalone service
> - Publish and consume messages
> - Run the Cassandra connector
> - Validate the stateful function
>
> Thank
I like the idea of keeping the suggestions as files in the repo since as
you mentioned, it makes the review process using PRs much more streamlined.
I think keeping the status in an MD file and only there (having a single
source of truth) will make it less error-prone (people might forget to move
GitHub user syhily edited a comment on the discussion: Flink Connector
Exception: Failed to list subscribed topic partitions due to
@BohanZhang0222 I think the root cause should be some performance issues on
Pulsar side. Since flink connector requests a lot of metadata informations in
an extr
GitHub user syhily added a comment to the discussion: Flink Connector
Exception: Failed to list subscribed topic partitions due to
@BohanZhang0222 I think the root cause should be some performance issues on
Pulsar side. Since flink connector requests a lot of metadata informations in
an extre
+1 (non binding)
Checks:
- Checksum and signatures
- Apache Rat check passes
- Compile from source
- Run Pulsar standalone and produce-consume from CLI
Nicolò Boschi
Il giorno sab 27 ago 2022 alle ore 17:12 Qiang Huang <
qiang.huang1...@gmail.com> ha scritto:
> +1(non-binding)
> - Checked
+1 (non binding)
Thanks for taking care of this
Nicolò Boschi
Il giorno lun 29 ago 2022 alle ore 15:26 tison ha
scritto:
> Hi devs,
>
> This is the official thread VOTE for PIP-200 Package Pulsar Trino distro
> and config in a dedicated folder.
>
> Here is the PIP issue: https://github.com/apa
GitHub user syhily added a comment to the discussion: Flink Connector
Exception: Failed to list subscribed topic partitions due to
It's tracked here. https://github.com/streamnative/flink/issues/162
GitHub link:
https://github.com/apache/pulsar/discussions/17200#discussioncomment-3500858
---
Here is the vote thread:
https://lists.apache.org/thread/9stw26rrp9hm6l2xd2p78gpogw9bywgc
You're welcome to vote on the thread.
Best,
tison.
tison 于2022年8月26日周五 09:06写道：
> Thanks for your input!
>
> I update the prototype as described in the proposal:
> https://github.com/apache/pulsar/pull/1
Hi devs,
This is the official thread VOTE for PIP-200 Package Pulsar Trino distro
and config in a dedicated folder.
Here is the PIP issue: https://github.com/apache/pulsar/issues/17137
Here is the discussion thread:
https://lists.apache.org/thread/s985ypf0r0hzcm0mx653n5h2rt7n273v
Here is the link
I updated it to be PIP-205 since there was a previous reference of PIP-204. :)
-Lari
On 2022/08/29 12:55:43 Lari Hotari wrote:
> Hi all,
>
> I have drafted PIP-204: Reactive Java client for Apache Pulsar.
>
> PIP link:
> https://github.com/apache/pulsar/issues/17335
>
> Here's a copy of the c
Hi all,
I have drafted PIP-204: Reactive Java client for Apache Pulsar.
PIP link:
https://github.com/apache/pulsar/issues/17335
Here's a copy of the contents of the GH issue for your references:
Motivation
There's a need to "go reactive from end-to-end" when building modern
reactive applicatio
GitHub user liangyuanpeng added a comment to the discussion: I encountered a
port error when using pulsar to integrate etcd
If you can see some log like `Cluster metadata for 'xxx' setup correctly` ,
your cluster metadata is init successed. Then you can ignore this log.
GitHub link:
https://
GitHub user liangyuanpeng added a comment to the discussion: I encountered a
port error when using pulsar to integrate etcd
If you can see some log like `Cluster metadata for 'xxx' setup correctly` ,
your cluster metadata is init successed. Then you can ignore this log.
GitHub link:
https://
jakiuncle closed issue #483: I want use casdoor to login,when i change code,
happen some problem
URL: https://github.com/apache/pulsar-manager/issues/483
--
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
tisonkun commented on PR #182:
URL: https://github.com/apache/pulsar-site/pull/182#issuecomment-1230199254
@michaeljmarshall we have api docs for python under
https://github.com/apache/pulsar-site/tree/main/site2/website-next/static/api/python.
`site2/website` can be the folder for le
nodece commented on PR #69:
URL: https://github.com/apache/pulsar-test-infra/pull/69#issuecomment-1230166815
Covert to draft for testing.
--
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 speci
nodece commented on code in PR #69:
URL: https://github.com/apache/pulsar-test-infra/pull/69#discussion_r957210713
##
docbot/action.yml:
##
@@ -11,12 +11,12 @@ runs:
- name: Checkout
uses: actions/checkout@v3
with:
-repository: apache/pulsar-test-infra
nodece commented on PR #69:
URL: https://github.com/apache/pulsar-test-infra/pull/69#issuecomment-1230164873
Hi @tisonkun and @maxsxu, could help review this PR?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
nodece opened a new pull request, #69:
URL: https://github.com/apache/pulsar-test-infra/pull/69
### Motivation
1. Fix #59
2. Add tests to cover this feature
### Verify
I verified this on my repo, please help verify the following case on your
repo if you have time, th
Hi all,
I will merge https://github.com/apache/pulsar/pull/17270 first and draft a
proposal for
the detailed PIP process changes. And will start a new VOTE thread for the
PIP process change.
After the proposal(for PIP process change) is approved. I will go back here
to discuss
how to migrate the
+1
I have completed the proposal review on the gdoc.
But unfortunately, that is an internal google driver which not able to
create
public links.
Cong has copied to a new one.
Thanks,
Penghui
On Mon, Aug 29, 2022 at 6:37 PM Cong Zhao wrote:
> Hi Pulsar Community,
>
> In order to facilitate com
Good reiteration of the problem and good points, Asaf.
I'd like to add a new aspect to the proposal: there might be other
solutions that would be useful in the case of large amount of topics in a
Pulsar cluster.
Rate limiting on the /metrics endpoint doesn't sound like the correct
approach.
When
Hi Pulsar Community,
In order to facilitate community review, I copied this proposal to Google Docs,
please review it and complete the vote.
PIP:
https://docs.google.com/document/d/17HE88w4WuEsLoz0DExPpRN555UC_Tc3MEIKckVWksDc/edit
On 2022/08/08 06:51:31 Cong Zhao wrote:
> Hi Pulsar Community,
Hi Jiuming,
I would reiterate the problem statement to make it clear (at least for me):
There are cases where a very large amount of topics exists (> 10k per
broker) and are used in Pulsar. Those topics usually have multiple
producers and multiple consumers.
There are metrics that are in the gran
=== Motivation
Now, when a version-data of schema is lost, all schema data for that topic
will be deleted. see:
https://github.com/apache/pulsar/blob/0e149ef0484755d42e214f03003237299433c89a/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/schema/SchemaRegistryServiceImpl.java#L527-L565
GitHub user Anonymitaet added a comment to the discussion: How to Make
Contributions to Pulsar Documentation and Website?
Thanks for raising this up!
The [Pulsar Contribution Guide](https://pulsar.apache.org/contributing/) lists
all the following guides explaining how to make contributions to
GitHub user Anonymitaet edited a discussion: [Design] Pulsar Release Timeline
Page
Hi team,
Currently, we do not have a place showing the timeline for all Pulsar releases.
How about creating a Pulsar [Release Notes >
Timeline](https://pulsar.apache.org/release-notes/timeline) page along with
GitHub user Anonymitaet edited a discussion: [Design] Pulsar Release Timeline
Page
Hi team,
Currently, we do not have a place showing the timeline for all Pulsar releases.
How about creating a Pulsar [Release Notes >
Timeline](https://pulsar.apache.org/release-notes/timeline) page along with
Hi all,
In case someone missed the first message in this thread, it can be read at
https://lists.apache.org/thread/tvco1orf0hsyt59pjtfbwoq0vf6hfrcj .
The intention is to start discussions about improving Apache Pulsar design
in Pulsar 3.0 . This seems to be the first time that we are discussing
P
GitHub user Huanli-Meng created a discussion: How to Make Contributions to
Pulsar Documentation and Website?
Hi team,
I want to update Pulsar documentation and website, are there any guides to
reference or standards to follow?
Thank you!
GitHub link: https://github.com/apache/pulsar/discussio
GitHub user Anonymitaet created a discussion: [New Site Design] Pulsar
Reference + Pulsar CLI + Pulsar Configuration
Hi team,
We're implementing [PIP 78: Generate Docs from Code
Automatically](https://docs.google.com/spreadsheets/d/1P6tePGmU1lEhGKY_hE3JWgJ1rUTBCmW7AshDICJZr3o/edit#gid=1030826
55 matches
Mail list logo
