[
https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428628#comment-15428628
]
ASF subversion and git services commented on GEODE-11:
------------------------------------------------------
Commit 1ab59ffb20346a957cfcbc8324376f772f14da96 in incubator-geode's branch
refs/heads/develop from [~adharmakkan]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=1ab59ff ]
GEODE-11: Fixing bug that arises while using user defined analyzer in gfsh.
This closes #233
When we use an user defined analyzer class in gfsh, the cluster hangs because
the create region message that is sent has a LuceneIndexCreationProfile has a
user defined analyzer class. Fixed this by storing only the class name in
LuceneIndexCreationProfile.
Signed-off-by: Gester Zhou <gz...@pivotal.io>
GEODE-11: StandardAnalyzer is used when analyzer option is null
Using the string "null" in the analyzer option for create lucene index command
will now set the field analyzer to be StandardAnalyzer.
GEODE-11: Added CliAvailabilityIndicator to lucene gfsh commands
The lucene gfsh commands were available offline. Changed this behavior by
adding CliAvailabilityIndicator.
GEODE-11:Fix for "Comparison method violates general contract"
The search results are sorted by score and the compareTo method caused the
"Comparison method violates general contract" error when it returned multiple
results with same score.
Signed-off-by: Gester Zhou <gz...@pivotal.io>
GEODE 11: Added a check to make sure StandardAnalyzer and NULL were considered
the same.
LuceneIndexCreationProfile checks to makes sure the newly created index's field
analyzers are consistent with existing indexes' field analyzers. However, when
a field's analyzer is null and a new index is created with StandardAnalyzer on
the same field, it failed. Fixed this issue by modifying the conditional
checks. Added dunit tests to verify.
Signed-off-by: Gester Zhou <gz...@pivotal.io>
GEODE 11: Added a check to make sure StandardAnalyzer and NULL were considered
the same.
LuceneIndexCreationProfile checks to makes sure the newly created index's field
analyzers are consistent with existing indexes' field analyzers. However, when
a field's analyzer is null and a new index is created with StandardAnalyzer on
the same field, it failed. Fixed this issue by modifying the conditional
checks. Added dunit tests to verify.
Signed-off-by: Gester Zhou <gz...@pivotal.io>
GEODE 11: Clean up of comparison code in LuceneIndexCreationProfile
Since the null in fieldAnalyzers are converted to Standard analyzer, a few
checks become irrelevant. Modified the code and relevant tests.
Signed-off-by: Gester Zhou <gz...@pivotal.io>
fix merge issue
> Lucene Integration
> ------------------
>
> Key: GEODE-11
> URL: https://issues.apache.org/jira/browse/GEODE-11
> Project: Geode
> Issue Type: New Feature
> Components: docs, querying
> Reporter: Dan Smith
> Assignee: xiaojian zhou
> Labels: experimental
>
> This is a feature that has been under development for GemFire but was not
> part of the initial drop of code for geode.
> Allow Lucene indexes to be stored in Geode regions allowing users to do text
> searches on data stored in Geode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
