You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/11/29 17:23:12 UTC
[jira] [Resolved] (OAK-2277) Field for analyzed field should use
different name
[ https://issues.apache.org/jira/browse/OAK-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved OAK-2277.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.2)
1.1.3
1.0.9
For a property name _foo_
* Non analyzed property value would be stored directly against propertyName i.e. _foo_
* Analyzed value would be stored against _full:foo_
> Field for analyzed field should use different name
> --------------------------------------------------
>
> Key: OAK-2277
> URL: https://issues.apache.org/jira/browse/OAK-2277
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: oak-lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.0.9, 1.1.3
>
>
> Currently a Lucene field is created with property name in two forms (depending on config)
> * Non analyzed form - Done when {{propertyIndex}} is true for the property being indexed. Used for case like _foo='bar'_
> * Analyzed form - Done when {{analyzed}} is true for property being indexed. Use for cases like _jcr:contains('foo', 'bar')
> As this is a index level changed this should only be done for newly created index.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)