Re: Slow select distinct query on primary key

Here is the explain plan. 0: jdbc:ignite:thin://127.0.0.1/> EXPLAIN SELECT DISTINCT ACCOUNT_ID FROM PERF_POSITIONS; 'PLAN' 'SELECT DISTINCT __Z0.ACCOUNT_ID AS __C0_0 FROM PUBLIC.PERF_POSITIONS __Z0 /* PUBLIC."_key_PK" */' 'SELECT DISTINCT __C0_0 AS ACCOUNT_ID FROM PUBLIC.__T0 /*

Re: Slow select distinct query on primary key

Hi, I tried the additional index as you suggested, but it did not improve the query time. The query still takes 58-61 seconds. CREATE INDEX PERF_POSITIONS_IDX ON PERF_POSITIONS (ACCOUNT_ID); CREATE INDEX PERF_POSITIONS_IDX2 ON PERF_POSITIONS (ACCOUNT_ID, EFFECTIVE_DATE, FREQUENCY, SOURCE_ID,

Re: Slow select distinct query on primary key

Here is my Ignite server configuration. http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd;>

Slow select distinct query on primary key

I am running below SQL query via Sqlline.sh, and I think it is running too slow (57s). Could someone confirm whether this response time is normal, or I am doing something wrong? Here is the query: 0: jdbc:ignite:thin://127.0.0.1/> SELECT DISTINCT ACCOUNT_ID FROM PERF_POSITIONS;

Re: Read SQL table via cache api

Hi Andrei, I got this to work by setting the server and client time zones to be the same. So what happened was that I had created the table and inserted the record using Sqlline.sh on the server host. That must have stored the effective_date field in the key based on the server's time zone

Re: Read SQL table via cache api

Hi Andrei, I captured below logs with the -DIGNITE_QUIET=false flag. There is a 5-hour difference between the two time zones. Server Log ignite-ef771a6b.log Client Log ignite-86fd5276.log

Re: Read SQL table via cache api

Another observation is that if I take out the effective_date field (Timestamp) from the key, and use only the Int and Double columns as the primary keys, the server finds it without any problem. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Read SQL table via cache api

Hi Andrei, Thank you for your reply. Here is the server log. However, I do not see any relevant information in it. The cache get request was made from the client between line 117 (client joins the topology) and 127 (client leaves the topology). ignite-db357bff.log

Re: Read SQL table via cache api

Hi Andrei, I have figured this out after several hours of troubleshooting today. I had the Ignite server process, which hosted the table/cache, running on a Linux host (CentOS7). On the other hand, I was running the client code on a Macbook. It seems that the two platform was deserializing the

Read SQL table via cache api

I ran below SQL from Ignite Sqlline which creates a table and inserts one entry. I am trying to query that entry using cache api. However, the value always returns null. ## SQL CREATE TABLE SIMPLE_TABLE ( ACCOUNT_ID INT, SECURITY_ALIAS INT, POSITION_TYPE