Skip to content

Commit f268760

Browse files
committed
update limitations.md from limitations.rst
1 parent 56b7b86 commit f268760

1 file changed

Lines changed: 25 additions & 1 deletion

File tree

docs/user/ppl/limitations/limitations.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,4 +62,28 @@ For the following functionalities, the query will be forwarded to the V2 query e
6262
* ML
6363
* Kmeans
6464
* `show datasources` and command
65-
* Commands with `fetch_size` parameter
65+
* Commands with `fetch_size` parameter
66+
67+
68+
## Malformed Field Names in Object Fields
69+
70+
OpenSearch normally rejects field names containing problematic dot patterns (such as `.`, `..`, `.a`, `a.`, or `a..b`). However, when an object field has `enabled: false`, OpenSearch bypasses field name validation and allows storing documents with any field names.
71+
72+
If a document contains malformed field names inside an object field, PPL ignores those malformed field names. Other valid fields in the document are returned normally.
73+
74+
**Example of affected data:**
75+
76+
```json
77+
{
78+
"log": {
79+
".": "value1",
80+
".a": "value2",
81+
"a.": "value3",
82+
"a..b": "value4"
83+
}
84+
}
85+
```
86+
87+
When ``log`` is an object field with ``enabled: false``, subfields with malformed names are ignored.
88+
89+
**Recommendation:** Avoid using field names that contain leading dots, trailing dots, consecutive dots, or consist only of dots. This aligns with OpenSearch's default field naming requirements.

0 commit comments

Comments
 (0)