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

GUI Search Function is broken #145

Closed
saadkadhi opened this Issue Oct 11, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@saadkadhi
Contributor

saadkadhi commented Oct 11, 2018

Request Type

Bug

Work Environment

Question Answer
OS version (server) RedHat
OS version (client) Windows 7 Enterprise SP1
Cortex version / git hash 2.1.0, bc11d5c
Package Type From source

Problem Description

In the GUI of Cortex, when looking at job history, the search function is broken. If you select an Analyzer for the criteria, the search will return no values.

When looking at the search executed through the API, a wrong field name is being used.

The call to elastic to find the similar jobs is broken.

Possible Solutions

The search is looking for an analyzerDefinitionId while it should look for workerDefinitionId.

Complementary information

The attribute analyzerDefinitionId has previously been changed to workerDefinitionId.

@saadkadhi

This comment has been minimized.

Contributor

saadkadhi commented Oct 11, 2018

Confirmed by @To-om on 2.1.1 as well.

@saadkadhi saadkadhi added the bug label Oct 11, 2018

@saadkadhi saadkadhi added this to the 2.1.2 milestone Oct 11, 2018

To-om added a commit that referenced this issue Oct 12, 2018

@To-om To-om closed this Oct 12, 2018

@saadkadhi saadkadhi reopened this Oct 16, 2018

@saadkadhi

This comment has been minimized.

Contributor

saadkadhi commented Oct 16, 2018

@To-om @nadouani issue has not been fixed in 2.1.2:

screenshot_2018-10-16_at_16_41_51

screenshot_2018-10-16_at_16_42_43

@saadkadhi saadkadhi modified the milestones: 2.1.2, 2.1.3 Oct 16, 2018

@nadouani nadouani self-assigned this Oct 16, 2018

@nadouani nadouani closed this Oct 16, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment