[
https://issues.apache.org/jira/browse/BLUR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799915#comment-13799915
]
Aaron McCurry commented on BLUR-280:
------------------------------------
I'm thinking that on the indexing side if the family is null in the record we
use a default value of "_default_". This should be done in the
BaseFieldManager.getFields method. That's pretty much it for the indexing side.
On the query side we need to resolve the field name to the correct family. So
I think in the BlurQueryParser we need to add some functionality to the
following methods.
newFuzzyQuery
newMultiPhraseQuery
newPhraseQuery
newPrefixQuery
newRangeQuery
newTermQuery
newWildcardQuery
We should resolve the provided field (which is usually in a Term object) to the
correct field. So with that we should add an abstract method on the
FieldManager called resolveField. Then implement it in the BaseFieldManager,
and if the field name matches an existing field then just return it. If not
then try to find the best family to use, meaning one with a column name that
matches the single provided field. If it matches nothing, just use the field
as-is. Also make sure to handle special cases like rowid, recordid, family,
and prime (all have constants in BlurConstants).
Let me know if you have more questions.
Thanks!
Aaron
> Make the family field optional on the Record object.
> ----------------------------------------------------
>
> Key: BLUR-280
> URL: https://issues.apache.org/jira/browse/BLUR-280
> Project: Apache Blur
> Issue Type: New Feature
> Components: Blur
> Affects Versions: 0.3.0
> Reporter: Aaron McCurry
> Fix For: 0.3.0
>
>
> Allow the family field in the Record object to be null (optionally set).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
