It does work as you described. Both JDBC and ODBC use the same 10800 port be
default unless you override it with ClientConnectorConfiguration. Thanks
again!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks for the clarification Denis, I will give that a try!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hey guys and gals,
Is it possible to use ODBC and JDBC connections on the same Ignite cluster
in version 2.4? I see that the
org.apache.ignite.configuration.OdbcConfiguration class was deprecated as of
2.1 in favor of
ClientConnectorConfiguration and
IgniteConfiguration.setClientConnectorConfigur
Denis,
Sorry for the late reply as I have been away from a computer for a few days.
Today, I do not use Kubernetes in production, it is only in use for POC work
so that I can understand how to utilize the K8s platform and test if it
works well with Ignite. So far, Ignite seems to be playing nicely
Ok thank you all for the tips, I will give it a try!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hey guys and gals!
I have created a development environment for Ignite 2.3 Native Persistence
on Kubernetes 1.9.3 and have it up and running successfully. I then
attempted to activate one of my clusters via a Java client call and
discovered that the TcpDiscoveryKubernetesIpFinder doesn't support th
I just ran into this same issue recently and it turns out that the
permissions given to the default ServiceAccount in Kubernetes Role-based
access control (RBAC) are not high enough to allow for the
TcpDiscoveryKubernetesIpFinder to talk to the kubernetes service at
"https://kubernetes.default.svc.
