[
https://issues.apache.org/jira/browse/OAK-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110092#comment-15110092
]
Chetan Mehrotra commented on OAK-3825:
--------------------------------------
To confirm the intended definition would like
{noformat}
+ app:Asset
+ properties (nt:unstructured)
+ nodeName
- propertyIndex = true
- analyzed = true
- useInSuggest = true
- name = ":nodeName"
{noformat}
Then couple of points
* Using existing constant from {{FieldNames}} - {{FieldNames}} constant are
meant to be for naming field in lucene documents. So would be better to define
this constant (yes duplicate) in {{LuceneIndexConstants}} where all constants
related to Lucene index config are defined
* Minor and should not affect much- If this node has {{nodeScopeIndex}} set to
true then node name would be indexed fine. That is perfectly fine though.
> Including Resource name to suggestions
> --------------------------------------
>
> Key: OAK-3825
> URL: https://issues.apache.org/jira/browse/OAK-3825
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Ankit Agarwal
> Assignee: Vikas Saurabh
> Fix For: 1.4
>
> Attachments: OAK-3825.patch
>
>
> Currently it is possible to include properties of a resource into
> suggestions.
> There should be a way so that its possible to include resource name itself
> into suggestions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
