Aias00 opened a new issue, #793:
URL: https://github.com/apache/rocketmq-dashboard/issues/793

   ### Problem
   
   The Studio LiteTopic backend currently returns hard-coded sample data by 
default. A fresh backend can show fake LiteTopic patterns, sessions, quota 
usage, and successful TTL extension even when no real LiteTopic 
provider/AdminClient integration is available.
   
   This is misleading for META-01 LiteTopic management because users may treat 
the sample data as real cluster state.
   
   ### Evidence
   
   
`server/src/main/java/org/apache/rocketmq/studio/instance/topic/LiteTopicService.java`
 currently:
   
   - returns `sampleItems()` from `listLiteTopics(...)`
   - builds a synthetic session in `getSession(...)`
   - returns fixed quota values from `getQuota(...)`
   - returns `supported=true` from `getCapability()`
   - validates `extendTTL(...)` but does not execute a real operation
   
   ### Expected behavior
   
   Until a real LiteTopic provider/AdminClient integration exists, the default 
backend should not fabricate resources or report fake successful write 
operations.
   
   A safer default is:
   
   - list APIs return an empty result rather than sample resources
   - capability reports unsupported
   - session/detail and TTL update operations return an explicit unsupported 
response
   - tests should lock the no-sample-data behavior
   
   ### Scope
   
   This is in the RocketMQ Studio contest scope under Track 1 / META-01 
LiteTopic management. It is a small safety fix that prevents fake management 
data before full LiteTopic provider integration lands.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to