fix: incorrect query being generated from traces page (#6130)

This commit is contained in:
Vikrant Gupta 2024-10-09 11:41:38 +05:30 committed by GitHub
parent a24fb5d84f
commit 4b79d3b785
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 5 additions and 3 deletions

View File

@ -244,7 +244,7 @@ function QueryBuilderSearchV2(
isFetching: isFetchingSuggestions,
} = useGetAttributeSuggestions(
{
searchText: searchValue.split(' ')[0],
searchText: searchValue?.split(' ')[0],
dataSource: query.dataSource,
filters: query.filters,
},
@ -691,7 +691,7 @@ function QueryBuilderSearchV2(
}
}
if (currentState === DropdownState.OPERATOR) {
const keyOperator = searchValue.split(' ');
const keyOperator = searchValue?.split(' ');
const partialOperator = keyOperator?.[1];
const strippedKey = keyOperator?.[0];

View File

@ -1,4 +1,5 @@
import { initialAutocompleteData, OPERATORS } from 'constants/queryBuilder';
import { getOperatorValue } from 'container/QueryBuilder/filters/QueryBuilderSearch/utils';
import getStep from 'lib/getStep';
import {
BaseAutocompleteData,
@ -27,7 +28,8 @@ export const getTraceToLogsQuery = (
items: [
{
id: uuid(),
op: OPERATORS.IN,
// for generating query we use in instead of IN
op: getOperatorValue(OPERATORS.IN),
value: traceId,
key,
},