Swarm 15 introduced the setting search.enableDelimiterPaths=True
, so that any search feeds the elasticsearch index when a search feed is first created will have a new paths
field which . That allows for faster delimiter listings when gateway.cfg has [folder_listings] usePaths=true
(https://perifery.atlassian.net/wiki/spaces/public/pages/2443810201/Gateway+Configuration#%5Bfolder_listings%5D ). Starting with Gateway 8.0.3 usePaths=true
is the default though it’s only in effect when ?prefix
is not specified or contains a small number of pseudo-directories.
Gateway 8 will log a warning if it cannot take effect because some elasticsearch entries are usePaths
is ignored due to any entries in the elasticsearch index missing the field. Unfortunately Gateway 7 could log a false warning. This can happen if the search feed was created before that setting search.enableDelimiterPaths
was True or if the setting it was temporarily changed to False while adding/updating objects.
...
Choose an elasticesarch node name or ip from the Search Feed.
Note the Swarm
cluster.name
and search feed number id (the first is 0).Issue this curl:
Code Block curl -H 'Content-type: application/json' 'ELASTICSEARCH-HOST:9200/index_CLUSTER-NAME0/_search?pretty&size=100' --data-binary ' { "query": { "bool": { "must": { "terms": { "stype": [ "NAMED" ] } }, "must_not": { "exists": { "field": "paths.p1" } } } } }'
The resulting If any entries are at least some of the entries preventing returned they prevent the use of
usePaths=true
.
Info |
---|
A new search feed must be created if any entries are found. Refreshing the feed will not add the “paths” |
...
Filter by label (Content by label) | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|