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

fix: Increases the options limit for Annotation Layers #23613

Conversation

michael-s-molina
Copy link
Member

SUMMARY

Increases the options limit for Annotation Layers in Explore. Previously, the options were limited to 20 results which is a problem for organizations with many records. Following the same pattern used in filters, the limit was increased to a 1000 values. Although, 1000 values will probably be sufficient for most of organizations, the endgame solution would be to create a control using the AsyncSelect and replace the sync version. This change is not in the scope of this PR.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Screenshot 2023-04-06 at 10 47 44

TESTING INSTRUCTIONS

Make sure the Annotation Layers select in Explore can show up to a 1000 values.

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

Copy link
Member

@Antonio-RiveroMartnez Antonio-RiveroMartnez left a comment

Choose a reason for hiding this comment

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

LGTM!

@michael-s-molina michael-s-molina merged commit 739adcb into apache:master Apr 6, 2023
michael-s-molina added a commit to airbnb/superset-fork that referenced this pull request Apr 7, 2023
@Vitor-Avila
Copy link
Contributor

hey @michael-s-molina @rusackas I was testing this change, and on my end the amount of returned results is 100 (rather than 1000). In my tests, regardless if I increase the page size in the request arguments, it seems that Superset has a max size defined in the server side.

Do you know if this server side limit is configureable and could be changed? It could be an additional modification needed on my end. Currently I see this server-side hard limit of 100 to most API endpoints (charts, annotation layers, dashboards, datasets, etc).

@michael-s-molina
Copy link
Member Author

michael-s-molina commented Aug 9, 2023

Do you know if this server side limit is configureable and could be changed?

The only one I can think of is FAB_API_MAX_PAGE_SIZE.

@Vitor-Avila
Copy link
Contributor

ohh, I see -- thanks for sharing!

@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 3.0.0 labels Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/XS 🚢 3.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants