Thanks Tomas, your suggestion worked!!
true
true
/terms
terms
On Thu, Nov 22, 2012 at 11:59 AM, Tomás Fernández Löbbe <
tomasflo...@gmail.com> wrote:
> Hi Federico, it should work. Make sure you set the "shards.qt" parameter
> too (in your case,
Hi Federico, it should work. Make sure you set the "shards.qt" parameter
too (in your case, it should be shards.qt=/terms)
On Thu, Nov 22, 2012 at 6:51 AM, Federico Méndez wrote:
> Anyone knows if the TermsComponent supports distributed search trough a
> SolrCloud installation? I have a SolrClou
Yes, per-doc. I mentioned TermsComponent but meant TermVectorComponent,
where we get back all the terms in the doc. Just wondering if there was a
way to only get back the terms that matched the query.
Thanks EE,
-Jay
On Sat, Feb 25, 2012 at 2:54 PM, Erick Erickson wrote:
> Jay:
>
> I've seen th
I think you have to walk the term positions and offsets, look in the
stored field, and find the terms that matched. Which is exactly what
highlighting does. And this will only find the actual terms in the
text, no synonyms. So if you search for Sempranillo and find
Sempranillo in some wines and Tem
Jay:
I've seen the this question go 'round before, but don't remember
a satisfactory solution. Are you talking on a per-document basis
here? If so, I vaguely remember it being possible to do something
with highlighting, just counting the tags returned after highlighting.
Best
Erick
On Fri, Feb 2
I'd use the suggester:
http://wiki.apache.org/solr/Suggester
The suggester can give a collation. The TermsComponent can't do that.
The suggester builds on top of the spellchecking infrastructure, so
should be easy to use if you're familiar with that.
Martijn
On 10 September 2011 08:37, Manish Ba
Which is preferable? using TermsComponent or Facets for autosuggest?
On Fri, Sep 9, 2011 at 10:33 PM, Chris Hostetter
wrote:
>
> : http://wiki.apache.org/solr/TermsComponent states that TermsComponent
> will
> : return frequencies from deleted documents too.
> :
> : Is there anyway to omit the de
: http://wiki.apache.org/solr/TermsComponent states that TermsComponent will
: return frequencies from deleted documents too.
:
: Is there anyway to omit the deleted documents to get the frequencies.
not really -- until a deleted document is expunged from segment merging,
they are still include
Hi antonio,
can you explain a bit more, how exactly have you implemented the
autocomplete, is it with the terms component only? Does autocomplete operate
on letter or word level?
What does user type in for which the server returns both "Rome" and "Near
Rome"?
-- Dmitry
On Thu, May 26, 2011 at 5:
Hi Dmitry Kan, thanks for your anwser.
This is an idea, but i think that will be not so performing. Because if the
terms are 1000, i must reorder 1000 terms by own length, and i think the
time will be high for make autocomplete.
Don't you think?
--
View this message in context:
http://lucene.472
Hi antonio,
Can you sort yourself on client side?
Are you trying to sort the terms with the same count in reverse order of
their lengths?
On Tue, May 24, 2011 at 8:18 PM, antonio wrote:
> Hi, i use solr 3.1.
> I implemented my autocomplete with TermsComponent. I'm finding, if there
> is,
> a w
Help me please...
--
View this message in context:
http://lucene.472066.n3.nabble.com/Termscomponent-sort-question-tp2980683p2986185.html
Sent from the Solr - User mailing list archive at Nabble.com.
No one has an idea?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Termscomponent-sort-question-tp2980683p2983776.html
Sent from the Solr - User mailing list archive at Nabble.com.
> Does anyone know how to apply some analyzers over a prefix
> query?
Lucene has an special QueryParser for this.
http://lucene.apache.org/java/3_0_2/api/contrib-misc/org/apache/lucene/queryParser/analyzing/AnalyzingQueryParser.html
Someone provided a patch to use it in solr. It was an attachmen
I don't believe you can. If you just need query-time transformation,
can't you just do it in your client app? If you need index-time
transformation... well, you can do that, but it's up to your schema.xml
and will of course apply to the field as a whole, not just for
termscomponent queries, be
To build your autocompletion, you can use the NGramFilterFactory. If you type
cat It will match "subcategory" and "the best category".
If you change your mind and you don't want anymore to match subcategory, you
can use the EdgeNGramFilterFactory.
--
View this message in context:
http://lucene.
Hi Saïd,
I think your problem is the field's type: String. You have to use a
TextField and apply tokenizers that will find "subcategory" if you put
in "cat". (Not sure which filter does that, though. I wouldn't think
that the PorterStemmer cuts off prefix syllables of that kind?)
If, however, you
You can use the spelling dictionary feature for auto-complete. This is
actually more useful than facet.prefix because normal people are not
perfect spellers. (It would be even more useful based on phonemes, but
I haven't figured out how to do that yet.)
On Tue, Jan 19, 2010 at 6:28 PM, Erik Hatche
On 20.01.2010, at 15:50, Lukas Kahwe Smith wrote:
>
> On 19.01.2010, at 22:52, Lukas Kahwe Smith wrote:
>
I also want to match multiple fields at once.
>>>
>>> Can you give an example?
>>
>>
>> I enter "Kreuz" but this could either be part of a persons name or of a
>> street name, whic
On 19.01.2010, at 22:52, Lukas Kahwe Smith wrote:
>>> I also want to match multiple fields at once.
>>
>> Can you give an example?
>
>
> I enter "Kreuz" but this could either be part of a persons name or of a
> street name, which are separate fields in my index mainly because they
> analyzed
On Jan 19, 2010, at 3:55 PM, Otis Gospodnetic wrote:
a search "quality" meter. As in indicate the total number of
matches (doesnt
need to be accurate, just a ballpark figure especially if there are
a lot of
matches)
As in, you want each suggestion include the number of documents it
would
You may be able to use faceting for this.
Use facet.method=enum - it will be more efficient for this specific use.
The main problem is that you can't specify a start term for faceting
though (you can only use numeric offset / limit into the list).
To do more will require either adding some terms
On 19.01.2010, at 21:55, Otis Gospodnetic wrote:
> Hi Lukas,
>
>
> - Original Message
>
>> From: Lukas Kahwe Smith
>
>> I want to use TermsComponent for both auto complete suggestions but also
>> showing
>
> Is TermsComponent really that good for AutoComplete?
> Have a look at ht
Hi Lukas,
- Original Message
> From: Lukas Kahwe Smith
> I want to use TermsComponent for both auto complete suggestions but also
> showing
Is TermsComponent really that good for AutoComplete?
Have a look at http://www.sematext.com/demo/ac/index.html - doesn't use TC.
> a search
Thanks for pointing that out. The TermsComponent prefix query is running
much faster than the facet prefix query. I guess there is yet another
reason to optimize the index.
Bill
On Tue, Nov 3, 2009 at 5:09 PM, Koji Sekiguchi wrote:
> Bill Au wrote:
>
>> Should the results of the TermsComponen
Bill Au wrote:
Should the results of the TermsComponent change after documents have been
removed from the index? I am thinking about using the prefix of
TermsComponent to implement auto-suggest. But I noticed that the prefix
counts in TermsComponent don't change after documents have been delete
Thanks Jay. What's a good way of extracting the original text from here?
On Thu, Oct 8, 2009 at 1:03 AM, Jay Hill wrote:
> Something like this, building on each character typed:
>
> &facet=on&facet.field=tc_query&facet.prefix=be&facet.mincount=1
>
> -Jay
> http://www.lucidimagination.com
>
>
> O
Something like this, building on each character typed:
&facet=on&facet.field=tc_query&facet.prefix=be&facet.mincount=1
-Jay
http://www.lucidimagination.com
On Tue, Oct 6, 2009 at 5:43 PM, R. Tan wrote:
> Nice. In comparison, how do you do it with faceting?
>
> > "Two other approaches are to u
Nice. In comparison, how do you do it with faceting?
> "Two other approaches are to use either the TermsComponent (new in Solr
> 1.4) or faceting."
On Wed, Oct 7, 2009 at 1:51 AM, Jay Hill wrote:
> Have a look at a blog I posted on how to use EdgeNGrams to build an
> auto-suggest tool:
>
> ht
Have a look at a blog I posted on how to use EdgeNGrams to build an
auto-suggest tool:
http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
You could easily add filter queries to this approach. Ffor example, the
query used in the blog could add filter
Thanks for the pointer. Definitely appreciate the help.
Todd
On Thu, Sep 10, 2009 at 11:10 AM, Jay Hill wrote:
> If you need an alternative to using the TermsComponent for auto-suggest,
> have a look at this blog on using EdgeNGrams instead of the TermsComponent.
>
>
> http://www.lucidimaginat
If you need an alternative to using the TermsComponent for auto-suggest,
have a look at this blog on using EdgeNGrams instead of the TermsComponent.
http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
-Jay
http://www.lucidimagination.com
On Wed, S
We're using the StandardAnalyzer but I'm fairly certain that's not the
issue.
In fact, I there doesn't appear to be any issue with Lucene or Solr. There
are many instances of data in which users have removed the whitespace so
they have a high frequency which means they bubble to the top of the so
And what Analyzer are you using? I'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 11:06 AM
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's teh link to the TermsComponent info:
>>
>> h
How are you tokenizing/analyzing the field you are accessing?
On Sep 9, 2009, at 8:49 AM, Todd Benge wrote:
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
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
Hi,
I tried setting the terms.raw param to true but didn't see any difference.
I did a little more digging and it appears the text in the TermEnum is
missing the whitespace inside Lucene so I'm not sure if it's because of the
way we're indexing the value or not.
One thing I noticed is we're index
Hi,
I have a requirement on Autocompletion search , iam using solr 1.4.
Could you please tell me how you worked on that Terms component using solr
1.4,
i could'nt find terms component in solr 1.4 which i have downloaded,is there
anyother configuration should be done.
Do you have code for autoco
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 have whitespace in them when in
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 have whitespace in them when indexed are absent the whitespace when
> returned from the TermsComp
Hi Todd,
I have not tried this yet.
But try setting the terms.raw parameter to true.
Maybe that will include the whitespace that is missing from the response.
On Fri, Sep 4, 2009 at 5:46 PM, Todd Benge wrote:
> Hi,
>
> I was looking at TermsComponent in Solr 1.4 as a way of building a
> autoc
: currently the terms component does not support filter queries. However,
: without them the returned count for the terms might differ to the actual
: results the user gets when conducting a search with a suggested word and
: (automatically) applied filter queries.
:
: So, are there any plans to
43 matches
Mail list logo
