-
Notifications
You must be signed in to change notification settings - Fork 70
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
[Change Proposal] Add support for counted_keyword field type #698
Comments
Thanks for opening this issue. Apart of adding the type in the package-spec, we will need to add the subfields validation to elastic-package, as was done for histograms in elastic/elastic-package#939. I have created a task list including these tasks. |
Thanks @jsoriano ! Do you have an estimate when we can expect this to be implemented? |
I am not sure when we will have a slot for this, pinging @jen-huang and @kpollich about planning. Is there a deadline when you would need this? Do you have workarounds in the meantime? Btw, I have added another point to the tasklist about adding support in Fleet if needed. |
@AlexanderWert I would like to understand the priority of the project(s) this blocks too. FYI we are happy to provide guidance and PR reviews if your team would like to contribute instead of being blocked by us. The list of tasks and reference PRs looks like a good place to start. |
I'll try to implement the necessary changes, so that our apm-package update can hopefully make it into 8.13. |
I believe this was closed by #707. Please reopen if this is incorrect. |
Recently the
counted_keyword
field type has been added to elasticsearch ((elastic/elasticsearch#101826).We would like to add a new field of this type to the APM package (see elastic/apm-server#12054).
Unfortunately this is not yet possible, because the
elastic-package
utility complains aboutcounted_keyword
being an invalid field type:So to me it seems like we have to add the
counted_keyword
to the field type specification, maybe this PR can serve as a template.Tasks
The text was updated successfully, but these errors were encountered: