For solr 1.4
Is basically the same but IndexSchema (org.apache.solr.schema.IndexSchema)
needs to be updated to include the function
getFieldTypeByName(String fieldTypeName) which is already in sorl1.5
/**
* Given the name of a {...@link org.apache.solr.schema.FieldType} (not to be
confused
Ok
For solr 1.5
after looking around, analyzing the answers in this forum, and browsing the
code, I think that I could manage it. I had to write a few lines of code,
the problem was to find which ones !!!
So i did a new class, which is a subclass of CompressableField that includes
a new parameter
Otis,
I've been thinking on it, and trying to figure out the different solutions
- Try to solve it doing a bridge between solr and clustering.
- Try to solve it before/during indexing
The second option, of course is better for performance, but how to do it??
I think a good option may be to crea
Hi Joan,
You could use the FieldAnalysisRequestHandler:
http://www.search-lucene.com/?q=FieldAnalysisRequestHandler
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Hadoop ecosystem search :: http://search-hadoop.com/
- Original Message
> From: JCodina
> To: solr-
Thanks,
It can be useful as a workarrond,
but I get a vector not a "result" that I may use wherever I could used the
stored text.
I'm thinking in clustering.
Ahmet Arslan wrote:
>
>> In an stored field, the content stored is the raw input
>> text.
>> But when the analyzers perform some cleani
> In an stored field, the content stored is the raw input
> text.
> But when the analyzers perform some cleaning or interesting
> transformation
> of the text, then it could be interesting to store the text
> after the
> tokenizer/Filter chain
> there is a way to do this? To be able to get back the
