fix the search for custom properties in advance search for some types #19113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
safe to test
…nfig along with name and type
|
The Java checkstyle failed. Please run You can install the pre-commit hooks with |
Ashish8689
changed the title
|
|
ulixius9
approved these changes
Jan 8, 2025
chirag-madlani
approved these changes
Jan 8, 2025
9 tasks
harshach
approved these changes
Jan 8, 2025
|
Failed to cherry-pick changes to the 1.6.2 branch. |
Ashish8689
added a commit
that referenced
this pull request
Jan 8, 2025
…#19113) * fix the search in advance search custom properties * modify v1/metadata/types/customProperties api to get customPropertyConfig along with name and type * added config list in the entity ref list * fix type of duration, timestamp and other types * minor ui changes * remove customProperty type which are not supported for now * added playwright test around the duration type property * fix flaky test --------- Co-authored-by: sonikashah <[email protected]> (cherry picked from commit 2179b43)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes:
Fixes for the Issue #19069
Backed :
UI Improvement :
Fix the Custom Property search for the Following Types:
yyyy-MM-ddformat, with the range selector to find the properties within the date range)NOTE: Entity having space in the name, will not get a result. This will be fixed in the next release.
Type needs to work:
Not Supported Custom Property for Elastic Search :
dd MMM yyyy, MM/dd/yyyy, dd/MM/yyyy, dd-MM-yyyy, yyyyDDD, d MMMM yyyyformats are not supported by Elastic search and onlyyyyy-MM-ddis supported.Type of change:
Checklist:
Fixes <issue-number>: <short explanation>