You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2018/02/01 22:52:51 UTC
[jira] [Closed] (GEODE-3953) Lucene create index can fail due to
comparison of fieldnames as an array
[ https://issues.apache.org/jira/browse/GEODE-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapnil Bawaskar closed GEODE-3953.
-----------------------------------
> Lucene create index can fail due to comparison of fieldnames as an array
> ------------------------------------------------------------------------
>
> Key: GEODE-3953
> URL: https://issues.apache.org/jira/browse/GEODE-3953
> Project: Geode
> Issue Type: Bug
> Components: lucene
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Shelley Lynn Hughes-Godfrey
> Assignee: Shelley Lynn Hughes-Godfrey
> Priority: Trivial
> Fix For: 1.4.0
>
>
> Note that Arrays.equals() fails if the entries are in a different order ... but order here is not significant and we should not fail the profile comparison
> {noformat}
> // Verify fields are the same
> if (!Arrays.equals(remoteProfile.getFieldNames(), getFieldNames())) {
> return LocalizedStrings.LuceneService_CANNOT_CREATE_INDEX_0_ON_REGION_1_WITH_FIELDS_2_BECAUSE_ANOTHER_MEMBER_DEFINES_THE_SAME_INDEX_WITH_FIELDS_3
> .toString(getIndexName(), regionPath, Arrays.toString(getFieldNames()),
> Arrays.toString(remoteProfile.getFieldNames()));
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)