Hi Ilya, It did compiled...but it is not inserting records to ignite at all...
I waited for 20 mins for it to insert and terminated and there are no exceptions in the ignite log. Could you please suggest the right syntax to enable the streaming using jdbc thin driver..and my key concern is performance...Inserting 1 million records with 90 columns each row should get completed in less than 30 sec is what we are looking for... Is it possible with ignite? Thanks & Regards, Sriveena ________________________________ From: Ilya Kasnacheev <ilya.kasnach...@gmail.com> Sent: 06 September 2018 17:24:13 To: user@ignite.apache.org Subject: Re: Batch insert into ignite using jdbc thin driver taking long time Hello! I'm not sure but it doesn't look right to me. Does it compile? Note that you also need to SET STREAMING OFF after data load is complete. -- Ilya Kasnacheev чт, 6 сент. 2018 г. в 14:42, Sriveena Mattaparthi <sriveena.mattapar...@ekaplus.com<mailto:sriveena.mattapar...@ekaplus.com>>: Thanks Ilya. Will try using together. Please correct if the below statement work. getConnection().createStatement().execute("SET STREAMING ON"); Regards, Sriveena From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com<mailto:ilya.kasnach...@gmail.com>] Sent: Thursday, September 06, 2018 3:28 PM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: Batch insert into ignite using jdbc thin driver taking long time Hello! I don't see why not. Have you tried? Any difference in run time? Regards, -- Ilya Kasnacheev чт, 6 сент. 2018 г. в 6:20, Sriveena Mattaparthi <sriveena.mattapar...@ekaplus.com<mailto:sriveena.mattapar...@ekaplus.com>>: Hi Ilya, Can we cobimbe both of them together I mean 1. SET STREAMING ON; 2. JDBC thin driver batch insert (pstmt.executeBatch()) Thanks & Regards, Sriveena From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com<mailto:ilya.kasnach...@gmail.com>] Sent: Wednesday, September 05, 2018 7:02 PM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: Batch insert into ignite using jdbc thin driver taking long time Hello! Have you tried streaming mode? https://apacheignite-sql.readme.io/docs/set<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapacheignite-sql.readme.io%2Fdocs%2Fset&data=02%7C01%7CSriveena.Mattaparthi%40ekaplus.com%7C7d329f7496a845c707bb08d61333fb1d%7C2a5b4e9716be4be4b2d40f3fcb3d373c%7C1%7C0%7C636717511328312021&sdata=WfZ7m34afylAJv0PZ0GRo2o7mIQVxR6f%2BCb2MuQUj3M%3D&reserved=0> Regards, -- Ilya Kasnacheev ср, 5 сент. 2018 г. в 15:44, Sriveena Mattaparthi <sriveena.mattapar...@ekaplus.com<mailto:sriveena.mattapar...@ekaplus.com>>: Hi, I am trying to batch insert 300000 records into ignite cache(on remote server) using jdbc thin driver. It is taking nearly 4mins to complete this operation. Please advise. Thanks & Regards, Sriveena “Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.” “Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.” “Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.” “Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.”