[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804908#comment-16804908
]
Ignite TC Bot commented on IGNITE-5962:
---
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3446506buildTypeId=IgniteTests24Java8_RunAll]
> Increase max length of index name
> -
>
> Key: IGNITE-5962
> URL: https://issues.apache.org/jira/browse/IGNITE-5962
> Project: Ignite
> Issue Type: Improvement
> Components: general, sql
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length
> was reduced from 768 to 256 bytes. If we need to support longer names, we
> need to change format of metastore data pages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804430#comment-16804430
]
Ignite TC Bot commented on IGNITE-5962:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3338626]]
* IgniteSpiTestSuite: TcpDiscoveryClientSuspensionSelfTest.testTwoServers -
0,0% fails in last 389 master runs.
{color:#d04437}MVCC PDS 2{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=3446502]]
* IgnitePdsMvccTestSuite2:
WalDeletionArchiveLogOnlyTest.testCorrectDeletedArchivedWalFiles - 0,0% fails
in last 358 master runs.
* IgnitePdsMvccTestSuite2:
LocalWalModeChangeDuringRebalancingSelfTest.testWalDisabledDuringRebalancingWithPendingTxTracker
- 0,0% fails in last 358 master runs.
{color:#d04437}MVCC PDS 4{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3446504]]
* IgnitePdsMvccTestSuite4:
IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testClientReconnectClusterDeactivateInProgress
- 0,0% fails in last 386 master runs.
{color:#d04437}Cache 5{color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=3446458]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsWithPersistence[ATOMIC]
- 0,0% fails in last 163 master runs.
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithPersistence[ATOMIC]
- 0,0% fails in last 163 master runs.
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithPersistence[TRANSACTIONAL]
- 0,0% fails in last 163 master runs.
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadOnlySafeWithPersistence[ATOMIC]
- 0,0% fails in last 163 master runs.
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsWithPersistence[TRANSACTIONAL]
- 0,0% fails in last 163 master runs.
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillCrdWithPersistence[ATOMIC]
- 0,0% fails in last 163 master runs.
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithDelayWithPersistence[ATOMIC]
- 0,0% fails in last 163 master runs.
{color:#d04437}PDS 2{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3446473]]
* IgnitePdsTestSuite2:
ClientAffinityAssignmentWithBaselineTest.testRejoinWithCleanLfs - 0,0% fails in
last 396 master runs.
* IgnitePdsTestSuite2:
IgnitePdsExchangeDuringCheckpointTest.testExchangeOnNodeJoin - 0,0% fails in
last 396 master runs.
* IgnitePdsTestSuite2:
LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge - 0,0% fails
in last 396 master runs.
{color:#d04437}MVCC Cache 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3446492]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3446506buildTypeId=IgniteTests24Java8_RunAll]
> Increase max length of index name
> -
>
> Key: IGNITE-5962
> URL: https://issues.apache.org/jira/browse/IGNITE-5962
> Project: Ignite
> Issue Type: Improvement
> Components: general, sql
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length
> was reduced from 768 to 256 bytes. If we need to support longer names, we
> need to change format of metastore data pages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804115#comment-16804115 ] Pavel Kuznetsov commented on IGNITE-5962: - [~vozerov] I've fixed typeId in case binary marshaller is not used. Note that in this case at validation we don't have access to the values class, so we expect the worst case: longest possible int. > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794935#comment-16794935 ] Pavel Kuznetsov commented on IGNITE-5962: - visa can be viewed at https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/6209/head=Latest 1) Inspections failed due to internal error. (https://ci.ignite.apache.org/viewLog.html?buildId=3338689) 2) TcpDiscoveryClientSuspensionSelfTest.testTwoServers - failure is not reproduced in previous run (before merge master) and is not reproduced locally. (https://ci.ignite.apache.org/viewLog.html?buildId=3338626) > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794578#comment-16794578 ] Pavel Kuznetsov commented on IGNITE-5962: - rerun : https://ci.ignite.apache.org/viewLog.html?buildId=3338711; > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792601#comment-16792601 ] Pavel Kuznetsov commented on IGNITE-5962: - [~vozerov] TC bot was unavailable at that moment, so I issued runAll manually. See bot comment based on : >runAll rerun : https://ci.ignite.apache.org/viewQueued.html?itemId=3287892 > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792598#comment-16792598
]
Ignite TC Bot commented on IGNITE-5962:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3287846]]
* IgniteCacheTestSuite7:
TxRollbackAsyncWithPersistenceTest.testSynchronousRollback - 0,0% fails in last
316 master runs.
{color:#d04437}Thin client: Python{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3287869]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3287892buildTypeId=IgniteTests24Java8_RunAll]
> Increase max length of index name
> -
>
> Key: IGNITE-5962
> URL: https://issues.apache.org/jira/browse/IGNITE-5962
> Project: Ignite
> Issue Type: Improvement
> Components: general, sql
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length
> was reduced from 768 to 256 bytes. If we need to support longer names, we
> need to change format of metastore data pages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791554#comment-16791554 ] Vladimir Ozerov commented on IGNITE-5962: - [~pkouznet], what TC bot says about test run? > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789801#comment-16789801 ] Pavel Kuznetsov commented on IGNITE-5962: - [~vozerov] Could you please take a look at the patch? > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789641#comment-16789641 ] Pavel Kuznetsov commented on IGNITE-5962: - runAll rerun : https://ci.ignite.apache.org/viewQueued.html?itemId=3287892 > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786773#comment-16786773
]
Ignite TC Bot commented on IGNITE-5962:
---
{panel:title=- Run :: SQL: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3256952]]
* exe: CancellationTest.TestJavaTask - 0,0% fails in last 582 master runs.
{panel}
[TeamCity *- Run :: SQL*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3256954buildTypeId=IgniteTests24Java8_RunAllSql]
> Increase max length of index name
> -
>
> Key: IGNITE-5962
> URL: https://issues.apache.org/jira/browse/IGNITE-5962
> Project: Ignite
> Issue Type: Improvement
> Components: general, sql
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length
> was reduced from 768 to 256 bytes. If we need to support longer names, we
> need to change format of metastore data pages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786681#comment-16786681
]
Pavel Kuznetsov commented on IGNITE-5962:
-
Currently {{LongIndexNameTest}} is part of {{IgniteBinaryCacheQueryTestSuite}}
> Increase max length of index name
> -
>
> Key: IGNITE-5962
> URL: https://issues.apache.org/jira/browse/IGNITE-5962
> Project: Ignite
> Issue Type: Improvement
> Components: general, sql
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length
> was reduced from 768 to 256 bytes. If we need to support longer names, we
> need to change format of metastore data pages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[
https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786215#comment-16786215
]
Ignite TC Bot commented on IGNITE-5962:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests 0 TIMEOUT , Out Of Memory Error ,
Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3251268]]
{color:#d04437}SPI{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3251250]]
{color:#d04437}MVCC Cache{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=3251266]]
{color:#d04437}Cache (Restarts) 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3251281]]
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=3251283]]
{color:#d04437}Cache 6{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3251288]]
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=3251284]]
{color:#d04437}MVCC Cache 1{color} [[tests 0 TIMEOUT , Out Of Memory Error ,
Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3251321]]
{color:#d04437}PDS 1{color} [[tests 0 TIMEOUT , Out Of Memory Error , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3251301]]
{color:#d04437}MVCC PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3251331]]
* IgnitePdsMvccTestSuite2: IgnitePdsRebalancingOnNotStableTopologyTest.test -
0,0% fails in last 448 master runs.
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 4 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3251316]]
* ZookeeperDiscoverySpiTestSuite4:
IgniteCachePutRetryTransactionalSelfTest.testGetAndPut - 0,0% fails in last 432
master runs.
* ZookeeperDiscoverySpiTestSuite4:
IgniteCachePutRetryTransactionalSelfTest.testInvoke - 0,0% fails in last 432
master runs.
{color:#d04437}PDS (Indexing){color} [[tests 75 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=3251299]]
* IgnitePdsWithIndexingTestSuite:
IgniteTwoRegionsRebuildIndexTest.testRebuildIndexes - 3,0% fails in last 437
master runs.
* IgnitePdsWithIndexingTestSuite:
IgnitePdsSingleNodeWithIndexingAndGroupPutGetPersistenceSelfTest.testGroupIndexes
- 0,2% fails in last 437 master runs.
* IgnitePdsWithIndexingTestSuite:
IgnitePdsSingleNodeWithIndexingAndGroupPutGetPersistenceSelfTest.testRandomPutGetRemove
- 0,2% fails in last 437 master runs.
* IgnitePdsWithIndexingTestSuite:
IgnitePdsSingleNodeWithIndexingAndGroupPutGetPersistenceSelfTest.testGroupIndexes2
- 0,2% fails in last 437 master runs.
* IgnitePdsWithIndexingTestSuite:
IgnitePdsSingleNodeWithIndexingAndGroupPutGetPersistenceSelfTest.testPutGetRandomUniqueMultipleObjects
- 0,2% fails in last 437 master runs.
* IgnitePdsWithIndexingTestSuite:
IgnitePdsSingleNodeWithIndexingAndGroupPutGetPersistenceSelfTest.testGradualRandomPutAllRemoveAll
- 0,2% fails in last 437 master runs.
* IgnitePdsWithIndexingTestSuite:
IgnitePdsSingleNodeWithIndexingAndGroupPutGetPersistenceSelfTest.testPutGetRandomNonUniqueMultipleObjects
- 0,2% fails in last 437 master runs.
* IgnitePdsWithIndexingTestSuite:
IgnitePdsSingleNodeWithIndexingAndGroupPutGetPersistenceSelfTest.testPutGetRemoveMultipleForward
- 0,2% fails in last 437 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testPutGetRemoveMultipleBackward - 0,2%
fails in last 438 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testRandomPut - 0,2% fails in last 438
master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testPutPrimaryUniqueSecondaryDuplicates
- 0,2% fails in last 438 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testPutGetMultipleObjects - 0,2% fails
in last 438 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testPutGetSimple - 0,2% fails in last
438 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testOverwriteNormalSizeAfterSmallerSize
- 0,2% fails in last 438 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testPutDoesNotTriggerRead - 0,2% fails
in last 438 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testRandomRemove - 0,2% fails in last
438 master runs.
* IgnitePdsWithIndexingTestSuite:
IgniteDbMultiNodeWithIndexingPutGetTest.testSizeClear - 0,2% fails in last 438
master runs.
* IgnitePdsWithIndexingTestSuite:
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781732#comment-16781732 ] Pavel Kuznetsov commented on IGNITE-5962: - Ok, I've commited another approach: 1) Both tree name and segmentName are now generated directly in the H2TreeIndex and no masking is performed in IndexingStorageImpl 2) Index name is validated by creating name of segment with biggestId. Then this name length in utf-8 is validated. > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780982#comment-16780982 ] Pavel Kuznetsov commented on IGNITE-5962: - In short, I calculate max number of possible added characters during name masking. It allows us to say that particular index name will be ok after masking, even in worst case: we have cache group, type and segment ids are negative ints (11 singns in string representation). In practice limit of not-yet-masked name is 211 utf8 bytes. > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780975#comment-16780975 ] Pavel Kuznetsov commented on IGNITE-5962: - First iteration fix is done, [~vozerov] would you please take a look at fix in general? scheduled RunAll > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769328#comment-16769328 ] Vladimir Ozerov commented on IGNITE-5962: - Real masker name appears here: org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl#allocateCacheIndex > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769327#comment-16769327 ] Vladimir Ozerov commented on IGNITE-5962: - Starting point: org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex#treeName > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767969#comment-16767969 ] Vladimir Ozerov commented on IGNITE-5962: - Instead of increasing index name I'd rather propose to make sure that correct exceptions are thrown. We need to make sure that this is the case for both indexes created on startup, and indexes created on dynamic table or index create commands. > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
