Re: count not updated through SQL using DataStreamer

Hi Calvin, Cache.size and SELECT COUNT(*) are not always equal in Ignite. Could you please tell what arguments did you pass to IgniteDataStreamer.addData method? Sent from my iPhone > On 16 May 2019, at 23:40, Banias H wrote: > > Hello Ignite experts, > > I am very new to Ignite. I am

Integrity of write behind

Hi, What happens if a node goes down while write behind is in progress on a cache that's persisting to the database? Can the task of persistence be carried on exactly where it failed by a back up node? Are cache entries flagged when they have been successfully persisted so that another node

count not updated through SQL using DataStreamer

Hello Ignite experts, I am very new to Ignite. I am trying to ingest 15M rows of data using DataStreamer into a table in a two-node Ignite cluster (v2.7) but run into problems of not getting the data through running SQL on DBeaver. Here is the list of steps I took: 1. Start up two nodes using

Re: SNI support for JDBC TLS

Hello! TLS is supported by thin client: https://apacheignite-sql.readme.io/docs/jdbc-driver#jdbc-thin-driver Moreover, with sslFactory parameter you can specify SSL factory class, which can be customized to initialize SNI properly. Can you try it with SSL factory, see if you can get SNI to work?

Re: SNI support for JDBC TLS

> Do I understand correctly that you want to have several services use same > ingress point, i.e. host and port, to access multiple services in your K8 > cluster? That's correct. > Can you guide me whether this controller will keep SSL on (so that service > has to support SSL too) or if it

Re: SNI support for JDBC TLS

Hello! Do I understand correctly that you want to have several services use same ingress point, i.e. host and port, to access multiple services in your K8 cluster? Can you guide me whether this controller will keep SSL on (so that service has to support SSL too) or if it will strip SSL so that

Re: Need help with Linux ODBC Driver

Thanks Igor. I also noticed that the Linux ODBC Driver deserializes the Ignite UUID data type into a byte[] instead of the .Net Guid type. That is contrary to what is stated in the documentation ( https://apacheignite-sql.readme.io/docs/data-types#section-uuid). SQL Example: CREATE TABLE MyTable

SNI support for JDBC TLS

Hi! I was pleased to see that the JDBC driver supports TLS[1]. However, after inspecting traffic with Wireshark, it doesn't appear to support Server Name Indication. My use case is Ignite on Kubrnetes, behind an ingress controller that uses SNI to route connections to services. I note that the

Re: Failed to find affinity server node

Hi, [14:32:52] Topology snapshot [ver=63, servers=0, clients=1, CPUs=8, offheap=0.1GB, heap=1.7GB] Your topology doesn't have any server nodes. Can you please check all the configuration files used in your sample, are there any differences in discoverySpi section? -- Sent from:

Re: Store raw binary value in Apache Ignite through thin python client

Hi, Thank you for your feedback! Just for information - I've also created a stackoverflow question (https://stackoverflow.com/questions/56127565/store-raw-binary-value-in-apache-ignite-through-thin-python-client) related to this topic > I'll post the JIRA issue link there. -- Sent from:

Re: Store raw binary value in Apache Ignite through thin python client

Hi! Thanks for the report! Seems like the implementation of serialization of primitive arrays is not optimal. I created a JIRA ticket for this issue: https://issues.apache.org/jira/browse/IGNITE-11854 Denis вт, 14 мая 2019 г. в 13:53, kulinskyvs : > I'm trying to save some raw binary data into

Ignite 'complex' type

Hello Ignite experts, I am trying to store a python value of type Tuple[Dict[str, float], bytes] in an Ignite cache. However, doing that without type hints I get: TypeError: Type `array of None` is invalid Do you know if this is possible? Kind regards, Stéphane Thibaud

Re: java.lang.NoSuchMethodError: org.apache.ignite.IgniteCache.getName()Ljava/lang/String;

Tomasz, There is no such Ignite version as 2.8.0. The latest one is 2.7.0. Please make sure that all dependencies are resolved correctly. Denis пн, 13 мая 2019 г. в 12:50, Tomasz Prus : > Hi, > i'm trying to set up Ignite 2.8.0 in our application but i get such error: > >

Re: Ignite WebSessionFilter client threads eating up CPU usage

Patrick, Could you explain a bit more, why do you think that striped pool is the reason? Striped pool is where cache operations happen. So, if you see, that it consumes a lot of CPU, then it probably means, that a lot of cache operations are coming to the cluster. You can record a JFR and see,

Re: Ignite in client Mode: outofMemory error with TCP discovery

Hi, I don’t think that it is directly related to the discovery message itself. Even before that you have long jvm pauses, probably it was a full gc, looks like you don’t have enough heap on the client. What do you there? What kind of operations do you run? I’d suggest collecting heap dump and

Re: Timestamp with Python thin client

I see. Thank you. I am still a bit unsure about what the second value in the tuple represents. Are these indeed the nanoseconds? Apparently a Python datetime can have differing precisions (perhaps depending on platform)... Kind regards, Stéphane Thibaud 2019年5月16日(木) 0:10 Igor Sapego : > I