You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Open elasticvue
Add cluster with name "cluster_1"
Add cluster with name "cluster_2"
In the search input from the screenshot type "cluster_2"
Click on the matching results which is correctly "cluster_2"
Instead, cluster_1 connection is being established
Screenshots
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
The text was updated successfully, but these errors were encountered:
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
Screenshots

Environment (please include the following information):
The text was updated successfully, but these errors were encountered: