geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-3953) Lucene create index can fail due to comparison of fieldnames as an array
Date Fri, 03 Nov 2017 23:26:01 GMT


ASF subversion and git services commented on GEODE-3953:

Commit c4697445a400d5bc2d7b490c475471e2f3226a93 in geode's branch refs/heads/feature/GEODE-3953
from [~lhughesgodfrey]
[;h=c469744 ]

GEODE-3953: Incorrect use of .equals() for comparison of fieldname arrays
GEODE-3954: Misleading Exception message with mismatched fieldAnalyzers

- corrected equals comparisons of fieldname arrays
- corrected Exception message for mismatched fieldAnalyzers to refer to field analyzers (vs.
fieldnames) when remote and local fieldAnalyzers are different sizes
- corrected Exception message to display fieldAnalyzers vs. fieldnames when remote and local
fieldAnalyzer maps are different sizes

> Lucene create index can fail due to comparison of fieldnames as an array
> ------------------------------------------------------------------------
>                 Key: GEODE-3953
>                 URL:
>             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
> 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())) {
>           .toString(getIndexName(), regionPath, Arrays.toString(getFieldNames()),
>               Arrays.toString(remoteProfile.getFieldNames()));
>     }
> {noformat}

This message was sent by Atlassian JIRA

View raw message