Consider the following use case.
Certain words are extracted from a document and indexed. The exact sentence
containing the word cannot be stored alongside the extracted word because
of the volume at which the documents grow; How can the index and, lets call
it doc servers be separated ?
An optio
and then use it to get
> the original document.
>
> If you're storing the original in a DB, this can be the PK.
> If on a file system the path. etc.
>
> Essentially, since the association is specific to your environment
> you need to handle it explicitly...
>
> Best
.
>
> Now, when _returning_ documents the fields must be read, so
> there is some resource consumption there which you can
> mitigate with lazy field loading. But this is usually just a few docs
> so often isn't a problem.
>
> Best
> Erick
>
> On Thu, Jun 6, 2013 a
I have noticed that when I write a doc with an id that already exists, it
creates a new revision with the only the fields from the second write. I
guess there is a REST API in the latest solr version which updates only
selected fields.
In my opinion, merge should be creating a doc which is a union
@Erick,
Your revelation on SSDs is very valuable.
Do you have any idea on the following ?
Does more processors with less cores or less processors with more cores
i.e. which of 4P2C or 2P4C has best cost per query ?
~ Sourajit
On Fri, Jun 7, 2013 at 4:45 PM, Erick Erickson wrote:
> Thanks for t
Hopefully I will be able to post results shortly on 2P4C performance.
~ Sourajit
On Mon, Jun 10, 2013 at 2:20 AM, Toke Eskildsen wrote:
> Sourajit Basak [sourajit.ba...@gmail.com]:
> > Does more processors with less cores or less processors with more cores
> > i.e. which of 4
When we have a user query like keyword1 OR keyword2, we can find the count
of each keyword using the following params.
q= keyword1 OR keyword2
facet.query=keyword1
facet.query=keyword2
facet=true
How do we do a date range facet that will return results for each keyword
faceted by date range ?
> facet.range=date_field_name
> ...
> facet=true
>
> q= keyword2
> facet.range=date_field_name
> ...
> facet=true
>
> Where the "..." means fill in the additional facet.range.xxx parameters
> (start, end, gap, etc.)
>
> -- Jack Krupansky
>
> -Origi
Is there a way to write this query using pivots. Will try out and post here.
Appreciate if someone points to a way.
On Sun, Jun 23, 2013 at 7:53 PM, Sourajit Basak wrote:
> Thats exactly how we are doing now. However, we need to offer the search
> over slow networks, hence was wonder
ate_field
>
> (See the example in the book! Or on the wiki.)
>
>
> -- Jack Krupansky
>
> -Original Message- From: Sourajit Basak
> Sent: Sunday, June 23, 2013 10:29 AM
> To: solr-user@lucene.apache.org
> Subject: Re: edismax: date range facet with queries cont
10 matches
Mail list logo
