Skip to content

Commit dcd71cf

Browse files
authored
TASK: Add instructions for using custom index name
1 parent 57e128d commit dcd71cf

1 file changed

Lines changed: 33 additions & 0 deletions

File tree

README.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,39 @@ Inclusion of the routes from this package into your main `Configuration/Routes.y
2020

2121
## Configuration
2222

23+
### Custom index name
24+
25+
It is usually a good idea to specify a custom index name for a project, instead of the default `typo3cr`. That
26+
way no conflicts can arise when multiple projects use the same Elasticsearch server.
27+
28+
To specify a custom index name, the following is needed:
29+
30+
Neos:
31+
ContentRepository:
32+
Search:
33+
elasticSearch:
34+
indexName: acmecom
35+
36+
Flowpack:
37+
ElasticSearch:
38+
indexes:
39+
default: # client name used to connect (see Flowpack.ElasticSearch.clients)
40+
acmecom: # custom index name
41+
analysis:
42+
filter:
43+
autocompleteFilter:
44+
max_shingle_size: 5
45+
min_shingle_size: 2
46+
type: 'shingle'
47+
analyzer:
48+
autocomplete:
49+
filter: [ 'lowercase', 'autocompleteFilter' ]
50+
char_filter: [ 'html_strip' ]
51+
type: 'custom'
52+
tokenizer: 'standard'
53+
54+
The latter is the custom analysis configuration used by the completion / suggestion and must be
55+
repeated for a custom index name.
2356

2457
### Pagination
2558

0 commit comments

Comments
 (0)