incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <>
Subject [jira] [Commented] (BLUR-44) Update BlurAnalyzer to use the Blur Thrift Analyzer object.
Date Sat, 08 Dec 2012 02:41:21 GMT


Aaron McCurry commented on BLUR-44:

1) Yes
2) I'm not sure, I think that there may be a managing object that will handle the IndexableFieldFactory
and if the field is not handled by that manager object then it will fall on the BlurAnalyzer
to pick either the defined analyzer or the default analyzer.

If you take a look at the public static IndexableField toLucene(Field field) throws IOException;
method in the ThriftLuceneConversion class that is where the default fields are converted.
 I don't think that is the best place for that code.  So perhaps that code should be moved
in the this field manager class.  There should probably one instance of the managing class
per table.

3) Only the class definitions that define analyzer should be in the this map.  At this point
I would say use your best judgement on how to structure things internally.
4) Probably not a bad idea, this will be of use once we get to implementing the LiveSchema.
5) We are only going to store the main fields and only index the sub fields, so yes.

Let me know if any of this doesn't make sense.  Thanks!

> Update BlurAnalyzer to use the Blur Thrift Analyzer object.
> -----------------------------------------------------------
>                 Key: BLUR-44
>                 URL:
>             Project: Apache Blur
>          Issue Type: Improvement
>    Affects Versions: 0.2.0
>         Environment: 0.2-dev-removing-old-thrift branch
>            Reporter: Aaron McCurry
>             Fix For: 0.2.0
> The BlurAnalyzer constructor that takes a org.apache.blur.thrift.generated.Analyzer currently
does nothing.  Obviously this needs to be implemented, I have added javadocs to the Blur thrift
API that describes the expected behavior.

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:

View raw message