Re: Query timeout

Hi, Taras. We try to connect to server via NetBeans 8.2 for development purposes. In Services tab we add Ignite 2.8.0 JDBC driver (ignite-core-2.8.0.jar) and choose org.apache.ignite.IgniteJdbcThinDriver. To reproduce long running query we create 2 tables: create table if not exists TEST (kField l

Re: Query timeout

I try jdbc:ignite:thin://192.168.1.138:10800;queryTimeout=1 and jdbc:ignite:thin://192.168.1.138:10800?queryTimeout=1 both. Query is still executed more then 1 sec without exception. Is this parameter supported in 2.8.0? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Query timeout

Hi all, Is there any way to set query timeout parameter in JDBC url? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Long running query

Yes, thats exactly what we need. Thanx. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Long running query

Hello, We have two tables LD (8 000 000 rows) and DRUGS (130 000 rows). Following query is executed ~7 minutes that is significantly longer then in RDBMS (~1,5 sec): select d.drug_id, d.drug_name, ld.price from drugs d left outer join ld on d.drug_id = ld.drug_id and ld.org_id = 264; Explain for q

Async query

Hi all. I found that IgniteCache.withAsync() is deprecated in v.2.3.0. How to execute multiple SqlFieldsQuery asynchronously now? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Primary key bug

Hello, Alexey. Thank you for clarification. Is there any way to use in Ignite tables created directly in H2? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Primary key bug

Hi, Suppose we have following DDL: CREATE TABLE TEST ( org_id INT NOT NULL, drug_id INT NOT NULL, price DOUBLE NULL, qtty INT NULL, inter_id INT NULL, trade_id INT NULL, med_id INT NULL, medp_id INT NULL, avgprc DOUBLE NULL, avgprc_region DOUBLE NULL, region_id INTEGER NULL,