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.
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
Optimize performance of '/apps/{appId}/envs/{env}/clusters/{clusterName}/namespaces' interface queries #4473
Optimize performance of '/apps/{appId}/envs/{env}/clusters/{clusterName}/namespaces' interface queries #4473
Changes from all commits
fe75b4d
99bf97a
1579f41
9f65eed
d7d3fd9
7329fab
5def448
6942564
0fc1f91
61ad016
587ce33
9de6563
9aab632
050dd0a
5a64035
0648fbd
35bd3a6
bc8149b
e771bdd
9a1ad83
3efef37
1274281
a968932
df8942c
f98175a
710cdd6
3c162b6
0101a3f
cc6f568
21dd30c
c1eeb41
e85d645
8b0056d
347e07b
d8eb437
19bae52
7e40fa1
fbbb02d
19cee24
91ba3b7
94ad542
64e1b0b
36ce5e2
14da645
e3eccdb
1305cbf
f5d8522
2a466f5
f79d1cd
1cb6f29
ad42aef
e67d2a5
c9de54d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original logic will throw the actual exception so that the user knows what's wrong. Is it better to preserve that logic? For example, we could use future.get to retrieve the exception occurred.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original exception stack information will be recorded here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand they are recorded in the server logs. What I propose is to throw the detailed exception message to the UI page so that the operating users could understand what's wrong, which is the original behavior.
The current error message
Parse namespaces error, expected: %s, but actual: %s, cannot get those namespaces: %s
could show the operating users some error details, but I have a concern that it might not be very clear.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I probably see what you mean, and the main points I took into account when making the changes here were.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The exceptions would be either timeout exceptions occurred in the portal side, or database access exceptions occurred in the admin service side. I suppose there is not much to do for a direct user, except that the user could report that to the admin users.
So my original idea was that we keep the logic the same as before - throw the actual exception and display it in the UI side, but I think the current logic is also ok.
That I suppose is the same as the user can't really handle the errors, no matter it contains one error or multiple errors :-)