No, I mean passing less values for the column than it actually has. I tested again and for the arguments (column values) that I don't pass, it ignores them and just updates the existing ones. But if the table has columns with NOT NULL restriction, then it does not throw any exception and it should. My table description: CREATE TABLE badjoras (
house_id STRING,
tip_id STRING,
created_ts BIGINT,
status STRING NOT NULL,
status_ts BIGINT,
visible BOOLEAN NOT NULL,
visible_ts BIGINT,
PRIMARY KEY (house_id, tip_id)
) PARTITION BY HASH(house_id) PARTITIONS 3 STORED AS KUDU; What I'm doing: try {
if (kc.tableExists(TABLE_BADJORAS)) {
KuduSession session = kc.newSession();
KuduTable table = kc.openTable(TABLE_BADJORAS);
Upsert upst = table.newUpsert();
PartialRow row = upst.getRow();
row.addString("house_id", "0123456789");
row.addString("tip_id", "987654321");
session.apply(upst);
System.out.println("overflowed " + session.getPendingErrors().isOverflowed());
System.out.println("size= " + session.getPendingErrors().getRowErrors().length);
for (RowError r : session.getPendingErrors().getRowErrors()) {
System.out.println("error status " + r.getErrorStatus());
System.out.println("error Operation " + r.getOperation().toString());
System.out.println("error TsUUID " + r.getTsUUID());
System.out.println("error toString " + r.toString());
}
LOGGER.info("KUDU BADJORAS" + houseId + "+" + tId + " upserted");
session.close();
}
} catch (KuduException e) {
e.printStackTrace();
} finally {
LOGGER.info("KUDU BADJORAS" + houseId + " run time = " + (System.currentTimeMillis() - start));
} Using my sample code, when a row is upserted in a table with columns with NOT NULL restrictions it never throws the KuduException, thus it doesn't enter the catch clause. I've even tried to catch some errors like you recommended, but I got no errors when using such an upsert operation.
... View more
