merlimat opened a new pull request #1500: When we try to get information for a 
topic, we should try to load it …
   …if exists instead of return "not found"
   ### Motivation
   If a topic exists but it is not "loaded", the API calls are returning "404 
not found".  This is due to the fact that this is relying on the fact that 
producer/consumers lookup are forcing the topic to be loaded.
   The behavior is confusing and it will never load the topic (and keep it 
hidden from stats) if producers/consumers are not online.
   It is better to load the topic if it does actually exists.
   ### Modifications
    * Added `createIfMissing` option in managed ledger. Default is true though 
it's possible to load a managed ledger only if it's already existing without 
forcing the creation.
    * Added `BrokerService.getTopicIfExists()` to force the loading of a topic 
only if it already exists

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to