Just replying for others in the future. The answer to this is to do
synonyms at index time, not at query time.
Mike
On Fri 06 Jan 2012 02:35:23 PM PST, Michael Lissner wrote:
I'm trying to set up some basic synonyms. The one I've been working on
is:
us, usa, united states
My understanding
storing that content it could be returned to the searching
client. If you aren't anonymizing before sending to Solr, how are you using
the stop word filtering to do this?
Erik
On Jan 8, 2012, at 23:08 , Michael Lissner wrote:
I've got them configured at index and query time, so sounds
?
Thanks,
Mike
On 01/07/2012 10:24 PM, Michael Lissner wrote:
I switched over to the FastVectorHighlighter, but I'm struggling with
the highlighting wiki. For example, it took me a while to figure out
that Highlighter only means that a parameter doesn't work for FVH.
Can somebody wise tell me
Hi,
I'm setting up a search system that I expect lawyers to use, and I know
they're demanding about the query operators they want. I've been looking
around a bit, and while some of these are possible on the backend, I
can't see how to enable them on the front end since they lack operators:
I have a unique use case where I have words in my corpus that users
shouldn't ever be allowed to search for. My theory is that if I add
these to the stopwords list, that should do the trick.
I'm using the edismax parser and it seems to be working in my dev
environment. Is there any risk to
for the confirmation.
Mike
On Sun 08 Jan 2012 09:32:53 PM PST, Gora Mohanty wrote:
On Mon, Jan 9, 2012 at 5:03 AM, Michael Lissner
mliss...@michaeljaylissner.com wrote:
I have a unique use case where I have words in my corpus that users
shouldn't ever be allowed to search for. My theory is that if I add
I'm trying to set up some basic synonyms. The one I've been working on is:
us, usa, united states
My understanding is that adding that to the synonym file will allow
users to search for US, and get back documents containing usa or united
states. Ditto for if a user puts in usa or united
I switched over to using FastVectorHighlighting, and the problem with
maxBooleanClause is resolved. I guess this is at the expense of having
a larger index (since you have to enable termVectors, termPositions and
termOffsets), but at least it's working.
Thanks for the help.
Mike
On Tue 03
On 01/01/2012 07:48 AM, Erick Erickson wrote:
This may be the impetus for Hoss creating SOLR-2996.
Yep, it is indeed, though I believe this problem can also happen when a
user searches for something like q=a* in a big index. I need a bigger
index to know for sure about that, but from what I've
This question has come up a few times, but I've yet to see a good solution.
Basically, if I have highlighting turned on and do a query for q=*, I
get an error that maxBooleanClauses has been exceeded. Granted, this is
a silly query, but a user might do something similar. My expectation is
10 matches
Mail list logo
