lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Jelsma <markus.jel...@openindex.io>
Subject RE: Per-document and per-query analysis
Date Fri, 24 Jul 2015 12:44:55 GMT
Hello Alessandro, i have thought about that, but in this case we do not want more fields, just
perform some additional normalization filters based on some parameter. We need this type of
index to be very low latency, and we have many varieties. We know from experience that hundreds
of fields adds considerable overhead, visible in the prepare section when debugging.

Markus
 
-----Original message-----
> From:Alessandro Benedetti <benedetti.alex85@gmail.com>
> Sent: Thursday 23rd July 2015 18:08
> To: solr-user@lucene.apache.org
> Subject: Re: Per-document and per-query analysis
> 
> markus,
> the first idea that come to my mind is this :
> 
> 1) you configure your schema, creating your field types, and if necessary
> fields associated
> 2) you build an UpdateRequestProcessor that do a conditional check per
> document, and create the proper fields starting from one input field .
> 
> In this way you will have the possibility of automatically analyse
> indexing/query time differently each field.
> As a cons you will have more fields, and not only one, each field will
> reflect your requirements in terms of analysis.1) you configure your schema, creating
your field types, and if necessary
fields associated
2) you build an UpdateRequestProcessor that do a conditional check per
document, and create the proper fields starting from one input field .

> 
> Do you think this solution can satisfy you ?
> Please share a feedback and we can discuss better the requirements.
> 
> Cheers
> 
> 2015-07-23 17:03 GMT+01:00 Markus Jelsma <markus.jelsma@openindex.io>:
> 
> > Hello - the title says it all. When indexing a document, we need to run
> > one or more additional filters depending on the value of a specific field.
> > Likewise, we need to run that same filter over the already analyzed tokens
> > when querying. This is not going to work if i extend TextField, at all. And
> > i am not sure about QParsers as well because it should be QParser agnostic.
> >
> > I am in need of some hints about which parts of the codebase i should
> > extend or replace, if possible at all. For the record, in this case we do
> > not want to create additional fields.
> >
> > Many thanks,
> > Markus
> >
> 
> 
> 
> -- 
> --------------------------
> 
> Benedetti Alessandro
> Visiting card - http://about.me/alessandro_benedetti
> Blog - http://alexbenedetti.blogspot.co.uk
> 
> "Tyger, tyger burning bright
> In the forests of the night,
> What immortal hand or eye
> Could frame thy fearful symmetry?"
> 
> William Blake - Songs of Experience -1794 England
> 

Mime
View raw message