Maybe I didn't describe it clearly. How to configure Ignite, you can achieve distributed without external configuration, and then directly use the sqline command to connect, for distributed query operations. Should it be through the configuration file below the installation file? I see that the configuration file that comes with it seems to be the format that Spring requires. Is there any relation between the two?
[email protected] From: Vladimir Pligin Date: 2019-07-04 20:27 To: user Subject: Re: Distributed Cluster Deployment Hi, Spring here is just a convenient way of configuration building. Ignite is not tightly bound to it. You're able to construct everything programmatically. For example here https://apacheignite.readme.io/docs/tcpip-discovery you can switch example from "XML" to "Java". And Spring xml configuration <bean class="org.apache.ignite.configuration.IgniteConfiguration"> ... <property name="discoverySpi"> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> <property name="ipFinder"> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder"> <property name="multicastGroup" value="228.10.10.157"/> </bean> </property> </bean> </property> </bean> turns into TcpDiscoverySpi spi = new TcpDiscoverySpi(); TcpDiscoveryMulticastIpFinder ipFinder = new TcpDiscoveryMulticastIpFinder(); ipFinder.setMulticastGroup("228.10.10.157"); spi.setIpFinder(ipFinder); IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setDiscoverySpi(spi); Ignition.start(cfg); Does it make sense? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
