Decouple Publisher Client and publishing Topic

[nitinchauhan178]

Is your feature request related to a problem? Please describe.
Currently Publisher client is bind to a single topic. This require to create dedicated publisher clients for each topic we want to publish. We have use case where we need to publish to multiple topic (few hundreds) and for that we need to keep track of huge list of clients on VM memory.

Describe the solution you'd like
Decouple Publisher client with topic to publish. Topic information should be taken as arg to publish method as TopicName

Describe alternatives you've considered
There is an alternative for it TopicAdminClient.publish which doesn't bind to a topic and a single client is able to publish to n number of topics. But this not recommended for high volume message publish and therefore not fulfilling our use case.

[maitrimangal]

We have moved this issue to our internal tracking system. However, the issue is considered low-priority at this time. If the issue is ultimately resolved, it will appear in the release notes for the client at that time. If this issue is of higher priority for you, please enter a support ticket for follow-up. Thanks

Internal Bug - b/278075996

[anthonyalayo]

@maitrimangal how does it look in terms of priority today? I am facing the same scenario and I agree with the issue.

I have a similar-ish discussion on the C++ side:
googleapis/google-cloud-cpp#13707

[anthonyalayo]

@maitrimangal how do I file a support ticket for raising the priority?

[michaelpri10]

Hello @anthonyalayo, I support ticket can be filed in the support console. I will note that this feature request is still tracked on our public issue tracker as it would affect client libraries for other languages as well, and it has not currently been re-prioritized.