Open vishesh92 opened 2 months ago
Hey @vishesh92 have you verified that this problem is not in the API? It sounds like it could have to do with the pagesize and page parameters.
Hey @vishesh92 have you verified that this problem is not in the API? It sounds like it could have to do with the pagesize and page parameters.
The problem could be fixed by increasing the pagesize parameter but that would also slow down the UI. And if the number of entries are let's say 10000, it can also increase the load on the database.
Hey @vishesh92 have you verified that this problem is not in the API? It sounds like it could have to do with the pagesize and page parameters.
The problem could be fixed by increasing the pagesize parameter but that would also slow down the UI. And if the number of entries are let's say 10000, it can also increase the load on the database.
What you are saying is that the problem is not in the UI, right?
Hey @vishesh92 have you verified that this problem is not in the API? It sounds like it could have to do with the pagesize and page parameters.
The problem could be fixed by increasing the pagesize parameter but that would also slow down the UI. And if the number of entries are let's say 10000, it can also increase the load on the database.
What you are saying is that the problem is not in the UI, right?
This is an enhancement request. As of now, the end user will have to use the API instead of the UI.
UI should be making search queries with keyword when text is entered in the drop down to ensure that the user can search and select the desired resource irrespective of how many entries are present.
Another possible fix is to allow the user to enter the UUID even if it's not present in the drop down.
This is an enhancement request. As of now, the end user will have to use the API instead of the UI.
UI should be making search queries with keyword when text is entered in the drop down to ensure that the user can search and select the desired resource irrespective of how many entries are present.
Another possible fix is to allow the user to enter the UUID even if it's not present in the drop down.
Yes, but still it is the API that must be fixed, unless you say that giving the page and pagesize parameters on the CLI will yield the requested results.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
N/A
OS / ENVIRONMENT
N/A
SUMMARY
The dropdown in the UI fetches all domains at once with the default page size. If the actual count of resources is higher, the keyword search doesn't work and the domains after the default page size can't be selected in the UI.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS