zt9788 commented on issue #22790:
URL:
https://github.com/apache/shardingsphere/issues/22790#issuecomment-1346217916
> > @Zhai6319
> > +1
> > > > @Zhai6319
> > > > > The main problem for me is that the metadata registered in nacos
has no format at all. It is difficult to change the metadata parameters
> > > >
> > > >
> > > > Looks there's newline in content. I didn't try Nacos before, it
works in ZooKeeper, and ShardingSphere just persist key-value to registry
center via SPI, it should work on Nacos too.
> > > > Could you debug `NacosRepository.put/update` to check whether the
value contains correct newline (one char `\n`, but not two chars `\` and `n`)?
> > >
> > >
> > > Can this metadata be registered through the configuration center of
nacos?
> > > What is the purpose of registering as a service?
> > > Do these all need to be connected in the form of IP+ports and each
metadata instance of nacos
> >
> >
> > +1 I think ShardingShpere-JDBC depends more on user configuration
Sharding-Porxy to use cluster by it self
>
> @sandynz About this question
>
> I think the article can be driven by jdbc Provide
org.apache.shardingsphere.driver SPI of ShardingSphereDriver The community can
expand relevant plug-ins For example:
spring.datasource.url=jdbc:shardingsphere:classpath:xxx.yaml The classpath in
this configuration can be configured as nacos, spring cloud config or other
configuration centers
jdbc:shardingsphere:{nacos/spring-cloud-config}:{ip}:{port}:{username}:{password}:{namespace}:xxx.yaml
Then drive plug-ins to obtain different configurations
@sandynz
I mean, the JDBC url: part gives users more choices
JDBC and SpringCloud cannot be used together in a lightweight way, while
using Cluster increases maintenance costs
> Cluster mode is optional for Proxy and JDBC
--
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]
