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
NET-4135 - Fix NodeMeta filtering Catalog List Services API #18322
NET-4135 - Fix NodeMeta filtering Catalog List Services API #18322
Changes from 21 commits
cef8e3d
79fdf19
91efd2c
4fa91a6
92ed62d
1a53944
c7c5876
db1039a
e475fa6
dc4f9d1
ecc8dbf
b8dfd87
174f8b0
6d1cee7
8b21150
6d8d396
f63c251
7f6c537
6c08f9c
44f366b
8c12cbb
961eeef
5af1b1c
1763589
f475356
86b1e28
aaf6e54
4ed56cc
eaed33c
5d366e8
7a95115
96421c2
94e73db
b7aa37e
89ed772
b25d920
1141444
af363ff
ebcf3c3
04aae7e
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.
@rboyer I saw you were the one that added
parseServiceNodes
to a bunch of other endpoints back in 2022. Is there any performance implications we need to think about for adding this to this endpoint as well? This change is needed to fill in nodemeta so it can be filtered on.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.
Currently we only do the expensive join against the
nodes
table when the user provides the NodeMeta parameter on the original API query. When they do this we call a completely different function link.If we were concerned like that, we could instead alter the
Store.Services
method to take an extra boolean parameter to conditionally join the NodeMeta as in this PR.Then the calling code in
agent/consul/catalog_endpoint.go
could set the flag totrue
whenfilter != ""
OR just when: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.
@rboyer I have updated the PR can I merge this now? please approve.
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.
@rboyer I have updated the PR can I merge this now? please approve.