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

Introduce viaq_index_name field #116

Merged
merged 2 commits into from
Nov 13, 2019
Merged

Introduce viaq_index_name field #116

merged 2 commits into from
Nov 13, 2019

Conversation

lukas-vlcek
Copy link
Member

No description provided.

@lukas-vlcek lukas-vlcek requested a review from richm November 13, 2019 12:03
@lukas-vlcek
Copy link
Member Author

FYI, @mijicherian I fixed the tests for #115

namespaces/_default_.yml Outdated Show resolved Hide resolved
@mijicherian
Copy link

Thanks @lukas-vlcek for your efforts.

@lukas-vlcek
Copy link
Member Author

@richm PTAL

Copy link
Member

@richm richm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@richm richm merged commit 07165e7 into master Nov 13, 2019
@lukas-vlcek
Copy link
Member Author

@richm @mijicherian When we are going to need this new field? (i.e. when we need to cut a new model release?)

@richm
Copy link
Member

richm commented Nov 13, 2019

@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.
Copy link
Member Author

@lukas-vlcek lukas-vlcek Dec 16, 2019

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).

Copy link
Member

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lukas-vlcek lukas-vlcek deleted the viaq_index_name branch December 16, 2019 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants