kutouziUk commented on issue #34556: URL: https://github.com/apache/shardingsphere/issues/34556#issuecomment-2633285482
> * The design of shardingsphere only reading `seata.conf` can be traced back to shardingsphere 4.x. At that time, I was not a shardingsphere committer. I would say that this file appeared very abruptly. But there is indeed no issue on the shardingsphere side to propose a new configuration solution to replace `seata.conf`. Yes, ZooKeeper is now supported in version 5.x as a registry, and it's even better for seata.conf to read the configuration from ZooKeeper or another configuration center like NACOS -- 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]
