[IGNITE-6265] BinaryObject fields nested deeper than one level cannot be updated via SQL

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.1
• Component/s: sql
• Assignee: Unassigned
• Reporter: Alexandr Fedotov
• Created: 05/Sep/17 09:23
• Updated: 14/Feb/19 08:29
• Resolved: 14/Feb/19 08:29

Description

SQL update of a BinaryObject field nested deeper than one level throws an exception

Caused by: class org.apache.ignite.IgniteCheckedException: Non-binary object received as a result of property extraction [parent=org.apache.ignite.internal.processors.query.property.QueryBinaryProperty@1e86486b, propName=nestedObj, obj=org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl@1fc7875]
at org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.value(QueryBinaryProperty.java:105)
at org.apache.ignite.internal.processors.query.property.QueryBinaryProperty.setValue(QueryBinaryProperty.java:159)
at org.apache.ignite.internal.processors.query.h2.H2RowDescriptor.setColumnValue(H2RowDescriptor.java:348)

The problem is that only a BinaryObject is expected in the following part of the QueryBinaryProperty.value method

if (!ctx.cacheObjects().isBinaryObject(obj))
    throw new IgniteCheckedException("Non-binary object received as a result of property extraction " + "[parent=" + parent + ", propName=" + propName + ", obj=" + obj + ']');

Corresponding SQL CRUD tests should be added for the nested BinaryObjects.

Issue Links

• relates to: IGNITE-6266 Nested BinaryObject fields cannot be inserted via SQL
• relates to: IGNITE-6268 Add documentation for SQL CRUD operations with nested BinaryObject fields
• links to: User list question