GitHub user dineshkothuru2020 created a discussion: Namespace isolation policy
:: No broker was available to own persistent
Appreciate your help to resolve this issues:
Thanks in Advance :-)
Created an single plusar cluster setup with four broker services running on
four different servers,
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
this is how the summary from link above looks like:
GitHub link:
https://git
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
some details:
GitHub link:
https://github.com/apache/pulsar/discussions/18754
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
would be very interesting to see, how an updated helm chart with
- latest pulsar image (2.9.3 -> 2.10.1 or even 2.11)
https://github.com/apache/pulsar
- latest prometheus image (2.17.2 -> 2.39.1)
https
GitHub user eolivelli added a comment to the discussion: Arguments for "why
pulsar is secure?"
@hpvd thanks for opening this issue. I think that your point is really valid.
I think that it is appropriate to start this discussion on the mailing lists
(dev@pulsar.apache.org), as that's the pla
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
before writing this issue, I had a conversation with Apache Security team,
that it is no problem to contribute this as normal issue:
> we'd warmly welcome if you'd contribute this finding as a norma
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
@eolivelli thanks for your comment.
Just opened an issue also in the repository of pulsars helm chart:
https://github.com/apache/pulsar-helm-chart/issues/294
GitHub link:
https://github.com/apache/pulsa
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
just as background info, the security scanner used by artifacthub, providing
results shown above
is trivy, **so all the finding should be pretty valid**.
For details, see:
https://artifacthub.io/docs/top
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
there is also an easy to use **github action for scanning with trivy**
- the complete repository,
- pull requests,
- docker container
- IaC
- etc.
=> Maybe this is interesting to integrate this directl
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
number of vulnerabilities is still growing:
Today images in Pulsars helm chart crosses the 1k:
**1005 vulnerabilities (683 fixable) have been detected in this package's
images**.
see https://artifacthub.
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
Latest security analysis show
- a stunning step in reducing the number of included vulnerabilities (minus
85%!)
- v2.9.4 with pulsar 2.9.3 **1024 vulnerabilities (698 fixable) have been
detected in thi
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
- on the other hand
- the number of fixable vulnerabilities with a severity of CRITICAL has risen
from 1 to 4 (plus 300%!)
![2022-11-04_10h05_52](https://user-images.githubusercontent.com/5681880/1999
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
-
- very old fixable and already reported vulnerabilities (up to 9 years old)
are still included in pulsar image:
![2022-11-04_09h21_54](https://user-images.githubusercontent.com/5681880/199937604-
GitHub user hpvd added a comment to the discussion: Arguments for "why pulsar
is secure?"
new Helm chart v 3.0 on the base of Pulsar 2.10.2 was just released:
https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.0.0
GitHub link:
https://github.com/apache/pulsar/discussions/18754
GitHub user github-actions[bot] added a comment to the discussion: Arguments
for "why pulsar is secure?"
The issue had no activity for 30 days, mark with Stale label.
GitHub link:
https://github.com/apache/pulsar/discussions/18754#discussioncomment-4321248
This is an automatically sent
GitHub user sfescape created a discussion: websocket feature parity
Is there a roadmap that discusses websocket features? It looks like websockets
is pretty far behind in feature parity.
I'm considering moving from kafka to pulsar but topics regex consumer is an
important feature for me.
Git
GitHub user hpvd added a comment to the discussion: websocket feature parity
for latest state see:
https://github.com/apache/pulsar/wiki/Client-Features-Matrix
GitHub link:
https://github.com/apache/pulsar/discussions/18756#discussioncomment-4321273
This is an automatically sent email f
GitHub user hpvd added a comment to the discussion: websocket feature parity
imho websocket is for pulsar something like "the window to the web world". It
enables usage of pulsar for fields like web-tracking, live chat and many more...
If one see the potential of this community, one should give
GitHub user hpvd added a comment to the discussion: websocket feature parity
feature parity would indeed be pretty awesome and would imho help adoption
further
GitHub link:
https://github.com/apache/pulsar/discussions/18756#discussioncomment-4321272
This is an automatically sent email f
GitHub user jiazhai created a discussion: Provide documentation for python
end-to-end messagecrypto
in issue #6834, user report there is no doc for configure and use feature
end-to-end messagecrypto in python.
We need to confirm whether this feature is supported in python, and add needed
doc.
GitHub user Huanli-Meng added a comment to the discussion: Provide
documentation for python end-to-end messagecrypto
@jiazhai , whether end-to-end messagecrypto is supported on Python?
GitHub link:
https://github.com/apache/pulsar/discussions/18757#discussioncomment-4321320
This is an a
GitHub user BewareMyPower added a comment to the discussion: Provide
documentation for python end-to-end messagecrypto
Here is a test that shows how to use e2e encryption:
https://github.com/apache/pulsar-client-python/blob/9182dd7ab69266ad0fb630a129a3ef478c1f8ab0/tests/pulsar_test.py#L369
Gi
GitHub user tisonkun added a comment to the discussion: Provide documentation
for python end-to-end messagecrypto
cc @BewareMyPower @shibd @RobertIndie what's the current status of this feature?
GitHub link:
https://github.com/apache/pulsar/discussions/18757#discussioncomment-4321322
Th
GitHub user jiazhai edited a discussion: How to do end-to-end messagecrypto
with Python client
in issue #6834, user report there is no doc for configure and use feature
end-to-end messagecrypto in python.
We need to confirm whether this feature is supported in python, and add needed
doc.
Gi
GitHub user devdattakulkarni added a comment to the discussion: Provide
documentation for python end-to-end messagecrypto
@jiazhai We are also interested in this. Do you know if this is already
supported and just the documentation is missing, or if this feature is yet to
be supported in the P
GitHub user tisonkun added a comment to the discussion: Provide documentation
for python end-to-end messagecrypto
@BewareMyPower Thank you! I'll convert this thread to a Q&A and select the
answer.
Further improvement to add the example to
https://pulsar.apache.org/docs/client-libraries-pytho
GitHub user beyondyinjl2 added a comment to the discussion: Is there any
development documentation for the authentication and authorization plug-in, and
what is the address?
I have read the document you mentioned, but I don’t know the role of each
interface, the loading process, and the flow
GitHub user codelipenghui added a comment to the discussion: Is there any
development documentation for the authentication and authorization plug-in, and
what is the address?
The issue had no activity for 30 days, mark with Stale label.
GitHub link:
https://github.com/apache/pulsar/discussio
GitHub user beyondyinjl2 created a discussion: Is there any development
documentation for the authentication and authorization plug-in, and what is the
address?
Is there any development documentation for the authentication and authorization
plug-in, and what is the address?
GitHub link: http
GitHub user Anonymitaet added a comment to the discussion: Is there any
development documentation for the authentication and authorization plug-in, and
what is the address?
Hi @beyondyinjl2 thanks for your question. Before raising an issue, please make
sure you have investigated it thoroughly
GitHub user github-actions[bot] added a comment to the discussion: Wishing
list: optimize blog page
The issue had no activity for 30 days, mark with Stale label.
GitHub link:
https://github.com/apache/pulsar/discussions/18759#discussioncomment-4321585
This is an automatically sent email
Hello, everyone.
I'd like to start the discussion about `Remove restful producer component`. The
Github repository path is here[1].
As discussed before[2], moving this feature to another project is better. Also,
we didn't provide the consumer part in the pulsar repo. I think it's a good
chanc
GitHub user Jennifer88huang-zz created a discussion: How to run Pulsar Function
in K8S
**Describe the bug**
My Pulsar function using State Storage (written in Python ) is working
perfectly in Docker Container, but the same code is not working on Kubernetes.
Can u please help me on that? Is th
GitHub user Jennifer88huang-zz added a comment to the discussion: How to run
Pulsar Function in K8S
@nlu90 are you familiar with K8S? Could you please give a hand on it? Thank you
very much.
GitHub link:
https://github.com/apache/pulsar/discussions/18761#discussioncomment-4321837
This
GitHub user codelipenghui added a comment to the discussion: How to run Pulsar
Function in K8S
The issue had no activity for 30 days, mark with Stale label.
GitHub link:
https://github.com/apache/pulsar/discussions/18761#discussioncomment-4321838
This is an automatically sent email for
GitHub user KannarFr created a discussion: Pulsar SQL: support user defined
indexes
**Is your feature request related to a problem? Please describe.**
Currently, there is no index used to query topic using presto.
`__publish_time__` can be considered as index because of ledger storage way but
GitHub user KannarFr added a comment to the discussion: Pulsar SQL: support
user defined indexes
And how can we handle it on offloaded parts?
GitHub link:
https://github.com/apache/pulsar/discussions/18763#discussioncomment-4321904
This is an automatically sent email for dev@pulsar.apac
GitHub user sijie added a comment to the discussion: Pulsar SQL: support user
defined indexes
@KannarFr
The indexes can be built in a background process using the approach that was
used for compaction. The "compacted" ledger is essentially an "index" to the
original data.
The index maintai
GitHub user KannarFr added a comment to the discussion: Pulsar SQL: support
user defined indexes
Adding the index definition into schema definition but maybe it is not the best
to do. I'm asking your opinion.
GitHub link:
https://github.com/apache/pulsar/discussions/18763#discussioncomment-4
GitHub user sijie added a comment to the discussion: Pulsar SQL: support user
defined indexes
Are you talking about adding the index definition into schema definition? Or
using Avro schema specification for describing the indexes?
GitHub link:
https://github.com/apache/pulsar/discussions/187
GitHub user KannarFr added a comment to the discussion: Pulsar SQL: support
user defined indexes
@sijie
Ok, about the indexes definition, what do you think about the definition
approach using avroschema to define indexes?
GitHub link:
https://github.com/apache/pulsar/discussions/18763#discu
GitHub user sijie added a comment to the discussion: Pulsar SQL: support user
defined indexes
I don't think it is a good idea to add an index definition to the schema
definition. The schema definition defines the structure of the original data.
The index definition depends on the schema defin
GitHub user pointearth added a comment to the discussion: Pulsar SQL: support
user defined indexes
I think user-defined indexes are very important for Pulsar SQL, it could be
able to be the real way that we can use pulsar as a database. I think it will
make pulsar more popular.
And I agree to
GitHub user KannarFr added a comment to the discussion: Pulsar SQL: support
user defined indexes
@pointearth @sijie How do you imagine the index composition regarding ledgers?
As the first implementation, regarding pub/sub system, timestamp index-based
would be a good start. I think we should
GitHub user KannarFr added a comment to the discussion: Pulsar SQL: support
user defined indexes
And where/how we store this index?
GitHub link:
https://github.com/apache/pulsar/discussions/18763#discussioncomment-4321912
This is an automatically sent email for dev@pulsar.apache.org.
T
GitHub user golden-yang added a comment to the discussion: Pulsar SQL: support
user defined indexes
Is there any progress on this issue?
Being able to support indexes in Pulsar Sql will be a very meaningful feature.
One way is to support it **natively**, and the other way I think it can be
a
GitHub user pointearth added a comment to the discussion: Pulsar SQL: support
user defined indexes
Can we store it in bookKeeper? and it may be able to start when the presto
enhancement switching is open.
GitHub link:
https://github.com/apache/pulsar/discussions/18763#discussioncomment-43219
GitHub user pointearth added a comment to the discussion: Pulsar SQL: support
user defined indexes
I know querying with timestamp is very fast, because data in bookKeeper save
timestamp as key.
My suggestion is to create a non-clustered index, based on the key in
bookKeeper, for example:
If w
GitHub user Hugues514 created a discussion: Pulsar SQL should support
readCompact on topics
So far, when a Pulsar topic is compacted, the Pulsar SQL query will read all
the records, not considering the compacted option
It could be interesting to be able to query such a topic using a readCompa
GitHub user longtengz added a comment to the discussion: Pulsar SQL should
support readCompact on topics
Does this also imply pulsar sql cannot process empty payload messages for the
time being? Because I'm experiencing #13127
GitHub link:
https://github.com/apache/pulsar/discussions/18764#
GitHub user jiazhai added a comment to the discussion: Pulsar SQL should
support readCompact on topics
We need a special handle in `PulsarSplitManager.getSplitsForTopic` to split
based also on `compactionHorizon`(contained in `CompactedTopicImpl`); so that
for data before compactionHorizon, w
GitHub user pointearth added a comment to the discussion: Pulsar SQL should
support readCompact on topics
Can you guys open this ticket and finish it or move it to a suitable
appointment? appreciate!
[Add readCompact option #7461](https://github.com/apache/pulsar/pull/7461 )
GitHub link:
htt
GitHub user jiazhai added a comment to the discussion: Pulsar SQL should
support readCompact on topics
more info:
https://github.com/apache/pulsar/wiki/PIP-19:-Pulsar-SQL
https://github.com/apache/pulsar/wiki/PIP-14:-Topic-compaction
GitHub link:
https://github.com/apache/pulsar/discussions
GitHub user tisonkun added a comment to the discussion: Pulsar SQL: support
user defined indexes
Moved to general discussions since there's a wishing list item and not
actionable.
GitHub link:
https://github.com/apache/pulsar/discussions/18763#discussioncomment-4321928
This is an autom
GitHub user KannarFr edited a discussion: Wishing list: Pulsar SQL support user
defined indexes
**Is your feature request related to a problem? Please describe.**
Currently, there is no index used to query topic using presto.
`__publish_time__` can be considered as index because of ledger sto
GitHub user Hugues514 edited a discussion: Wishing list: Pulsar SQL should
support readCompact on topics
So far, when a Pulsar topic is compacted, the Pulsar SQL query will read all
the records, not considering the compacted option
It could be interesting to be able to query such a topic usin
GitHub user tisonkun added a comment to the discussion: Wishing list: Pulsar
SQL should support readCompact on topics
Moved to general discussions since there's a wishing list item and no one works
on it now.
GitHub link:
https://github.com/apache/pulsar/discussions/18764#discussioncomment-4
GitHub user ivankelly created a discussion: Proxy should autodetect whether to
use TLS to connect brokers
Currently you need to set `tlsEnabledWithBroker` in the proxy to use TLS to
connect to brokers. However, if the URL is https:// or pulsar+ssl:// it should
be obvious that we should use TL
GitHub user waxzce created a discussion: Use graalVM native image to build
client and client admin
Using the pulsar-admin command can be very frustrating because of the startup
time. That's one point were graalVM native image is interesting: build a static
"binary".
Various problem to compil
GitHub user sijie added a comment to the discussion: Use graalVM native image
to build client and client admin
alternatively, you can now use
[pulsarctl](https://github.com/streamnative/pulsarctl). it is a static linked
CLI written in golang.
GitHub link:
https://github.com/apache/pulsar/di
GitHub user aahmed-se added a comment to the discussion: Use graalVM native
image to build client and client admin
I don't know how stable graalVM is last I checked it's still is an RC candidate
we might also need to look at other http client libs that support aot code
generation.
GitHub lin
GitHub user fantapsody added a comment to the discussion: Use graalVM native
image to build client and client admin
Pulsar itself should also be built with AOT compilers to reduce the time to
start the process. Sometimes it takes up to a minute to start the broker with
function worker enabled
GitHub user harissecic added a comment to the discussion: Use graalVM native
image to build client and client admin
> Broker will require many changes and unlikely it can be made to work with
> graalvm anytime soon. Client should not an issue it has a dependency on netty
> , but netty authors
GitHub user harissecic added a comment to the discussion: Use graalVM native
image to build client and client admin
I'm experiencing similar issues trying to make Micronaut integration for Pulsar
Java client is really hard mainly due to reflection and Micronaut now demands
that it can build f
GitHub user aahmed-se added a comment to the discussion: Use graalVM native
image to build client and client admin
Broker will require many changes and unlikely it can be made to work with
graalvm anytime soon. Client should not an issue it has a dependency on netty ,
but netty authors should
+1
And we should also remove the documentation of this part.
Penghui
> On Dec 6, 2022, at 18:36, mattisonc...@gmail.com wrote:
>
>
> Hello, everyone.
>
> I'd like to start the discussion about `Remove restful producer component`.
> The Github repository path is here[1].
>
> As discussed bef
+1
I agree that such kind of APIs can be on side projects
Enrico
Il giorno mar 6 dic 2022 alle ore 14:20 PengHui Li
ha scritto:
>
> +1
>
> And we should also remove the documentation of this part.
>
> Penghui
>
> > On Dec 6, 2022, at 18:36, mattisonc...@gmail.com wrote:
> >
> >
> > Hello, every
+1 (binding)
- verified checksums, digests
- built from sources
- tested the docker image built from sources and the docker image
provided as convenience with the VOTE
- run successfully the Jakarta JMS 2.0 TCK against those two docker images
My problem with the JMS TCK is that the behaviour of "d
GitHub user flowchartsman added a comment to the discussion: Golang | Pulsar
Functions Runtime Death Exception
This is unfortunately a pretty generic response. Debugging pulsar function
crashes in go can be kind of a pain, especially if they happen before
`pf.Start` is called, since there's n
GitHub user flowchartsman edited a comment on the discussion: Golang | Pulsar
Functions Runtime Death Exception
This is unfortunately a pretty generic response. Debugging pulsar function
crashes in go can be kind of a pain, especially if they happen before
`pf.Start` is called, since there's
GitHub user divya-nsurely added a comment to the discussion: Golang | Pulsar
Functions Runtime Death Exception
Thanks for your response.
The Create API returns a successful response. However, the function stops
running due to this Death Exception error.
When I try to restart the function, I
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little a little bit from trying to be too much like t
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little a little bit from trying to be too much like t
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little a little bit from trying to be too much like t
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little a little bit from trying to be too much like t
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little a little bit from trying to be too much like t
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little a little bit from trying to be too much like t
GitHub user woodsmur created a discussion: multiple topic sink to multiple
elasticsearch index
Hi,
Is there a way to send data from multiple topic to different elasticsearch
indices? For example, if I have `t-2020.12.01` and `t-2020.12.02`, how could I
consume these two topics and create two
GitHub user hpvd added a comment to the discussion: multiple topic sink to
multiple elasticsearch index
yes this would be helpful in many cases of bigger installations.
At this time doc is only talking about "singular"
https://pulsar.apache.org/docs/en/io-elasticsearch/
Problem and possible r
GitHub user zymap added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
Do you want this?
https://pulsar.apache.org/docs/concepts-messaging#acknowledgement
GitHub link:
https://github.com/apache/pulsar/discussions/18771#discussioncomment-4324377
Thi
GitHub user startjava added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
> Do you want this?
> https://pulsar.apache.org/docs/concepts-messaging#acknowledgement
YES，i see the doc too .
GitHub link:
https://github.com/apache/pulsar/discussions/18771#di
GitHub user startjava added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
@momo-jun
question1：
why
（1）individually (in Shared and Key_Shared subscription types)
（2）cumulatively (Exclusive and Failover subscription types).
why bottom is error：
（1）cumula
GitHub user startjava added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
@momo-jun please see the question
GitHub link:
https://github.com/apache/pulsar/discussions/18771#discussioncomment-4324379
This is an automatically sent email for dev@pulsa
GitHub user momo-jun added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
> Messages are negatively acknowledged individually or cumulatively, depending
> on the consumption subscription type.
> * In Exclusive and Failover subscription types, consumers onl
GitHub user momo-jun added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
> but i don't know what mean "negatively acknowledged cumulatively"。
You can understand it as "Cumulative NACK" - the negative acknowledgement is
performed cumulatively, that is, co
GitHub user labuladong added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
You can try `negativeAcknowledge` in `Failover/Exclusive` subscription types.
All the messages the consumer didn't acknowledge will be redelivered, this
behavior could be negative
GitHub user startjava added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
Actually I want to know what situation belongs to "the acknowledged
cumulatively"?
thank you !
GitHub link:
https://github.com/apache/pulsar/discussions/18771#discussioncomment-43
GitHub user startjava added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
but i don't know what mean "negatively acknowledged cumulatively"。
GitHub link:
https://github.com/apache/pulsar/discussions/18771#discussioncomment-4324383
This is an auto
GitHub user tisonkun added a comment to the discussion: [Doc] "negatively
acknowledged cumulatively" ambiguous?
This is about knowledge sharing. Not an issue to resolve.
GitHub link:
https://github.com/apache/pulsar/discussions/18771#discussioncomment-4324394
This is an automatically se
GitHub user flowchartsman added a comment to the discussion: Go Function SDK
Feature Parity
Please comment with any other issues you feel like you need to track, and they
can be added to the master list above.
GitHub link:
https://github.com/apache/pulsar/discussions/18768#discussioncomment-
GitHub user codelipenghui created a discussion: Dataset by pulsar functions
When use pulsar functions, The ending strategy of consume messages is useful in
dataset scenes.
Such as:
1. Ending by message produce time.
2. Ending by message id.
3. Ending by user(user support the ending strategy).
GitHub user srkukarni added a comment to the discussion: Dataset by pulsar
functions
This feature indeed make sense. Is it possible for you to to volunteer to add
this functionality?
GitHub link:
https://github.com/apache/pulsar/discussions/18773#discussioncomment-4327675
This is an au
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little bit from trying to be too much like the Java v
GitHub user flowchartsman edited a discussion: Go Function SDK Feature Parity
The Pulsar functions for Go SDK needs some love. It is lacking in some key
features and has a couple of rough edges. Broadly, I think the SDK has been
held back a little bit from trying to be too much like the Java v
GitHub user flowchartsman added a comment to the discussion: Go Function SDK
Feature Parity
### Pre-function init
Most things available from the function context such as tenant, namespace, etc
should be available without needing the function context. This exists for user
config, and should e
GitHub user flowchartsman added a comment to the discussion: Go Function SDK
Feature Parity
### Depencency-free logging
A [new standard, leveling logger](https://pkg.go.dev/golang.org/x/exp/slog)
will likely be landing in the standard library in the next few versions.
Switching to this will
GitHub user flowchartsman edited a comment on the discussion: Go Function SDK
Feature Parity
### Pre-function init
Most things available from the function context such as tenant, namespace, etc
should be available without needing the function context. This exists for user
config, and should
GitHub user Anonymitaet added a comment to the discussion: [Website + Doc]
generate connector configuration info automatically
Why close this issue? What are the criteria for keeping an issue open or
closed?
GitHub link:
https://github.com/apache/pulsar/discussions/18776#discussioncomment-4
GitHub user github-actions[bot] added a comment to the discussion: [Website +
Doc] generate connector configuration info automatically
The issue had no activity for 30 days, mark with Stale label.
GitHub link:
https://github.com/apache/pulsar/discussions/18776#discussioncomment-4328568
GitHub user tisonkun added a comment to the discussion: [Website + Doc]
generate connector configuration info automatically
Closed as stale and no progress.
GitHub link:
https://github.com/apache/pulsar/discussions/18776#discussioncomment-4328570
This is an automatically sent email for
1 - 100 of 172 matches
Mail list logo
