Index mapping strategy proposal #146
Description
Hello,
It could be nice to have the possibility to have an index mapping strategy configurable into the plugin section or the searchable section ( if feasible more complex ).
Currently and when installing the mapping the only strategy ( to create an index name ) it is based on the domain class full name ( including the package )
This strategy ( nice anyway ) it is blocking the install mapping ( http 403 forbidden ) when on the cluster side there are some constraints that allow the creation of indices which starts with a specific "prefix".
This issue is true when the organization package does not start with the prefix allowed by the cluster rules.
Therefore a custom and multi index strategy could be highly appreciated to have,
Giving in this way the ( optional ) facility to the ES client ( Grails ES plugin ) to set a wished index name . .
I don't know based on a
- prefix without package ( prefix and default domain property name )
- prefix with package ( prefix and domain class full name )
- full custom alias ( one for each domain to index )
- etc
Thank you for understanding,
Best regards
antonio