You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected module
Does it impact the UI, backend or Ingestion Framework?
-- UI
Describe the bug
A clear and concise description of what the bug is.
-- Currently, the "number of results per page" setting on the Ingestions page does not persist across sessions.
If a user increases the results per page, navigates into a pipeline, and then returns, the setting resets to the default (which seems to be 10, but 10 is not in the dropdown).
This creates a minor but persistent frustration, especially when managing multiple ingestions.
Additionally, there's an inconsistency in the results per page dropdown:
The default appears to be 10, but once changed, 10 is no longer an option in the dropdown (the lowest is 15).
The only way to revert to 10 per page is by reloading the page.
To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
The selected results per page setting should persist during the session.
If 10 per page is the default, it should be included as an option in the dropdown.
* fix the default pageSize setting on Ingestions Page
* minor change
* added playwright for it
* fix minor misplacement
(cherry picked from commit 2257f02)
Affected module
Does it impact the UI, backend or Ingestion Framework?
-- UI
Describe the bug
A clear and concise description of what the bug is.
-- Currently, the "number of results per page" setting on the Ingestions page does not persist across sessions.
Additionally, there's an inconsistency in the results per page dropdown:
To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Version:
openmetadata-ingestion[docker]==XYZ
]Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: