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
Since we have more than 251 distinct values the auto complete does not show the correct values even when typing the correct prefixes.
It seems like Grafana UI generally triggers a correct search (with search term), but this data source does not use it.
My improvement idea would be to correctly implement the auto complete function and use the typed search term for the auto completion if available.
adx-<tablename>
| where isnotempty(<column_name>)
| where <column_name> contains <search_string>
| take 50000
| distinct <column_name>
| take 251
The text was updated successfully, but these errors were encountered:
javisst
changed the title
Improve auto-complete for query builder by using search string
Improve auto-completion for query builder by using search string
Jul 3, 2024
Currently the auto completion for the query builder is initialized once with fixed values by the following query.
The query to initialize the values is fixed to sample 50000 values and then take 251 distinct values from that sample.
For code see here:
azure-data-explorer-datasource/src/KustoExpressionParser.ts
Lines 67 to 69 in a8a6c09
Since we have more than 251 distinct values the auto complete does not show the correct values even when typing the correct prefixes.
It seems like Grafana UI generally triggers a correct search (with search term), but this data source does not use it.
My improvement idea would be to correctly implement the auto complete function and use the typed search term for the auto completion if available.
The text was updated successfully, but these errors were encountered: