Skip to content
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

Improve search response rendering; other minor fixes #523

Merged
merged 10 commits into from
Dec 11, 2024

Conversation

ohltyler
Copy link
Member

Description

This PR primarily improves the search response rendering. Instead of a single JSON editor view showing the list of _sources from the response, now offer 2 modes: 1/ a more structured view of the sources in a tabular format with pagination to look through the data, or 2/ a raw JSON view which shows the full response. This ensures that any data users are interested outside of the _source hits (e.g., aggregations, ext field values, etc.) is still accessible.

Implementation details:

  • adds new Results component and sub-components containing the new rendering options
  • makes new Results component accessible in the edit query modal and the query tab of the Inspector, which is the 2 places search is supported
  • adds new "Search" button to open/close the search-related components in the edit query modal. Defaults to closed
  • other: bug fix: handles edge case of search-related template node diffs not being detected when no search resources exist
  • other: enhancement: small state updates when creating ingest/search resources for the first time
  • other: cleanup of unused props

Demo video, showing the updates to the edit query modal and the query panel in Inspector:

screen-capture.1.webm

Issues Resolved

--

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Collaborator

@saimedhi saimedhi left a comment

Choose a reason for hiding this comment

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

  • LGTM.
  • Tyler, Ming suggested to have the results tab below search tab right in the below screenshot. Will that be done in a followup PR?
Screenshot 2024-12-11 at 8 50 35 AM

@ohltyler
Copy link
Member Author

  • LGTM.
  • Tyler, Ming suggested to have the results tab below search tab right in the below screenshot. Will that be done in a followup PR?
Screenshot 2024-12-11 at 8 50 35 AM

Nothing is finalized, if that decision is made will be in a separate pr, yes.

@ohltyler ohltyler closed this Dec 11, 2024
@ohltyler ohltyler reopened this Dec 11, 2024
@ohltyler ohltyler merged commit 72c32e6 into opensearch-project:main Dec 11, 2024
12 of 14 checks passed
@ohltyler ohltyler deleted the nit-fixes-2 branch December 11, 2024 16:57
opensearch-trigger-bot bot pushed a commit that referenced this pull request Dec 11, 2024
Signed-off-by: Tyler Ohlsen <[email protected]>
(cherry picked from commit 72c32e6)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
ohltyler pushed a commit that referenced this pull request Dec 11, 2024
(cherry picked from commit 72c32e6)

Signed-off-by: Tyler Ohlsen <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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.

2 participants