-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fix(elasticsearch_index): create datahub_usage_event index where datahub_analytics_enabled
set to false
#5974
fix(elasticsearch_index): create datahub_usage_event index where datahub_analytics_enabled
set to false
#5974
Conversation
@jjoyce0510 Please chime in here for next steps |
Hello @GyuhoonK Could you explain the reasoning behind the PR? |
@pedro93 |
Can you clarify what you mean by:
|
Sorry, I make you confused. |
How does wanting to use Data Landscape Summary and not DataHub Analytics relate to wanting to use ElasticSearch's |
So if I understand you correctly… you can not use DataHub Analytics because your Elastic cluster does not support x pack but still want to have Data Summary Landscape by changing the way the datahub_usage_event index works? |
That is my interpretation. I think this PR makes sense. Landscape is indeed separate from usage tracking. Going to approve! |
@pedro93 |
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, but needs a tweak to the curl calls to align with the rest.
…b.com/GyuhoonK/datahub into fix(add-index-for-notusing-analytics)
@shirshanka |
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 let’s wait for green ci before merging
@pedro93
is there any issue on kafka setup? |
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
Checklist
Setting
global.datahub_analytics_enabled
tofalse
means not using the feature ofDataHub Usage Analytics
. However, Ifglobal.datahub_analytics_enabled
is set tofalse
,elasticsearch-setup
job doesn't create any index. Not creating any index means you cannot use not onlyDataHub Usage Analytics
but alsoData Landscape Summary
. This is because when you clickAnalytics
tab, GMS check whetherElasticSearch has the index named
datahub_usage_event
(precisely data_stream index).So, developers who want to turn off only
DataHub Usage Analytics
feature and useData Landscape Summary
have no choice. They should turn both of them off or turn them on.If
elasticsearch-setup
job could create index(datahub_usage_event
, but not data_stream index) whereglobal.datahub_analytics_enabled
is set tofalse
, We can keepData Landscape Summary
alive.Thank you.