incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-280) Make the family field optional on the Record object.
Date Fri, 18 Oct 2013 01:12:42 GMT

    [ https://issues.apache.org/jira/browse/BLUR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798689#comment-13798689
] 

Aaron McCurry commented on BLUR-280:
------------------------------------

#1 and #4 are going to be where the focus should be.  Basically the blur-query project is
the one to focus on.

I would start by adding to the existing unit tests that take in the family name and pass null
to them and see what breaks.

#5 is actually handled in the BaseFieldManager getFields call.

If I have time this weekend I will go through and create sub tasks, but for now I would focus
on BaseFieldManager and SuperParser.  I have a feeling that the code changes will likely not
be major but I could be wrong.

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)

Mime
View raw message