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

Ignite TC Bot commented on IGNITE-10291:
----------------------------------------

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 2{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=2422400]]
* IgniteBinaryCacheQueryTestSuite2: 
DynamicColumnsConcurrentAtomicReplicatedSelfTest.testConcurrentPutRemove - 0,0% 
fails in last 100 master runs.

{color:#d04437}PDS (Indexing){color} [[tests 
8|https://ci.ignite.apache.org/viewLog.html?buildId=2422455]]
* IgnitePdsWithIndexingCoreTestSuite: 
IgniteLogicalRecoveryTest.testRecoveryOnJoinToInactiveCluster - 0,0% fails in 
last 100 master runs.
* IgnitePdsWithIndexingCoreTestSuite: 
IgniteLogicalRecoveryTest.testRecoveryOnDynamicallyStartedCaches - 0,0% fails 
in last 100 master runs.
* IgnitePdsWithIndexingCoreTestSuite: 
IgnitePersistentStoreCacheGroupsTest.testCreateDropCache - 0,0% fails in last 
100 master runs.
* IgnitePdsWithIndexingCoreTestSuite: 
IgniteLogicalRecoveryTest.testRecoveryOnJoinToActiveCluster - 0,0% fails in 
last 100 master runs.
* IgnitePdsWithIndexingCoreTestSuite: 
IgnitePersistentStoreCacheGroupsTest.testCreateDropCache2 - 0,0% fails in last 
100 master runs.

{color:#d04437}Basic 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=2422418]]
* IgniteBasicTestSuite: 
IgniteServiceReassignmentTest.testNodeStopWhileThereAreCacheActivitiesInServiceProcessor
 - 0,0% fails in last 100 master runs.

{color:#d04437}SPI{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=2422405]]
* IgniteSpiTestSuite: TcpClientDiscoverySpiMulticastTest.testJoinWithMulticast 
- 0,0% fails in last 100 master runs.

{color:#d04437}Queries 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=2422467]]
* IgniteBinaryCacheQueryTestSuite: 
IgniteDynamicSqlRestoreTest.testMergeChangedConfigOnInactiveGrid - 0,0% fails 
in last 100 master runs.
* IgniteBinaryCacheQueryTestSuite: 
IgniteDynamicSqlRestoreTest.testTakeConfigFromJoiningNodeOnInactiveGrid - 0,0% 
fails in last 100 master runs.

{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=2422397]]
* JdbcThinWalModeChangeSelfTest.testSharedCacheGroup (last started)

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2422473&buildTypeId=IgniteTests24Java8_RunAll]

> Unable to find row by index created on partial baseline topology
> ----------------------------------------------------------------
>
>                 Key: IGNITE-10291
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10291
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, persistence, sql
>    Affects Versions: 2.4, 2.5, 2.6
>            Reporter: Pavel Vinokurov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 2.8
>
>         Attachments: Reproducer.java
>
>
> Steps to reproduce:
> 1. Start two nodes cluster with persistence.
> 2. Create table
> CREATE TABLE PERSON (
>  FIRST_NAME VARCHAR,
>  LAST_NAME VARCHAR,
>  ADDRESS VARCHAR,
>  LANG VARCHAR,
>  BIRTH_DATE TIMESTAMP,
>  CONSTRAINT PK_PESON PRIMARY KEY (FIRST_NAME,LAST_NAME,ADDRESS,LANG)
> ) WITH "key_type=PersonKeyType, CACHE_NAME=PersonCache, 
> value_type=PersonValueType, 
> AFFINITY_KEY=FIRST_NAME,template=PARTITIONED,backups=1"
> Insert 1000 rows.
> 3. Stop the second node.
> 4. Create index
> create index PERSON_FIRST_NAME_IDX on  PERSON(FIRST_NAME)
> 5. Start the second node
> 6. Perform select query for each row:
> select * from PERSON use index(PERSON_FIRST_NAME_IDX) 
> where 
> FIRST_NAME=?
> and LAST_NAME=?
> and ADDRESS=?
> and LANG  = ? 
> Result: The select doesn't return row in half of cases.
> The reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to