JetStream CreateOrUpdateConsumerAsync throw NatsJSApiException if FilterSubject contains '.'

[eddyyuen]

Observed behavior

When my code like this

var consumer = await _natsJSStream.CreateOrUpdateConsumerAsync(new ConsumerConfig()
 {
     FilterSubject = "a.b.c"
 });

Throw Exception:

NATS.Client.JetStream.NatsJSApiException:“Consumer create request did not match filtered subject from create subject”

If we use this code ,it works

var consumer = await _natsJSStream.CreateOrUpdateConsumerAsync(new ConsumerConfig()
{
    FilterSubject = "a_b_c"
});

Expected behavior

FilterSubject should be able to input any character

Server and client version

nats-server: v2.10.11 (widows amd64)
NATS.Net 2.1.3

Host environment

No response

Steps to reproduce

This throw Exception

 var config = new StreamConfig(name: "test", subjects: new[] {
     "a.b.c"
 });
 _natsJSStream = await _natsJSContext.CreateStreamAsync(config);
var consumer = await _natsJSStream.CreateOrUpdateConsumerAsync(new ConsumerConfig()
 {
     FilterSubject = "a.b.c"
 });

It works:

 var config = new StreamConfig(name: "test", subjects: new[] {
     "a_b_c"
 });
 _natsJSStream = await _natsJSContext.CreateStreamAsync(config);
var consumer = await _natsJSStream.CreateOrUpdateConsumerAsync(new ConsumerConfig()
 {
     FilterSubject = "a_b_c"
 });

[mtmk]

Thanks for reporting this @eddyyuen. It looks like a bug where we're mucking up the request subject when consumer name is not provided.

As a workaround, it's fine if you name the consumer:

var consumer = await _natsJSStream.CreateOrUpdateConsumerAsync(new ConsumerConfig("my_consumer")
{
    FilterSubject = "a.b.c"
});

Admittedly there is a little complication due to server support for legacy consumer configurations as consumer implementation evolved and we might not be handling that well to give friendly errors.

Having said all that, I might be missing something here that you don't want to name your consumer for some reason. What sort of consumer are you trying to create?

[eddyyuen]

Thanks for reporting this @eddyyuen. It looks like a bug where we're mucking up the request subject when consumer name is not provided.

As a workaround, it's fine if you name the consumer:

var consumer = await _natsJSStream.CreateOrUpdateConsumerAsync(new ConsumerConfig("my_consumer")
{
    FilterSubject = "a.b.c"
});

Admittedly there is a little complication due to server support for legacy consumer configurations as consumer implementation evolved and we might not be handling that well to give friendly errors.

Having said all that, I might be missing something here that you don't want to name your consumer for some reason. What sort of consumer are you trying to create?

Thanks! I am new to NATS , and I just forgot to name my consumer.