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

Feat/elasticsearch optimization ext #229

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/datahub/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: A Helm chart for LinkedIn DataHub
type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
version: 0.2.127
version: 0.2.128
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application.
appVersion: 0.9.5
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -152,6 +152,10 @@ spec:
- name: ELASTICSEARCH_INDEX_BUILDER_REFRESH_INTERVAL_SECONDS
value: {{ . | quote }}
{{- end }}
{{- with .Values.global.elasticsearch.index.upgrade.allowDocCountMismatch }}
- name: ELASTICSEARCH_BUILD_INDICES_ALLOW_DOC_COUNT_MISMATCH
value: {{ . | quote }}
{{- end }}
- name: GRAPH_SERVICE_IMPL
value: {{ .Values.global.graph_service_impl }}
{{- if eq .Values.global.graph_service_impl "neo4j" }}
Expand Down
11 changes: 10 additions & 1 deletion charts/datahub/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -215,9 +215,18 @@ global:
enabled: true

## When reindexing is required, this option will clone the existing index as a backup
## The clone indices are not currently managed
## The clone indices are not currently managed.
# cloneIndices: true

## Typically when reindexing the document counts between the original and destination indices should match.
## In some cases reindexing might not be able to proceed due to incompatibilities between a document in the
## orignal index and the new index's mappings. This document could be dropped and re-ingested or restored from
## the SQL database.
##
## This setting allows continuing if and only if the cloneIndices setting is also enabled which
## ensures a complete backup of the original index is preserved.
# allowDocCountMismatch: false

kafka:
bootstrap:
server: "prerequisites-kafka:9092"
Expand Down