thanks Miles, yes... i missed that the queryParser could transform a query..
but i don't like very much my idea: the integration is too high level.
it would be great if a low level of integration will be possible
because of the scorer.
In fact the calcul of score will certainly more complex. Act
On Wed, 2005-03-09 at 18:29 +0100, Nicolas Maisonneuve wrote:
> I would like use a index with structured search field.
>
> - flat index (lucene type)
> searchfield1
> searchfield2
> searchffield3
> ...
> -structured index
> search1
>search2
> search4
>search3
> search5
>
> to
oups ..
2- According to the table , a new Query is created with just non zero
boost search field search2:coco^search2_boost
search4:coco^search4_boost
On Wed, 9 Mar 2005 18:53:41 +0100, Nicolas Maisonneuve
<[EMAIL PROTECTED]> wrote:
> hmm a idea would be to create dynamically a boost table (f
hmm a idea would be to create dynamically a boost table (field,
boostvalue) in a extended version of a TermQuery depending on the
field:
ex: StructuredTermQuery ("search2", "coco")
1-> Update a boost table according to:
* the virtual structure :
> -structured index
> search1
>search2
>
hy everybody,
I would like use a index with structured search field.
- flat index (lucene type)
searchfield1
searchfield2
searchffield3
...
-structured index
search1
search2
search4
search3
search5
to allow simple extensions of some search features:
- the query TermQuery(
