provectus / kafka-ui

Open-Source Web UI for Apache Kafka Management

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Search with groovy fails

HStoyanov-augglobal opened this issue Β· comments

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running master-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

Even the simplest ones fail - keyAsText != null, as taken from actual example. It doesn't display errors, no progress is evident (i.e. messages being counted/consumed).

When i hit the Submit button, the only things that changes on the page are:

  • the Submit button turning to Cancel, then back to Submit;
  • there is a DONE message, it is displayed near the text showing how many messages were consumed, download size, timing. That DONE message changes to Polling partitions: [0, 1, 2], then back to DONE.

Both changes happen for less than a second on topics of any size.

Expected behavior

When i add a new filter, it should be obvious that is doing the search - count messages being consumed, count download size...

Your installation details

83b5a60 v0.7.2

Steps to reproduce

  1. Choose topic
  2. Click Add Filters button
  3. Use filter like keyAsText != null (from example) or just about anything else whose results you can verify
  4. It will start search automatically, but can also hit the Submit button, behavior is the same

Screenshots

No response

Logs

No response

Additional context

No response

Hello there HStoyanov-augglobal! πŸ‘‹

Thank you and congratulations πŸŽ‰ for opening your very first issue in this project! πŸ’–

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. πŸ‘€

Hey, this repo is not maintained (#4255), but we've replaced groovy with CEL (and fixed the related CVE) here: https://github.com/kafbat/kafka-ui . I'll be glad to answer your questions there if any.

@HStoyanov-augglobal You can set the configuration property "filtering.groovy.enabled" to true to re-enable groovy filtering.