Skip to content

[Transform] fixing naming in HLRC and _cat to match API content #54300

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

Merged

Conversation

benwtrent
Copy link
Member

@benwtrent benwtrent commented Mar 26, 2020

Fixing the naming of the HLRC values to match the ToXContent field names (i.e. the field names returned from an API call).

Also fixes the names in the _cat API as well.

closes #53946

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml/Transform)

@benwtrent benwtrent force-pushed the feature/transform-unify-stats-naming branch from 211c6af to 19e5486 Compare March 26, 2020 19:23
@benwtrent
Copy link
Member Author

@elasticmachine update branch

Copy link

@hendrikmuhs hendrikmuhs left a comment

Choose a reason for hiding this comment

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

LGTM

@hendrikmuhs
Copy link

FYI @lcawl

static ParseField TRIGGER_COUNT = new ParseField("trigger_count");
static ParseField INDEX_TIME_IN_MS = new ParseField("index_time_in_ms");
static ParseField SEARCH_TIME_IN_MS = new ParseField("search_time_in_ms");
static ParseField PROCESSING_TIME_IN_MS = new ParseField("processing_time_in_ms");
Copy link
Contributor

Choose a reason for hiding this comment

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

processing_time_in_ms

Does this mean we need to add this property to the stats object in https://www.elastic.co/guide/en/elasticsearch/reference/master/get-transform-stats.html ?

Copy link

@hendrikmuhs hendrikmuhs Mar 27, 2020

Choose a reason for hiding this comment

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

Sorry, that's my fault. In #53770 I added processing_time_in_ms and processing_total.

The 2 are counterparts of the search and index one:

The amount of time processing results, in milliseconds.
The number of processing operations.

This is basically what happens between search and index and shows the time/load the transform task itself used.

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks, I've created #54368 to add those.

static ParseField PROCESSING_TIME_IN_MS = new ParseField("processing_time_in_ms");
static ParseField INDEX_TOTAL = new ParseField("index_total");
static ParseField SEARCH_TOTAL = new ParseField("search_total");
static ParseField PROCESSING_TOTAL = new ParseField("processing_total");
Copy link
Contributor

Choose a reason for hiding this comment

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

processing_total

This also doesn't appear in https://www.elastic.co/guide/en/elasticsearch/reference/master/get-transform-stats.html
Should it?

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 think it should be in stats. I am not 100% sure it should be in the _cat API though. Right now processing times are so small that they are pretty insignificant.

Copy link
Contributor

Choose a reason for hiding this comment

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

Likewise this will be fixed in #54368

@benwtrent
Copy link
Member Author

@elasticmachine update branch

Copy link
Contributor

@lcawl lcawl left a comment

Choose a reason for hiding this comment

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

@benwtrent benwtrent merged commit 3c81082 into elastic:master Mar 30, 2020
@benwtrent benwtrent deleted the feature/transform-unify-stats-naming branch March 30, 2020 12:10
benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Mar 30, 2020
…tic#54300)

Fixing the naming of the HLRC values to match the ToXContent field names (i.e. the field names returned from an API call).

Also fixes the names in the _cat API as well.

closes elastic#53946
benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Mar 30, 2020
…tic#54300)

Fixing the naming of the HLRC values to match the ToXContent field names (i.e. the field names returned from an API call).

Also fixes the names in the _cat API as well.

closes elastic#53946
benwtrent added a commit that referenced this pull request Mar 30, 2020
…) (#54409)

Fixing the naming of the HLRC values to match the ToXContent field names (i.e. the field names returned from an API call).

Also fixes the names in the _cat API as well.

closes #53946
benwtrent added a commit that referenced this pull request Mar 30, 2020
…) (#54408)

Fixing the naming of the HLRC values to match the ToXContent field names (i.e. the field names returned from an API call).

Also fixes the names in the _cat API as well.

closes #53946
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Transform] Field naming is inconsistent between _stats, HLRC and _cat
6 participants