[
https://issues.apache.org/jira/browse/IGNITE-10645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729255#comment-16729255
]
Ignite TC Bot commented on IGNITE-10645:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2653576]]
* IgniteCacheWithIndexingTestSuite:
CacheBinaryKeyConcurrentQueryTest.testPutAndQueries - 0,0% fails in last 374
master runs.
{color:#d04437}Cache (Restarts) 2{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2653570]]
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithPutEightNodesTwoBackups - 0,0%
fails in last 398 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithTxTwoNodesOneBackup - 0,0%
fails in last 398 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithTxSixNodesTwoBackups - 0,0%
fails in last 398 master runs.
* IgniteCacheRestartTestSuite2:
IgniteCacheAtomicNodeRestartTest.testRestartWithTxFourNodesOneBackups - 0,0%
fails in last 398 master runs.
{color:#d04437}Data Structures{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2653584]]
* IgniteCacheDataStructuresSelfTestSuite:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups
- 0,0% fails in last 363 master runs.
* IgniteCacheDataStructuresSelfTestSuite:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutTenNodesTwoBackups
- 0,0% fails in last 363 master runs.
* IgniteCacheDataStructuresSelfTestSuite:
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups
- 0,0% fails in last 363 master runs.
{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2653554]]
{color:#d04437}Thin client: Python{color} [[tests 1 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2653601]]
*
tests.test_binary.test_sql_write_as_binary[localhost-None-_SSLMethod_PROTOCOL_TLSv1_1-None-None-0-10800-False-None-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-None-None]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2653608&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 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)
