DQL Bug when `match` is used with a logical clause (`or`) in a `@filter`

when i use match search like this:

{
node(func: type(km.Industry))
@filter(match(km.nameCN, "方案文档类型", 3))
{
uid
km.nameCN
km.nameEN
}
}

it works and the result is as expected.
RESULT_A–>

{
"data": {
"node": [
{
"uid": "0x9a6bc8",
"km.nameCN": "文档文档类型",
"km.nameEN": "Document Document Type"
},
{
"uid": "0x9a6d8d",
"km.nameCN": "解决方案文档类型"
}
]
}

but when i add another condition like this:

{
node(func: type(km.Industry))
@filter(match(km.nameCN, "方案文档类型", 3) or match(km.nameEN, "方案文档类型", 3))
{
uid
km.nameCN
km.nameEN
}
}

The result is uncertain,
the result Often isthis,

{
"data": {
"node": []
}

occasionally is RESULT_A,
is Use rules of match wrong? or something else wrong?

This looks like a bug. Possibly in the tokenizer.

So how can I modify this DQL to make it work normally?