Hi Brett,
We, at IndiaMART, have Solr installed behind PHP servers which are
behind Varnish servers.
Yes, you are right exposing Solr URL is not a good idea. A single service
in between would do the trick.
You can try our service at dir.indiamart.com. We have a client-side JS that
handles AJAX r
Thank you so much.
I'll read up on that and try that out.
Regards,
Edwin
On 12 July 2015 at 00:41, Erick Erickson wrote:
> Cool! I've bookmarked it, much more thorough
>
> Erick
>
> On Sat, Jul 11, 2015 at 8:13 AM, Walter Underwood
> wrote:
> > Thanks, this is very helpful.
> >
> > Sugge
Cool! I've bookmarked it, much more thorough
Erick
On Sat, Jul 11, 2015 at 8:13 AM, Walter Underwood wrote:
> Thanks, this is very helpful.
>
> Suggester config is quite under documented. It took me longer than I expected
> to get it working.
>
> wunder
> Walter Underwood
> wun...@wunderwoo
Thanks, this is very helpful.
Suggester config is quite under documented. It took me longer than I expected
to get it working.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
On Jul 10, 2015, at 6:30 PM, Alessandro Benedetti
wrote:
> Hi guys,
> just
Hi guys,
just wrote a blog to integrate Erick's post and to explain in details with
practical examples all the main Lookup implementations :
http://alexbenedetti.blogspot.co.uk/2015/07/solr-you-complete-me.html
I think this can be useful for Edwin to finally fix the config for the
FreeTextSuggest
Thanks, Erick, i didn't have time to go again through the code.
But i will forward this to the Dev list.
Thank you for your time !
Cheers
2015-06-27 16:19 GMT+01:00 Erick Erickson :
> Alessandro:
>
> Going to have to defer to Mike McCandless et.al., they're the
> authorities here. Don't quite kn
Alessandro:
Going to have to defer to Mike McCandless et.al., they're the
authorities here. Don't quite know whether they monitor this list,
consider the dev list?
Best,
Erick
On Fri, Jun 26, 2015 at 4:53 AM, Alessandro Benedetti
wrote:
> Up, Can anyone gently take a look to my considerations r
Up, Can anyone gently take a look to my considerations related the FreeText
Suggester ?
I am curious to have more insight.
Eventually I will deeply analyse the code to understand my errors.
Cheers
2015-06-19 11:53 GMT+01:00 Alessandro Benedetti
:
> Actually the documentation is not clear enough
Can any of our beloved super guru take a look to my mail ?
It could help Edwin as well :)
Cheers
2015-06-19 11:53 GMT+01:00 Alessandro Benedetti
:
> Actually the documentation is not clear enough.
> Let's try to understand this suggester.
>
> *Building*
> This suggester build a FST that it will
Ok sure.
> " ngrams: The max number of tokens out of which singles will be make the
> dictionary. The default value is 2. Increasing this would mean you want
> more than the previous 2 tokens to be taken into consideration when making
> the suggestions. "
I got confused by this, as I could not ge
Actually the documentation is not clear enough.
Let's try to understand this suggester.
*Building*
This suggester build a FST that it will use to provide the autocomplete
feature running prefix searches on it .
The terms it uses to generate the FST are the tokens produced by the
"suggestFreeTextA
Any one find any solution for this probleme ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-suggest-with-adding-accents-tp4150379p4150972.html
Sent from the Solr - User mailing list archive at Nabble.com.
hello,
on the new suggester, when the field is multivalued="true", itsnot working
i need to try the patch "LUCENE-3842" to test auto complete but i dont know
how.
i have Solr-4.7.2 not source code.
can some one help?
Best regards,
Anass BENJELLOUN
--
View this message in context:
http://luce
Perhaps the actual suggester module is a better fit then:
http://blog.mikemccandless.com/2012/09/lucenes-new-analyzing-suggester.html
http://romiawasthy.blogspot.fi/2014/06/configure-solr-suggester.html
Also:
http://jayant7k.blogspot.com/2014/03/an-interesting-suggester-in-solr.html
Regards,
Aha. I don't know if Solr Suggester can do that. Let's see what others
say. I know http://www.sematext.com/products/autocomplete/ could do that.
Otis
--
Performance Monitoring * Log Analytics * Search Analytics
Solr & Elasticsearch Support * http://sematext.com/
On Fri, Aug 1, 2014 at 9:26 AM
hello,
you didnt enderstand well my problem i give you exemple:
the document contain the word "genève".
q="gene" auto suggestion give "geneve"
q="genè" auto suggestion give "genève"
but what i need is q="gene" auto suggestion give "genève" with accent like
correction of word.
i tried to add spel
You need to do the opposite. Make sure accents are NOT removed at index &
query time.
Otis
--
Performance Monitoring * Log Analytics * Search Analytics
Solr & Elasticsearch Support * http://sematext.com/
On Thu, Jul 31, 2014 at 5:49 PM, benjelloun wrote:
> hi,
>
> q="gene" it suggest "geneve
hi,
q="gene" it suggest "geneve"
ASCIIFoldingFilter work like isolate accent
what i need to suggest is "genève"
any idea?
thanks
best reagards
Anass BENJELLOUN
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-suggest-with-adding-accents-tp4150379p4150392.html
Sent f
Hi,
What happens when you add ASCIIFoldingFilter to field type definition of
suggestField?
Ahmet
On Thursday, July 31, 2014 5:49 PM, benjelloun wrote:
Hello,
i'm trying to autosuggest frensh word with accents,
but if the user write q="gene" it will not suggest "genève", it will suggest
"gene
Hello Erick,
So in your opinion what is the solution to use autosuggest with sentece :)
an exemple will be very helpfull,
Thanks,
best regards,
Anass BENJELLOUN
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-Suggest-tp4149004p4149441.html
Sent from the Solr - User ma
No, although there's been some joy with using shingles. Autosuggest
works off of the _indexed tokens_. So the problem is really reducing
the tokenization to something that is multi-word.
Best,
Erick
On Thu, Jul 24, 2014 at 5:11 AM, benjelloun wrote:
> Hello,
>
> Did solr.SuggestComponent work
Sorry, I forgot the link:
[1] - http://wiki.apache.org/solr/SolrRelevancyFAQ
- Mensaje original -
De: "Ing. Jorge Luis Betancourt Gonzalez"
Para: solr-user@lucene.apache.org
Enviados: Martes, 1 de Octubre 2013 13:34:03
Asunto: Re: Auto Suggest - Time decay
For that core
omatically boosted by date.
PS: You could tweak the above formula used in the boost parameter for a more
suitable to your needs.
- Mensaje original -
De: "SolrLover"
Para: solr-user@lucene.apache.org
Enviados: Martes, 1 de Octubre 2013 12:19:51
Asunto: Re: Auto Suggest - Time
I am using a totally separate core for storing the auto suggest keywords.
Would you be able to send me some more details on your implementation?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-Suggest-Time-decay-tp4092965p4092969.html
Sent from the Solr - User mailing
Are you using the suggester component? or a separated core? I've used a
separated core to store suggestions and order this suggestions (queries
performed on the frontend) using a time decay function, and it works great for
me.
Regards,
- Mensaje original -
De: "SolrLover"
Para: solr-u
Seems like this feature is still yet to be implemented..
https://issues.apache.org/jira/browse/SOLR-866
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-Suggest-spell-check-dictionary-replication-to-slave-issue-tp4068562p4068739.html
Sent from the Solr - User mailing li
On Wed, Apr 25, 2012 at 8:18 AM, prakash_ajp wrote:
> Is it true that faceting is case sensitive? That would be disastrous for
> our
> requirement :(
>
>
it depends on your schema definition: if you lower case your tokens both
for index and query sides, the faceting should not be case sensitive.
Is it true that faceting is case sensitive? That would be disastrous for our
requirement :(
--
View this message in context:
http://lucene.472066.n3.nabble.com/Auto-suggest-on-indexed-file-content-filtered-based-on-user-tp3934565p3937370.html
Sent from the Solr - User mailing list archive at Nabb
The first one may not work because the number of users can be big. Besides,
the users can simply register themselves and start using it. It won't work
if an admin has to intervene in the registration process.
The second could work I guess. But the problem would be data duplication as
users might a
Another option is to use faceting (via the facet.prefix param) for your
auto-suggest. It's not as fast and scalable as using one of the
Suggester implementations, but it does allow arbitrary fq parameters to
be included in the request to limit the results.
http://wiki.apache.org/solr/SimpleFa
I don't know if there is a really good solution here. The problem is that
suggester (and the trunk FST version) simply traverse the terms in
the index. there's not even a real concept of those terms belonging to
any document. Since your security level is on a document basis, that
makes things hard.
yes only spellcheck indexed build field is for suggest query
I believe, filtering a documents on search handler using fq parameter and spell
suggest are two part we are discussing here.
lets say you have field for spellcheck - used to build spell dictionary
using copyField for populating a spe
I read on a couple of other web pages that fq is not supported for suggester.
I even tried the query and it doesn't help. My understanding was, when the
suggest (spellcheck) index is built, only the field chosen is considered for
queries and the other fields from the main index are not available fo
I'm new to Solr, but I would think the fq=[username] would work here.
http://wiki.apache.org/solr/CommonQueryParameters#fq
Mike
-Original Message-
From: prakash_ajp [mailto:prakash_...@yahoo.com]
Sent: Tuesday, April 24, 2012 11:07 AM
To: solr-user@lucene.apache.org
Subject: Re:
On Apr 24, 2012, at 9:37 PM, prakash_ajp wrote:
> Right now, the query is a very simple one, something like q=text. Basically,
> it would return ['textview', 'textviewer', ..]
hmm, so you're using default query field
>
> But the issue is, the 'textviewer' could be from a file that is out of
>
Right now, the query is a very simple one, something like q=text. Basically,
it would return ['textview', 'textviewer', ..]
But the issue is, the 'textviewer' could be from a file that is out of
bounds for this user. So, ultimately I would like to include the userName in
the query. As mentioned ea
can you please share a sample query?
-Jeevanandam
On 24-04-2012 1:49 pm, prakash_ajp wrote:
I am trying to implement an auto-suggest feature. The search feature
already
exists and searches on file content in user's allotted workspace.
The following is from my schema that will be used for se
ld that contains only important key/product terms from the
> text.
> >>>>>>
> >>>>>> Regards
> >>>>>> Johan
> >>>>>>
> >>>>>> On Wed, Sep 1, 2010 at 9:12 PM, Robert Petersen
> >&g
;>>> Regards
>>>>>> Johan
>>>>>>
>>>>>> On Wed, Sep 1, 2010 at 9:12 PM, Robert Petersen
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> We do
s (since the index's docs are small and not complex) are logged as
>> >> typically 1 ms if not 0 ms. It's funny but sometimes it is so fast no
>> >> milliseconds have elapsed. Incredible if you ask me... :)
>> >>
>> >> Once you get
es it is so fast no
> >> milliseconds have elapsed. Incredible if you ask me... :)
> >>
> >> Once you get SOLR to consider the whole phrase as just one big term, the
> >> wildcard is very fast.
> >>
> >> -Original Message-
> >>
:impalah...@googlemail.com]
Sent: Wednesday, September 01, 2010 12:35 PM
To: solr-user@lucene.apache.org
Subject: Re: Auto Suggest
Hi Robert,
Interesting approach, how many documents do you have in Solr?
I have about 2 million and I just wonder if it might be a bit slow.
Regards
Johan
On Wed, Sep 1, 201
a hundred thousand, and solr response
>>>>> times (since the index's docs are small and not complex) are logged as
>>>>> typically 1 ms if not 0 ms. It's funny but sometimes it is so fast no
>>>>> milliseconds have elapsed. Incredible if you ask
he index's docs are small and not complex) are logged as
>>>> typically 1 ms if not 0 ms. It's funny but sometimes it is so fast no
>>>> milliseconds have elapsed. Incredible if you ask me... :)
>>>>
>>>> Once you get SOLR to consider th
you get SOLR to consider the whole phrase as just one big term, the
>>> wildcard is very fast.
>>>
>>> -Original Message-
>>> From: Eric Grobler [mailto:impalah...@googlemail.com]
>>> Sent: Wednesday, September 01, 2010 12:35 PM
>>> To: solr-
dible if you ask me... :)
>>>
>>> Once you get SOLR to consider the whole phrase as just one big term, the
>>> wildcard is very fast.
>>>
>>> -Original Message-
>>> From: Eric Grobler [mailto:impalah...@googlemail.com]
>>> Sent: W
---
>> From: Eric Grobler [mailto:impalah...@googlemail.com]
>> Sent: Wednesday, September 01, 2010 12:35 PM
>> To: solr-user@lucene.apache.org
>> Subject: Re: Auto Suggest
>>
>> Hi Robert,
>>
>> Interesting approach, how many documents do you have in S
the whole phrase as just one big term, the
> wildcard is very fast.
>
> -Original Message-
> From: Eric Grobler [mailto:impalah...@googlemail.com]
> Sent: Wednesday, September 01, 2010 12:35 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Auto Suggest
>
> Hi
you get SOLR to consider the whole phrase as just one big term, the
wildcard is very fast.
-Original Message-
From: Eric Grobler [mailto:impalah...@googlemail.com]
Sent: Wednesday, September 01, 2010 12:35 PM
To: solr-user@lucene.apache.org
Subject: Re: Auto Suggest
Hi Robert,
Interesting app
Hi Robert,
Interesting approach, how many documents do you have in Solr?
I have about 2 million and I just wonder if it might be a bit slow.
Regards
Johan
On Wed, Sep 1, 2010 at 7:38 PM, Robert Petersen wrote:
> I do this by replacing the spaces with a '%' in a separate search field
> which is
I do this by replacing the spaces with a '%' in a separate search field
which is not parsed nor tokenized and then you can wildcard across the
whole phrase like you want and the spaces don't mess you up. Just store
the original phrase with spaces in a separate field for returning to the
front end
Given below are the steps for auto-suggest and spellcheck in single query:
Make the change in TermComponent part in solrconfig.xml
true
termsComponent
spellcheck
Use given below query format for getting autosuggest and spellcheck
suggestion.
http
Am 03.06.2010 16:45, schrieb Andrzej Bialecki:
> You are right to a certain degree. Still, there are some contention
> points in Lucene/Solr, how threads are allocated on available CPU-s, and
> how the heap is used, which can make a two-JVM setup perform much better
> than a single-JVM setup given
On 2010-06-03 13:38, Michael Kuhlmann wrote:
> Am 03.06.2010 13:02, schrieb Andrzej Bialecki:
>> ..., and deploy this
>> index in a separate JVM (to benefit from other CPUs than the one that
>> runs your Solr core)
>
> Every known webserver ist multithreaded by default, so putting different
> Solr
Am 03.06.2010 13:02, schrieb Andrzej Bialecki:
> ..., and deploy this
> index in a separate JVM (to benefit from other CPUs than the one that
> runs your Solr core)
Every known webserver ist multithreaded by default, so putting different
Solr instances into different JVMs will be of no use.
-Mich
On 2010-06-03 09:56, Michael Kuhlmann wrote:
> The only solution without "doing any custom work" would be to perform a
> normal query for each suggestion. But you might get into performance
> troubles with that, because suggestions are typically performed much
> more often than complete searches.
The only solution without "doing any custom work" would be to perform a
normal query for each suggestion. But you might get into performance
troubles with that, because suggestions are typically performed much
more often than complete searches.
The much faster solution that needs own work would be
I was interested in the same thing and stumbled upon this article:
http://www.mattweber.org/2009/05/02/solr-autosuggest-with-termscomponent
-and-jquery/
I haven't followed through, but it looked promising to me.
Tim
-Original Message-
From: Jay Hill [mailto:jayallenh...@gmail.com]
Sent
I'm painfully new to Solr so please be gentle if my suggestion is terrible!
Could you use highlighting to do this? Take the first n results from a query
and show their highlights, customizing the highlights to show the desired
number of words.
Just a thought.
Patrick
-Original Message
hi shalin,
can you please share code or tutorial documents for (it'll be great help)
1. Prefix search on shingles
2. Exact (phrase) search on n-grams
The regular prefix search also works. The good thing with these is that you
can filter and different stored value is also possible.
??
thank
On Mon, Jun 22, 2009 at 4:55 PM, Paul Libbrecht wrote:
> I'm not sure I'm understanding fully this thread,
>
> on the one hand it speaks about tuning the appropriate analyzer to get
> mixed case matching...
> This part I am not addressing and I zapped that part of the suject.
>
> on the other han
I'm not sure I'm understanding fully this thread,
on the one hand it speaks about tuning the appropriate analyzer to get
mixed case matching...
This part I am not addressing and I zapped that part of the suject.
on the other hand it seems to speak about an auto-suggestion facility?
Is this ht
On Mon, Jun 22, 2009 at 2:55 PM, Ingo Renner wrote:
>
> Hi Shalin,
>
> I think
>> that by naming it as /autoSuggest, a lot of users have been misled since
>> there are other techniques available.
>>
>
> what would you suggest?
>
>
There are many techniques. Personally, I've used
1. Prefix se
Am 22.06.2009 um 11:09 schrieb Shalin Shekhar Mangar:
Hi Shalin,
I think
that by naming it as /autoSuggest, a lot of users have been misled
since
there are other techniques available.
what would you suggest?
Ingo
--
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2
On Fri, Jun 19, 2009 at 12:50 PM, Ian Holsman wrote:
> I've noticed that one of the new features in Solr 1.4 is the Termscomponent
> which enables the Autosuggest.
>
TermsComponent *can* be used for autosuggest though I don't think that was
the original motivation. In the end it just the same th
65 matches
Mail list logo
