kssumin commented on issue #10476:
URL:
https://github.com/apache/shardingsphere/issues/10476#issuecomment-3397481844
Hi @strongduanmu,
Thanks for the question!
From my understanding, this feature should work in both Standalone and
Cluster modes,
not only in Cluster mode — but please correct me if I’m misunderstanding.
### My understanding
- In Standalone mode, YAML is only used for initial bootstrap.
- Runtime changes via DistSQL are persisted to the configured repository
(JDBC or in-memory), not to YAML.
- When using the default in-memory repository, changes are volatile and will
be lost after restart.
- When using a JDBC repository, the changes are persisted and reloaded on
restart.
- This follows the same behavior as other DDL operations (like DROP/CREATE
TABLE),
where the physical operation succeeds and rules can be updated manually
via DistSQL.
### Implementation approach
Based on that, I kept the behavior consistent:
- Physical tables are renamed automatically.
- Sharding/broadcast rules remain unchanged.
- Users can update those rules manually via DistSQL.
- Changes are persisted in the repository.
Could you please confirm if my understanding of how Standalone mode handles
persistence is correct?
If there are any details or edge cases I should handle differently, I’d
really appreciate your guidance.
Thanks again!
--
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]
