Unfortunately it's not our case.
Pay attention that you have different PK classes:
*com.inspur.edp.qdp.config.api.ketype.PubPartionKeys_1_7*
and
*com.inspur.edp.qdp.config.keytype.PubPartionKeys_1_7*
are different.
Also note that BinaryObject to put as PK must have exactly the same fields
(count an
Here is my insert code.
BinaryObjectBuilder builder =
ignite.binary().builder("com.inspur.edp.caf.db.dbaccess.DynamicResultRow");
Map datasBinary = new HashMap<>();
IgniteDataStreamer stmr = ignite.dataStreamer("TBDATA_GLFY_1");
..
..
for(int i = 0; i < meta.length; i++){
b
Hi,
It seems we have solved that problem.
We need to see your code where you insert data via BinaryObject and SQL
both.
сб, 2 апр. 2022 г. в 12:51, y :
> Hi Igniters:
>
> First, I use custom primary key classes and *BinaryObject* to insert
> several pieces of data. And then, when I use the *INSER
I think we’d need to see how you created the table to help you.
> On 2 Apr 2022, at 10:51, y wrote:
>
> Hi Igniters:
>
> First, I use custom primary key classes and BinaryObject to insert several
> pieces of data. And then, when I use the INSERT statement to insert data, the
> following error
Hi Igniters:
First, I use custom primary key classes and BinaryObject to insert several
pieces of data. And then, when I use the INSERT statement to insert data, the
following error occurs:
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to update
keys on primary node.
at
