[
https://issues.apache.org/jira/browse/IGNITE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742002#comment-16742002
]
Vladimir Ozerov commented on IGNITE-10645:
------------------------------------------
[~pkouznet], my comments:
# {{QueryUtils.processBinaryMeta}} - what is the reason to add
{{!F.isEmpty(keyFields) && isKeyClsSqlType}} check? Will it be valid when _KEY
alias is set? It is not obvious how this check is related to the problem
described in the ticket
The rest looks fine.
> SQL properties ownership flag should be set at configuration parsing, not
> query execution.
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-10645
> URL: https://issues.apache.org/jira/browse/IGNITE-10645
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Pavel Kuznetsov
> Assignee: Pavel Kuznetsov
> Priority: Major
> Fix For: 2.8
>
>
> At processing time, query entities are transformed and validated, table
> descriptors with properties are created.
> Now in some case (thre's no keyFields and key is of complex non-sql type),
> ownership flag of query property is calculated at execution time (for example
> at first put()):
> https://github.com/apache/ignite/blob/dcdb27a24a450f63487290360b265e1570534629/modules/core/src/main/java/org/apache/ignite/internal/processors/query/property/QueryBinaryProperty.java#L132
> So we can't access metadata, that uses this not-yet-initialized field before
> we put the data.
> But we already have all necessary info to set this field at processing time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
