BewareMyPower commented on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618794964
The problem may be the strange value (538973717) of `readIdx_` 。Could you
provide the `payload` info of each frame?
Following is the lifetime of `payload` (if I don't
BewareMyPower commented on pull request #6812:
URL: https://github.com/apache/pulsar/pull/6812#issuecomment-618793369
/pulsarbot run unit-tests
This is an automated message from the Apache Git Service.
To respond to the
jiazhai commented on a change in pull request #4848:
URL: https://github.com/apache/pulsar/pull/4848#discussion_r414277906
##
File path:
pulsar-client/src/main/java/org/apache/pulsar/client/impl/MessageImpl.java
##
@@ -270,7 +270,11 @@ public T getValue() {
zplinuxlover commented on pull request #6775:
URL: https://github.com/apache/pulsar/pull/6775#issuecomment-618786237
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
zplinuxlover commented on pull request #6775:
URL: https://github.com/apache/pulsar/pull/6775#issuecomment-618786155
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
zplinuxlover commented on pull request #6775:
URL: https://github.com/apache/pulsar/pull/6775#issuecomment-618786115
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the
hangc0276 commented on pull request #6776:
URL: https://github.com/apache/pulsar/pull/6776#issuecomment-618784699
> @hangc0276 Good catch! @wolfstudy could please help take a look the last
comment? maybe you need to move the `messageId` to the end of params list.
Thanks for your
BewareMyPower commented on pull request #6812:
URL: https://github.com/apache/pulsar/pull/6812#issuecomment-618779875
/pulsarbot run cpp-tests
This is an automated message from the Apache Git Service.
To respond to the
wolfstudy commented on pull request #6776:
URL: https://github.com/apache/pulsar/pull/6776#issuecomment-618775410
![image](https://user-images.githubusercontent.com/20965307/80170680-156e2380-861b-11ea-9bb1-d1bf3627df91.png)
@hangc0276 @codelipenghui Thanks feedback, fixed done,
wolfstudy removed a comment on pull request #6776:
URL: https://github.com/apache/pulsar/pull/6776#issuecomment-618772842
![image](https://user-images.githubusercontent.com/20965307/80169997-89a7c780-8619-11ea-8cd9-b31b386688a0.png)
Thanks @hangc0276 feedback, fixed done, PTAL again
codelipenghui commented on issue #6811:
URL: https://github.com/apache/pulsar/issues/6811#issuecomment-618775036
close via #6759
This is an automated message from the Apache Git Service.
To respond to the message, please log
BewareMyPower opened a new pull request #6812:
URL: https://github.com/apache/pulsar/pull/6812
### Motivation
After commit of [#4817](https://github.com/apache/pulsar/pull/4811), the
send callback's 2nd argument became `MessageId`, but the `MessageId` in
callback is always the
wolfstudy commented on pull request #6776:
URL: https://github.com/apache/pulsar/pull/6776#issuecomment-618772842
![image](https://user-images.githubusercontent.com/20965307/80169997-89a7c780-8619-11ea-8cd9-b31b386688a0.png)
Thanks @hangc0276 feedback, fixed done, PTAL again
codelipenghui opened a new issue #6811:
URL: https://github.com/apache/pulsar/issues/6811
**Describe the bug**
![image](https://user-images.githubusercontent.com/12592133/80169049-fd94a080-8616-11ea-9f9e-e3337be35286.png)
tuteng opened a new pull request #6034:
URL: https://github.com/apache/pulsar/pull/6034
Fixes #5633
### Motivation
Currently, some users want to support Avro schema in debezium, so this pr
supports this feature.
For Kafka's Avro schema, it depends on the Avro 1.8
codelipenghui commented on pull request #6776:
URL: https://github.com/apache/pulsar/pull/6776#issuecomment-618764842
@hangc0276 Good catch! @wolfstudy could please help take a look the last
comment? maybe you need to move the `messageId` to the end of params list.
Anonymitaet commented on a change in pull request #6763:
URL: https://github.com/apache/pulsar/pull/6763#discussion_r414238608
##
File path: site2/docs/security-encryption.md
##
@@ -144,11 +148,12 @@ for (int i = 0; i < 10; i++) {
// Acknowledge the consumption of all
KannarFr commented on a change in pull request #6799:
URL: https://github.com/apache/pulsar/pull/6799#discussion_r414239613
##
File path:
pulsar-broker-common/src/main/java/org/apache/pulsar/broker/authentication/AuthenticationService.java
##
@@ -83,13 +83,29 @@ public String
merlimat opened a new pull request #6810:
URL: https://github.com/apache/pulsar/pull/6810
### Motivation
The subscription `InitialPosition` is not currently set when using the
multi-topic or regex consumers in C++/Python.
That makes that if you try to start from
sijie commented on issue #6807:
URL: https://github.com/apache/pulsar/issues/6807#issuecomment-618704820
Yes, I think Token Authentication Provider is not serializable. Use
configuration to pass the auth plugins and params are the recommended way.
sijie commented on issue #6809:
URL: https://github.com/apache/pulsar/issues/6809#issuecomment-618703430
@qmnonic
The `v2` endpoint still takes a serialized json string of FunctionConfig:
`/admin/v3/functions/{tenant}/{namespace}/{functionName} `
There was a change in
frankjkelly opened a new issue #233:
URL: https://github.com/apache/pulsar-client-go/issues/233
Expected behavior
Tell us what should happen:
When creating a new topic - the consumer should be able to receive the first
message
Actual behavior
Tell us what
cdbartholomew commented on issue #6809:
URL: https://github.com/apache/pulsar/issues/6809#issuecomment-618693846
@qmnonic I am not sure if this is helpful, but I am able to upload functions
via the REST API in versions 2.4.2 to 2.5.1 using this JavaScript code:
```
createFunction
qmnonic opened a new issue #6809:
URL: https://github.com/apache/pulsar/issues/6809
**Describe the bug**
Seems there was a change in the
https://pulsar.apache.org/admin/v3/functions/{tenant}/{namespace}/{functionName}
function, where the method signature changed, specifically the
merlimat commented on pull request #6796:
URL: https://github.com/apache/pulsar/pull/6796#issuecomment-618600371
> acknowledgementCumulative on a partitioned topic means acknowledging
cumulative the messages of the partition inferred by the MessageId.
If I'm consuming from a
merlimat opened a new pull request #6808:
URL: https://github.com/apache/pulsar/pull/6808
### Motivation
In Python client, the serialization of enums when using the schema is
currently broken, throwing error because it's not possible to directly
serialize them into json.
gaoran10 commented on issue #6034:
URL: https://github.com/apache/pulsar/pull/6034#issuecomment-618533772
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
merlimat commented on issue #6791:
URL: https://github.com/apache/pulsar/pull/6791#issuecomment-618531886
> I see there is a problem in the current algorithm when scaling down the
number of consumers. But I don't think its broken.
The Key Shared subscriptions has 2 stated goals:
addisonj commented on issue #6800:
URL: https://github.com/apache/pulsar/pull/6800#issuecomment-618502915
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
addisonj commented on issue #6801:
URL: https://github.com/apache/pulsar/pull/6801#issuecomment-618503075
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
merlimat commented on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618497703
> This only covers 50% of the contract. If a reader is scanning a log, it
should receive events in order and there are no data gaps.
That's not what the contract is. And it's
addisonj commented on issue #6801:
URL: https://github.com/apache/pulsar/pull/6801#issuecomment-618461858
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
addisonj commented on issue #6800:
URL: https://github.com/apache/pulsar/pull/6800#issuecomment-618461247
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
bschofield edited a comment on issue #6785:
URL: https://github.com/apache/pulsar/issues/6785#issuecomment-618379476
These are not quite the same bug. The problem with the go/C client is that
there is no way to set the topic name in a message ID, whereas the problem with
the Java library
bschofield edited a comment on issue #6785:
URL: https://github.com/apache/pulsar/issues/6785#issuecomment-618379476
These are not quite the same bug. The problem with the go/C client is that
there is no way to set the topic name in a message ID, whereas the problem with
the Java library
why198852 commented on issue #6807:
URL: https://github.com/apache/pulsar/issues/6807#issuecomment-618393481
good idea,Mr qianmoQ.
This is an automated message from the Apache Git Service.
To respond to the message, please
qianmoQ edited a comment on issue #6807:
URL: https://github.com/apache/pulsar/issues/6807#issuecomment-618388237
I don't recommend using it this way because it can cause serialization
problems
`public class ClientConfigurationData implements Serializable`
source code
qianmoQ edited a comment on issue #6807:
URL: https://github.com/apache/pulsar/issues/6807#issuecomment-618388237
I don't recommend using it this way because it can cause serialization
problems
`public class ClientConfigurationData implements Serializable`
source code
qianmoQ edited a comment on issue #6807:
URL: https://github.com/apache/pulsar/issues/6807#issuecomment-618388237
I don't recommend using it this way because it can cause serialization
problems
please init client For example:
```java
val confData = new
qianmoQ edited a comment on issue #6807:
URL: https://github.com/apache/pulsar/issues/6807#issuecomment-618388237
I don't recommend using it this way because it can cause serialization
problems
please init client egg:
```java
val confData = new ClientConfigurationData()
qianmoQ commented on issue #6807:
URL: https://github.com/apache/pulsar/issues/6807#issuecomment-618388237
I don't recommend using it this way because it can cause serialization
problems
please init client :
```java
val confData = new ClientConfigurationData()
cbornet edited a comment on issue #6720:
URL: https://github.com/apache/pulsar/pull/6720#issuecomment-617403363
The change is already in this PR. I did it in the 2nd commit. The interface
to implement by protocol handlers is `ServerCnx`.
bschofield commented on issue #6785:
URL: https://github.com/apache/pulsar/issues/6785#issuecomment-618379476
These are not quite the same bug. The problem with the go/C client is that
there is no way to set the topic name in a message ID, whereas the problem with
the Java library is that
wangyunpeng666 opened a new issue #6807:
URL: https://github.com/apache/pulsar/issues/6807
when I consume topic by sparkstreming with token ,it meet errors. The code
and error is as follows:
bschofield edited a comment on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618298060
Here are the DEBUG messages from the C++ library immediately before the
crash:
```
DEBUG [x.x.x.x:46978 -> y.y.y.y:29841] Received a message from the server
for
zplinuxlover commented on issue #6758:
URL: https://github.com/apache/pulsar/pull/6758#issuecomment-618299158
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
zplinuxlover commented on issue #6783:
URL: https://github.com/apache/pulsar/pull/6783#issuecomment-618298816
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
zplinuxlover commented on issue #6783:
URL: https://github.com/apache/pulsar/pull/6783#issuecomment-618298669
/pulsarbot run-failure-checks
This is an automated message from the Apache Git Service.
To respond to the message,
bschofield commented on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618298060
Here are the DEBUG messages from the C++ library immediately before the
crash:
```
DEBUG [x.x.x.x:46978 -> y.y.y.y:29841] Received a message from the server
for
bschofield removed a comment on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618297295
Here are the DEBUG messages from the C++ library immediately before the
crash:
```
DEBUG [192.168.2.191:46978 -> 51.79.31.254:29841] Received a message from
the
bschofield commented on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618297295
Here are the DEBUG messages from the C++ library immediately before the
crash:
```
DEBUG [192.168.2.191:46978 -> 51.79.31.254:29841] Received a message from
the server
bschofield removed a comment on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618291497
Here are the DEBUG messages from the C++ library, immediately before the
segfault:
```
DEBUG [192.168.2.191:46978 -> 51.79.31.254:29841] Received a message from
bschofield edited a comment on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618291497
Here are the DEBUG messages from the C++ library, immediately before the
segfault:
```
DEBUG [192.168.2.191:46978 -> 51.79.31.254:29841] Received a message from
bschofield commented on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618291497
Here's a dump of 489 bytes starting at `uncompressedPayload.ptr_`:
```
(gdb) xxd uncompressedPayload.ptr_ 489
: 2020 1611 5b7f 2020 1611 5b7f
sijie commented on issue #6791:
URL: https://github.com/apache/pulsar/pull/6791#issuecomment-618267027
> The current implementation is severely broken. This PR is fixing the bug.
I don't see an easy way to fix it based on the splitting range design.
I see there is a problem in the
sijie edited a comment on issue #6791:
URL: https://github.com/apache/pulsar/pull/6791#issuecomment-618267027
> The current implementation is severely broken. This PR is fixing the bug.
I don't see an easy way to fix it based on the splitting range design.
I see there is a problem
bschofield commented on issue #6806:
URL: https://github.com/apache/pulsar/issues/6806#issuecomment-618262902
If we go up a stack frame, then `uncompressedPayload` looks pretty suspect
to me: it has `readIdx_` much larger than `capacity_`, which doesn't seem right:
```
(gdb) up
sijie commented on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618259435
> The contract is clear and it's that a reader can read all the data that is
being retained based on max time and size.
This only covers 50% of the contract. If a reader is
bschofield opened a new issue #6806:
URL: https://github.com/apache/pulsar/issues/6806
I am using the go client, which is a wrapper around the C++ client. I
encountered a bug where all my consumers on a namespace suddenly died and could
not be restarted. It seems that they are segfaulting
sijie commented on issue #6796:
URL: https://github.com/apache/pulsar/pull/6796#issuecomment-618248226
@BewareMyPower @merlimat
The `MessageId` is used for identifying the position within a topic. For a
partitioned topic, the `MessageId` includes the partition index for identifying
sijie commented on a change in pull request #6799:
URL: https://github.com/apache/pulsar/pull/6799#discussion_r413589283
##
File path:
pulsar-broker-common/src/main/java/org/apache/pulsar/broker/authentication/AuthenticationService.java
##
@@ -83,13 +83,29 @@ public String
This is an automated email from the ASF dual-hosted git repository.
sijie pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git.
from 550f155 Add apache pulsar 2.5.1 blog (#6805)
add 53407fc Fix some empty message related problems in the
This is an automated email from the ASF dual-hosted git repository.
sijie pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git.
from fb6e43a [hotfix]Website publish failed for ko language (#6803)
add 550f155 Add apache pulsar 2.5.1 blog
itaross edited a comment on issue #6797:
URL: https://github.com/apache/pulsar/issues/6797#issuecomment-618232785
I have used a json field "retainOrdering" as written here
itaross commented on issue #6797:
URL: https://github.com/apache/pulsar/issues/6797#issuecomment-618232785
I have used a json field "retainOrdering" as written here
https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/SinksBase.java
merlimat commented on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618228354
> The behavior of a non-durable cursor reading a managed ledger should be
close to the behavior of a file reader reading a file in the filesystem. If a
reader is actively reading a
merlimat commented on issue #6791:
URL: https://github.com/apache/pulsar/pull/6791#issuecomment-618223059
> Since the current algorithm has been used in many production environments
already, we should be concerned about removing an existing implementation.
Providing a way to opt-in a
shiv4289 commented on issue #6782:
URL: https://github.com/apache/pulsar/pull/6782#issuecomment-618217216
> @shiv4289 - did you remember which Authentication is not serializable in
#4283?
@rdhabalia @sijie AuthenticationToken.java
tuteng commented on issue #6805:
URL: https://github.com/apache/pulsar/pull/6805#issuecomment-618207811
@Huanli-Meng PTAL
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
jerrypeng edited a comment on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618205635
@sijie the default behavior of stored data in pulsar is not exactly the same
as data stored in a file. By default data is not persisted in Pulsar at all.
Only if a topic has
jerrypeng edited a comment on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618205635
@sijie the default behavior of stored data in pulsar is not exactly the same
as data stored in a file. By default data is not persisted in Pulsar at all.
Only if a topic has
jerrypeng edited a comment on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618205635
@sijie the default behavior of stored data in pulsar is not exactly the same
as data stored in a file. By default data is not persisted in Pulsar at all.
Only if a topic has
tuteng opened a new pull request #6805:
URL: https://github.com/apache/pulsar/pull/6805
### Motivation
* Add apache pulsar 2.5.1 features blog
### Modifications
* Add apache pulsar 2.5.1 features blog
jerrypeng edited a comment on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618205635
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
jerrypeng edited a comment on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618205635
@sijie the default behavior of stored data in pulsar is not exactly the same
as data stored in a file. By default data is not persisted in Pulsar at all.
Only if a topic has
jerrypeng commented on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618205635
@sijie the default behavior of stored data in pulsar is not exactly the same
as data in a file. By default data is not persisted in Pulsar at all. Only if
a topic has a
This is an automated email from the ASF dual-hosted git repository.
sijie pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git.
from 5542126 Fixed website publish failed (#6802)
add fb6e43a [hotfix]Website publish failed for ko language
Huanli-Meng commented on issue #6804:
URL: https://github.com/apache/pulsar/pull/6804#issuecomment-618201728
close the
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
sijie commented on issue #6798:
URL: https://github.com/apache/pulsar/pull/6798#issuecomment-618200536
> Tenant admin has the ability to produce/consume. This is honored by the
http api, but not the binary api.
I am confused by this statement. Http doesn't provide any ability to
sijie commented on a change in pull request #6798:
URL: https://github.com/apache/pulsar/pull/6798#discussion_r413535462
##
File path:
pulsar-broker/src/main/java/org/apache/pulsar/broker/service/ServerCnx.java
##
@@ -935,6 +937,38 @@ private SchemaData
codelipenghui commented on issue #6554:
URL: https://github.com/apache/pulsar/issues/6554#issuecomment-618198792
@merlimat I like the approach you have mentioned.
This is an automated message from the Apache Git Service.
To
Huanli-Meng opened a new pull request #6804:
URL: https://github.com/apache/pulsar/pull/6804
*(If this PR fixes a github issue, please add `Fixes #`.)*
Fixes #
*(or if this PR is one task of a github issue, please add `Master Issue:
#` to link to the master issue.)*
sijie commented on issue #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-618196829
@jerrypeng @merlimat I think this should be a flag to allow people to choose
whether to include readers for backlog quota consideration or not. The behavior
of a non-durable cursor
phemmer commented on issue #6790:
URL: https://github.com/apache/pulsar/issues/6790#issuecomment-618196763
Unfortunately not. I do not know Java at all. Otherwise I probably would as
I'm sure it's a simple change.
This is
84 matches
Mail list logo