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

Client streaming methods should send routing headers #448

Open
busunkim96 opened this issue Jun 9, 2020 · 5 comments
Open

Client streaming methods should send routing headers #448

busunkim96 opened this issue Jun 9, 2020 · 5 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@busunkim96
Copy link
Contributor

Clients streaming methods should send routing headers on the initial RPC that opens the stream. Field headers are currently ignored for these methods

{%- if method.field_headers %}
# Certain fields should be provided within the metadata header;
# add these here.
metadata = tuple(metadata) + (
gapic_v1.routing_header.to_grpc_metadata((
{%- for field_header in method.field_headers %}
{%- if not method.client_streaming %}
('{{ field_header }}', request.{{ field_header }}),
{%- endif %}
{%- endfor %}
)),
)

As far as I know this isn't currently an issue for any libraries on the microgenerator.

@busunkim96 busunkim96 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 9, 2020
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Sep 7, 2020
@arithmetic1728
Copy link
Collaborator

any updates as we are out of slo

@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Dec 6, 2020
@hkdevandla
Copy link
Member

@busunkim96 , can you clarify why this isn't an issue for libraries using micro-generator?

is this a feature gap between micro-generator and the legacy (monolith) that we need to support i.e adding routing headers to the streaming requests? If not, we should mark this bug as feature request or mark with appropriate priority so we can fix it. Please advice. Thanks!

P.S: This issue triggered OO-SLO.

@busunkim96
Copy link
Contributor Author

@hkdevandla None of the currently published APIs have a streaming method that requires a routing header be sent.

I opened this after discussion #443 which added routing headers for all the http verbs. The current behavior may be correct, but I opened this to make sure this comment was followed up on:

I was under the impression that headers for streaming methods don't make a lot of sense because they're not tightly bound to http semantics. If that's not correct, then I think we would need to ask someone who knows better.

Originally posted by @software-dov in #443 (comment)

@hkdevandla hkdevandla removed the 🚨 This issue needs some love. label Dec 21, 2020
@hkdevandla
Copy link
Member

Thanks @busunkim96, making this as P3 in that case if it is not an issue but needs some follow up/investigation.

@hkdevandla hkdevandla added priority: p3 Desirable enhancement or fix. May not be included in next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Dec 21, 2020
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Jun 21, 2021
@software-dov software-dov added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Oct 12, 2021
@software-dov
Copy link
Contributor

We are dropping this to a feature request for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

5 participants