Repository navigation
Conversation
Elasticsearch names the Vector DB indices profile "Default", so the UI should match instead of calling it "Performant". The i18n id is renamed to match the profile name. Co-authored-by: Cursor <cursoragent@cursor.com>
… type The project default flyout needs each type's managed profiles in cost order, and the one to mark as the default. Expose both from common/managed_profiles instead of keeping the list private. Indices have no marked default, because their only managed profile is already labeled "Default".
The Pick of name, isHidden and outrankedByRuleName accepted the same objects as BoostRuleMatch, since its other fields are optional. Using the type directly makes the props easier to read. Co-authored-by: Cursor <cursoragent@cursor.com>
… card The count badge that opens the matches popover is needed by the project default card and by the flyout footers. It counts only the matches the rule applies to and takes a function for its accessible label, so callers don't compute the count twice. Co-authored-by: Cursor <cursoragent@cursor.com>
Shows what a rule or profile applies to above a flyout's buttons: the match count with its popover, the storage size and, for data streams, the boost timeline of the profile. Co-authored-by: Cursor <cursoragent@cursor.com>
Lets users change the profile the default rule uses for a type. It offers the managed profiles in cost order, marks the one new projects start with, and has a custom option to pick one of the user's own profiles. The custom choice is kept when switching between options. Closes elastic#304397. Co-authored-by: Cursor <cursoragent@cursor.com>
Covers both types, custom and converted profiles, no custom profiles, and the flyout without its applies to footer. Co-authored-by: Cursor <cursoragent@cursor.com>
Remove the custom profile and "without applies to" stories, and name the converted profile story after what it shows: a built-in profile with no label or description listed for it. Co-authored-by: Cursor <cursoragent@cursor.com>
Lets users create and edit a boost rule: name, boost profile, one index pattern or name with a preview of the indices or data streams it matches, and priority, with the project default flyout's "Applies to" footer. Name and index pattern validation lives in common/ so the profile flyout and the server routes can reuse it. Priority ties are reported the way Elasticsearch decides them. Closes elastic#303827. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
This branch has not been deployed
This file contains hidden or 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
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.
Summary
Closes #303827
Note
Built on top of #306380 (project default flyout).
Adds the boost rule flyout to Search boost, in create and edit modes. It takes its data as props and reports actions through callbacks, and for now it only runs in Storybook. #303832 connects it to the API.
Checklist
Documentation was added for features that require explanation or tutorials(not user facing yet)Plugin configuration key changes(none)Breaking HTTP API changes(none)release_note:*type label (orrelease_note:skip) is appliedbackport:*labels.Identify risks
Low. The flyout isn't wired into the app yet; it only runs in Storybook and unit tests. The Search boost plugin is also disabled by default (
xpack.searchBoost.enabled: false).