ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10645) SQL properties ownership flag should be set at configuration parsing, not query execution.
Date Sat, 29 Dec 2018 19:11:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730793#comment-16730793

Ignite TC Bot commented on IGNITE-10645:

{panel:title=--&gt; Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=2679781]]
* IgniteCacheWithIndexingTestSuite: CacheBinaryKeyConcurrentQueryTest.testPutAndQueries -
0,0% fails in last 407 master runs.

[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2679815&amp;buildTypeId=IgniteTests24Java8_RunAll]

> 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
> But we already have all necessary info to set this field at processing time.

This message was sent by Atlassian JIRA

View raw message