-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
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
multi-fields config #28
Comments
Hi. But I think it's a good idea to support this feature like fluent-plugin-elasticsearch is doing. |
@jmwiersma @sakama How can we specify this mapping as plugin config options? Any thoughts? |
Sorry, I feel a technical reply is beyond my abilities on this one. For now as a work around I have pushed a template to ES, to created non_analyzed fields for any index named embulk-*.
|
I think specify as a file is better. For example, fluent-plugin-elasticseach has 2 options. |
Thank you. name and file path (or json content) are good as config options. Will take it. |
👍 |
Hi,
I like to push string input from CSV columns both as analyzed field for full-text search, and well as a not_analyzed field to Elasticsearch. Normally that can be done with the fields mapping parameter;
https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html
How do I specify that using embulk ?
The text was updated successfully, but these errors were encountered: