-
Notifications
You must be signed in to change notification settings - Fork 31
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
Introduce viaq_index_name field #116
Conversation
FYI, @mijicherian I fixed the tests for #115 |
4a065db
to
e73c714
Compare
e73c714
to
82ae6c1
Compare
Thanks @lukas-vlcek for your efforts. |
@richm PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
@richm @mijicherian When we are going to need this new field? (i.e. when we need to cut a new model release?) |
I would say now - at least, go ahead and generate a release, and submit a PR to origin-aggregated-logging to use the new release |
type: keyword | ||
example: project.my-cool-project-in-lab04.748e92c2-70d7-11e9-b387-000d3af2d83b.2019.05.09 | ||
description: | | ||
Index name in which this message will be stored within the Elasticsearch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@richm @jcantrill How is this going to be impacted when moving to the new data model with ES 6.x (rollover and common index; no more index per namespace/day).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we still need this field
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No description provided.