-
Notifications
You must be signed in to change notification settings - Fork 149
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
[ACS-4794] ES migration PR #3359
Conversation
999887c
to
0ddcf84
Compare
213af45
to
f0adb72
Compare
…nd sorting search terms
* [ACS-4794][link-adf:feature/dev-mkinas-es-migration] Fix actionsAvailableFilesFolders and actionsAvailableSpecialPermissions * [ACS-4794][link-adf:feature/dev-mkinas-es-migration] Empty commit * [ACS-4794][link-adf:feature/dev-mkinas-es-migration] Fix missed test case * Reverted searchFor calls in single-file-actions.test.ts back to original state without *
…ing from unit tests
5a49850
to
0e751ea
Compare
expect(await dataTable.isItemPresent(filePdfUser2.name)).toBe(true, 'PDF file not displayed'); | ||
expect(await dataTable.isItemPresent(fileJpgUser1.name)).toBe(true, 'JPG file not displayed'); | ||
expect(await locationFilter.getChipTitle()).toEqual(`${site}, _REPOSITORY_`, 'Incorrect location filter selected'); | ||
// TODO check this again after ES migration works as expected when tested manually |
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.
should we raise some jira/add comment to existing jira to don't forget about this?
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.
Yes I will raise it today, thanks!
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
What is the new behaviour?
Queries and E2Es in ACA are now compatible with both ES and Solr
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: