Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] - Clusters filter problem #210

Closed
flyhigh-hifi opened this issue Feb 20, 2024 · 0 comments
Closed

[BUG] - Clusters filter problem #210

flyhigh-hifi opened this issue Feb 20, 2024 · 0 comments
Assignees
Labels

Comments

@flyhigh-hifi
Copy link

flyhigh-hifi commented Feb 20, 2024

Description
Filtering in clusters list doesn't work as expected. Results being showed correctly, but clicking on them leads to different clusters. I have 15 clusters in my list (2 pages), filtering is not usable for me. Looks like row index from the table is being the same before/after filtering for different clusters, so my suggestion is to give each cluster an unique autoincrement id (not elastic cluster id because multiple configurations can be added with different name / credentials) and use it as reference instead of loadCluster(row.index)

Steps To Reproduce

  1. Open elasticvue
  2. Add cluster with name "cluster_1"
  3. Add cluster with name "cluster_2"
  4. In the search input from the screenshot type "cluster_2"
  5. Click on the matching results which is correctly "cluster_2"
  6. Instead, cluster_1 connection is being established

Screenshots
Снимок экрана 2024-02-20 в 08 44 05

Environment (please include the following information):

  • Elasticsearch version: Doesn't matter
  • Operating system: MacOS 12.6.1
  • Browser + version: Chrome 121.0.6167.184 (ARM)
  • Elasticvue version: 1.0.3
  • How are you running elasticvue: extension
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants