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

Make Elasticsearch archive storage optional #1334

Merged

Conversation

pavolloffay
Copy link
Member

Related to #1321 (comment)

Signed-off-by: Pavol Loffay ploffay@redhat.com

Signed-off-by: Pavol Loffay <ploffay@redhat.com>
@codecov
Copy link

codecov bot commented Feb 12, 2019

Codecov Report

Merging #1334 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #1334   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files         162     162           
  Lines        7295    7308   +13     
======================================
+ Hits         7295    7308   +13
Impacted Files Coverage Δ
plugin/storage/es/options.go 100% <100%> (ø) ⬆️
plugin/storage/es/factory.go 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80b3dbb...0dbe8cb. Read the comment docs.

Copy link
Contributor

@objectiser objectiser left a comment

Choose a reason for hiding this comment

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

LGTM - just one minor comment.

@@ -206,6 +208,12 @@ func addFlags(flagSet *flag.FlagSet, nsConfig *namespaceConfig) {
"(experimental) Use read and write aliases for indices. Use this option with Elasticsearch rollover "+
"API. It requires an external component to create aliases before startup and then performing its management. "+
"Note that "+nsConfig.namespace+suffixMaxSpanAge+" is not taken into the account and has to be substituted by external component managing read alias.")
if nsConfig.namespace == archiveNamespace {
Copy link
Contributor

Choose a reason for hiding this comment

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

Just wondering if this needs to be conditional? The primary namespace is enabled by default, so it just means a user could disable the primary namespace, which is unlikely.

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't want to show this flag for the primary NS. We do the same for c*

@pavolloffay pavolloffay merged commit e96fe91 into jaegertracing:master Feb 13, 2019
@ghost ghost removed the review label Feb 13, 2019
iori-yja pushed a commit to iori-yja/jaeger that referenced this pull request Feb 15, 2019
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
Signed-off-by: Iori Yoneji <fivo.11235813@gmail.com>
iori-yja pushed a commit to iori-yja/jaeger that referenced this pull request Feb 15, 2019
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
iori-yja pushed a commit to iori-yja/jaeger that referenced this pull request Feb 15, 2019
Signed-off-by: Pavol Loffay <ploffay@redhat.com>
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.

None yet

2 participants