lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Avlesh Singh <avl...@gmail.com>
Subject Re: Retrieving the boost factor using Solrj CommonsHttpSolrServer
Date Tue, 11 Aug 2009 11:50:20 GMT
>
> The boost factor is available in the SolrInputDocument, but not in the
> SolrDocument returned by the SolrServer 'query' method
>
Yes, you are right. There seems to be an inconsistency.

And there is no relationship between the SolrInputDocument and the
> SolrDocument (... which in itself is pretty confusing).
>
I definitely agree with you.

Actually, I always had this question for Yonik (the SolrDocument class has
your name, Yonik) - One should always use SolrInputDocument (and not
SolrDocument) for indexing, right? Why do we have setField, addField and
removeFields as public methods in the SolrDocument class?

Cheers
Avlesh

On Tue, Aug 11, 2009 at 10:29 AM, Villemos, Gert
<gert.villemos@logica.com>wrote:

> I'm using the solrj CommonsHttpSolrServer to retrieve documents from the
> index for update. I therefore also need to retrieve the boost factor as else
> each resubmission would reset the boost factor. I just cant figure out how
> to retrieve the boost factor.
>
> The boost factor is available in the SolrInputDocument, but not in the
> SolrDocument returned by the SolrServer 'query' method. And there is no
> relationship between the SolrInputDocument and the SolrDocument (... which
> in itself is pretty confusing).
>
> How can I get the boost factor? Do I have to use 'request' method and parse
> the result myself?
>
> Cheers,
> Gert.
>
>
>
>
> Please help Logica to respect the environment by not printing this email  /
> Pour contribuer comme Logica au respect de l'environnement, merci de ne pas
> imprimer ce mail /  Bitte drucken Sie diese Nachricht nicht aus und helfen
> Sie so Logica dabei, die Umwelt zu sch├╝tzen /  Por favor ajude a Logica a
> respeitar o ambiente nao imprimindo este correio electronico.
>
>
>
> This e-mail and any attachment is for authorised use by the intended
> recipient(s) only. It may contain proprietary material, confidential
> information and/or be subject to legal privilege. It should not be copied,
> disclosed to, retained or used by, any other party. If you are not an
> intended recipient then please promptly delete this e-mail and any
> attachment and all copies and inform the sender. Thank you.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message