Skip to content
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

Add support for alias field type to fields.yml #7645

Merged
merged 1 commit into from
Jul 24, 2018

Conversation

ruflin
Copy link
Collaborator

@ruflin ruflin commented Jul 19, 2018

In elastic/elasticsearch#23714 Elasticsearch implemented the alias field type. This can be used in fields.yml as following:

- name: a.b
  type: alias
  path: a.c

a.b will be the alias for a.c.

@andrewkroh
Copy link
Member

Would collocating the alias with the original field make sense?

- name: a.c
  type: keyword
  alias: a.b

a.b. will be an alias of a.c

@ruflin
Copy link
Collaborator Author

ruflin commented Jul 23, 2018

If we do that, alias would have to be an array as multiple alias can point to the same field.

I would prefer to keep the alias definition local as the alias definition is likely going to be inside a metricset / dataset and the original field is defined in libbeat.

Also in case we add it to the original field and alias supports additional features in the future, not sure how we would deal with it if we have all alias defined in one place.

In elastic/elasticsearch#23714 Elasticsearch implemented the alias field type. This can be used in fields.yml as following:

```
- name: a.b
  type: alias
  path: a.c
```

`a.b` will be the alias for `a.c`.
@andrewkroh andrewkroh merged commit 2bbf5a2 into elastic:master Jul 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants