Inconsitent filtering messages on a topic

[ErykCh]

Hi, version 2.4.1

filtering messages on a topic

sometimes it works correctly and returns the correct result, but more often it does not work properly

some example:
there is a message with the key Ao9JdNYRQPirTIGe2Nz64g

filtering out works

finding doesn't work

Often I see such error:

No errors in logs:

[weeco]

We are looking at this. This issues was not introduced with v2.4.1, but we are not sure yet what is causing this. cc @bojand

Re the network error - this is most likely completely separate. Please have a look at the network tab and check the response status code as well as the request duration. If it's something like 30s or 60s I assume there's some timeout (e.g. from your reverse proxy) cutting of the connection.

[ErykCh]

Hi @bojand,

In version 2.4.2 the problem still exists.

!= works correctly, == works incorrectly

but the backend error information no longer appears

[weeco]

@ErykCh Could you please post more details? Such as screenshots that show the filter and the returned message content on which was filtered. That would help us to understand the problem better.

[ErykCh]

Hi,

the same behaviour as in first comment.

So here comparission of two versions:

2.3.10:

logs:

now version 2.4.2, the same environment, the same kafka, the same configuration, only difference is kowl version:

it looks like the filters are stored as cookies, so we're sure they're the same

logs:

[weeco]

Thanks @ErykCh , this looks like an issue specific to strings (i.e. JSON would work) - fixed here: #1093 . Sorry for missing that one - this Docker image will hopefully do it for you: docker pull redpandadata/console-unstable:master-1a0ad4a , we'll cut a patch release with this fix very soon

[ErykCh]

Hi,
version 2.4.3 works properly.

Thanks