沈佳庆 created IGNITE-14959:
----------------------------
Summary: jdbc thin client turns on Partition awareness, which
results in slower data insertion
Key: IGNITE-14959
URL: https://issues.apache.org/jira/browse/IGNITE-14959
Project: Ignite
Issue Type: Improvement
Components: clients
Reporter: 沈佳庆
With Apache Ignite Release 2.9.1，I created a table using jdbc connection and
enabled partition awareness. I found that partition awareness took effect when
I query data, and the query speed became faster, but when I inserted data, The
client always cannot obtain the corresponding partition information sent by the
server, but each query will go through the process of partition perception
computing node id, but the partition information is null and cannot be
calculated.I think the above process of inserting data through partition
perception is redundant , because it doesn’t work, it slows down my data
insertion speed.
This is my connection information:
jdbc:ignite:thin://ignite-0.ignite:10800,ignite-1.ignite:10800,ignite-2.ignite:10800,ignite-3.ignite:10800,ignite-4.ignite:10800?partitionAwareness=true
This is my table information:create table demo(id varchar,name varchar ,PRIMARY
KEY (id))；
insert into demo(id,name) values (?,?)
select id,name from demo where id = ?
I am not sure if there is a problem with my use, or if it has other uses
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
