# KQL unexpected behaviour when '/' on text field
**URL:** https://discuss.elastic.co/t/kql-unexpected-behaviour-when-on-text-field/190716
**Category:** Kibana
**Tags:** kql-kibana-query-language
**Created:** [July 16, 2019, 11:12am UTC](https://discuss.elastic.co/t/kql-unexpected-behaviour-when-on-text-field/190716 "2019-07-16T11:12:09Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@masual](https://discuss.elastic.co/u/masual)
#### Post date: [July 16, 2019, 11:12am UTC](https://discuss.elastic.co/t/kql-unexpected-behaviour-when-on-text-field/190716/1 "2019-07-16T11:12:09Z")
When using KQL expressions such as `*keyword*`, no results are displayed if the text field contains an slash ('/') and the "keyword" is located afterwards the slash. For example with the following text field value:
```
Process '848' hidden from /proc. Possible kernel level rootkit.
```
With the query `*hidden*` it works, but with `*rootkit*` no results are displayed .
Is that the intended behaviour?
ELK 7.2.0
---
### Author:  [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)
#### Post date: [July 18, 2019, 1:07pm UTC](https://discuss.elastic.co/t/kql-unexpected-behaviour-when-on-text-field/190716/2 "2019-07-18T13:07:36Z")
This shouldn't happen. Could you open an issue in the Kibana repo, please?
---
### Author:  [@masual](https://discuss.elastic.co/u/masual)
#### Post date: [July 18, 2019, 1:22pm UTC](https://discuss.elastic.co/t/kql-unexpected-behaviour-when-on-text-field/190716/3 "2019-07-18T13:22:42Z")
Done!
[https://github.com/elastic/kibana/issues/41436](https://github.com/elastic/kibana/issues/41436)
Thank You!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 15, 2019, 1:22pm UTC](https://discuss.elastic.co/t/kql-unexpected-behaviour-when-on-text-field/190716/4 "2019-08-15T13:22:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.