Aq
On 10/7/09, clico wrote:
>
> Hello
> I have a pb trying to retrieve a tree with facet use
>
> I 've got a field location_field
> Each doc in my index has a location_field
>
> Location field can be
> continent/country/city
>
>
> I have 2 queries:
>
> http://server/solr//select?fq=(location_
>
> http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
>
> -Jay
> http://www.lucidimagination.com
>
>
> On Wed, Sep 9, 2009 at 3:35 PM, Todd Benge wrote:
>
> > We're using the StandardAnalyzer but I'm fairly certain that
'm guessing that your words are being
> split up during analysis, which is why you aren't seeing whitespace. If you
> want to keep the whitespace, you will need to use the String field type or
> possibly the Keyword Analyzer.
>
> -Grant
>
>
> On Sep 9, 2009, at
It's set as Field.Store.YES, Field.Index.ANALYZED.
On Wed, Sep 9, 2009 at 8:15 AM, Grant Ingersoll wrote:
> How are you tokenizing/analyzing the field you are accessing?
>
>
> On Sep 9, 2009, at 8:49 AM, Todd Benge wrote:
>
> Hi Rekha,
>>
>> Here
Hi Rekha,
Here's teh link to the TermsComponent info:
http://wiki.apache.org/solr/TermsComponent
and another link Matt Weber did on autocompletion:
http://www.mattweber.org/2009/05/02/solr-autosuggest-with-termscomponent-and-jquery/
We had to upgrade to the latest nightly to get the TermsCompo
g I noticed is we're indexing with Lucene 2.4 and Solr is using 2.9
rc2 in the nightly build. Any chance that could be causing the problem?
Thanks,
Todd
On Sat, Sep 5, 2009 at 11:50 AM, Todd Benge wrote:
> Thanks - I'll give it a try
>
> On 9/5/09, Yonik Seeley wrote:
> &g
Thanks - I'll give it a try
On 9/5/09, Yonik Seeley wrote:
> On Fri, Sep 4, 2009 at 5:46 PM, Todd Benge wrote:
>> I was looking at TermsComponent in Solr 1.4 as a way of building a
>> autocomplete function. I have a prototype working but noticed that terms
>> that ha
Hi,
I was looking at TermsComponent in Solr 1.4 as a way of building a
autocomplete function. I have a prototype working but noticed that terms
that have whitespace in them when indexed are absent the whitespace when
returned from the TermsComponent.
Any ideas on why that may be happening? Am I
Our company has a large search deployment serving > 50 M search hits / per
day.
We've been leveraging Lucene for several years and have recently deployed
Solr for the distributed search feature. We were hitting scaling limits
with lucene due to our index size.
I did an evaluation of Sphinx and f
Hi,
We're in the process of converting a Lucene deployment of 500 M documents /
60 G deployment into a Solr Distributed search deployment.
The primary reason for the change is instability in the Lucene deployment
due to memory constraints. The existing infrastructure is deployed on 48
machines w
lts to be sorted &
scored separately.
Any suggestions are helpful. I'm sure we can find a solution to the problem
but are just trying to find the best architectural solution.
Todd
On Mon, Mar 30, 2009 at 10:53 PM, Yonik Seeley
wrote:
> On Mon, Mar 30, 2009 at 7:07 PM, Todd Benge wr
Hi,
We're in the early stages of converting a large scale lucene deployment to
Solr. The primary reason is to take advantage of the distributed search
capabilities.
We have multiple sets of indices that serve different types of documents.
In our existing deployment, we use MultiSearcher and cust
12 matches
Mail list logo