leizhiyuan opened a new issue, #1534:
URL: https://github.com/apache/rocketmq-dashboard/issues/1534
## Motivation
The Tencent Cloud provider (`provider/tencent`, Trocket v20230308 OpenAPI)
is already wired
for instance onboarding, but the `TencentInstanceProvider` only threw
`UnsupportedOperationException`
for every topic operation. Users cannot list, create, update or delete
topics on a Tencent Cloud
RocketMQ 5.x instance from the Topic management page.
## What this adds
Implements the instance-scoped topic operations for the Tencent provider by
mapping to the
Trocket OpenAPI:
- **List topics** - `DescribeTopicList` with pagination and type/name/remark
filtering; per-topic
created/updated timestamps enriched via `DescribeTopic` (millisecond
timestamps).
- **Create topic** - `CreateTopic` (name, type, queue num, remark); rejects
`LiteTopic` which Tencent
Cloud does not support.
- **Update topic** - `ModifyTopic` (remark / queue num).
- **Delete topic** - `DeleteTopic`.
- **Topic consumers** - `DescribeTopic` subscription data (group, consume
type, message model, lag).
- **Topic count** - cheap list path (no N+1 detail lookups) so instance
listings stay fast.
Frontend: the topic page date formatter now renders missing timestamps as
`-` instead of
`1970-01-01 08:00:00`, and the no-instance reset no longer calls `setState`
synchronously inside
the effect (`react-hooks/set-state-in-effect`).
## Scope
This is scoped to the `rocketmq-studio` branch where the Tencent provider
lives. It only touches
topic management; consumer-group, message and trace operations for Tencent
remain unsupported.
## Notes
This branch (from `apache/rocketmq-studio`) also carried a few pre-existing
build/startup fixes
that block the project from compiling and booting (e.g. `Pattern` import in
`AlertService`,
`MessageExt#getProperties()` on rocketmq-tools 5.5.0, `@Autowired` on
`GrafanaDashboardService`
constructor). They are kept in a separate commit so the functional change is
reviewable on its own.
--
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]
