We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
I read the documentation of this plugin, and didn't find a way to define my custom multi fields as defined in https://www.elastic.co/guide/en/elasticsearch/reference/1.4/_multi_fields.html.
I know that is possible to use field_name multi_field: true, but it generate a field with the name untouched, which is not analyzed. But I want to do something like this (https://www.elastic.co/guide/en/elasticsearch/guide/current/sorting-collations.html#_unicode_sorting).
field_name multi_field: true
Is there a way to do that now? If not, will it be implemented? A think a nice syntax would be this way:
field_name fields = [ raw: [type: 'string', index: 'not_analyzed' ], sort: [type: 'string', analyzer: 'my_sort'] ]
The text was updated successfully, but these errors were encountered:
puneetbehl
No branches or pull requests
Hello,
I read the documentation of this plugin, and didn't find a way to define my custom multi fields as defined in https://www.elastic.co/guide/en/elasticsearch/reference/1.4/_multi_fields.html.
I know that is possible to use
field_name multi_field: true
, but it generate a field with the name untouched, which is not analyzed. But I want to do something like this (https://www.elastic.co/guide/en/elasticsearch/guide/current/sorting-collations.html#_unicode_sorting).Is there a way to do that now? If not, will it be implemented? A think a nice syntax would be this way:
The text was updated successfully, but these errors were encountered: