[
https://issues.apache.org/jira/browse/BLUR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673282#comment-13673282
]
Aaron McCurry commented on BLUR-113:
------------------------------------
We could it wouldn't hurt, but the ID_TYPE in the TransactionRecorder tells the
IndexWriter to not analyzer the field at all. So we could in fact remove all
the references to the KeywordAnalyzer in the BlurAnalyzer. But perhaps a
better option we be to replace the KeywordAnalyzer in the BlurAnalyzer with a
new Analyzer that throws an exception when it's used. That way no one can add
a field from one of the special fields (ROWID, PRIME_DOC, RECORDID, and FAMILY)
to an index and have it be analyzed, which would be wrong. In other words the
new Analyzer would provide a validation for those special fields.
> Index the family as a special field
> -----------------------------------
>
> Key: BLUR-113
> URL: https://issues.apache.org/jira/browse/BLUR-113
> Project: Apache Blur
> Issue Type: Improvement
> Affects Versions: 0.1.5
> Reporter: Aaron McCurry
> Fix For: 0.1.5
>
>
> I've come across several situations where indexing the family name in each
> record would have made certain queries much easier. So we should add it as a
> default indexed filed of type stringfield, like rowid and recordid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
