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
In this case, the index type 'tokenbf_v1' is suitable.
Before extracting the field from a json object, it need to check the presence of the key or the value using the hasToken function.
It also need to pay attention that word breaks are not allowed in tokens for indexing.
The text was updated successfully, but these errors were encountered:
sorry for late reply, yes this is a good idea, the problem is that size of this index will be huge and insert will be a bit slower..
let us play around it and make it optional.
the problem is that size of this index will be huge and insert will be a bit slower
By the way, this is quite consistent with the general logging recommendation that the number of unique combination should be small. Therefore, this is not a big deal, since a new entry of labels will actually be added only once per partition (one per day for example).
In this case, the index type 'tokenbf_v1' is suitable.
Before extracting the field from a json object, it need to check the presence of the key or the value using the hasToken function.
It also need to pay attention that word breaks are not allowed in tokens for indexing.
The text was updated successfully, but these errors were encountered: