And keep in mind you do need quotes around your searchTerm if it consists
of multiple words - q=text_exact_field:"your_unquoted_query"
otherwise Solr will interpret "two words" as: "exact_field:two
defaultfield:words"
(Maybe not directly applicable for your problem Kristian, but I just want
to men
I'm using the new AnalyzingSuggester (my code is available on
http://pastebin.com/tN9yXHB0)
and I got the synonyms "whisky,whiskey" (they are bi-directional)
So whether the user searches for whiskey or whisky, I want to retrieve all
documents that have any of them.
However, for autosuggest, I wou
> probably with an implied SHOULD
>
> whereas
> (field1:"article test" OR field2:"article test" OR ... )
> is parsing as phrase queries. That is, test must appear immediately after
> article in either field1 ro field2
>
> Best
> Erick
>
>
&g
Hi there,
I'm implementing a didYouMean in Java, which will returns collated terms.
Unfortunately, the only way (?) to retrieve those collated terms is by
"getCollationQueryString()", which will look something like this:
input for my query: atricle test
my final query: (field1:atricle test OR fiel
Ok, I see - you want to send a JSON Object which contains the query
parameters.
As far as I know, that's not possible out-of-the-box, so you'll have to
create a custom SearchHandler
http://lucene.apache.org/solr/4_1_0/solr-core/org/apache/solr/handler/component/SearchHandler.html
for
that.
In the
I'm not sure if I understood you..
You want to send a request like http://localhost/solr/select?
q=*:*&wt=json&start=0&fq=course_id:"18" and get back only parts of the
response for further processing?
Then the easiest way is to retrieve the whole json and post-process only
"responseHeader.params".
What do you want to achieve with these tests?
Is it meant as a regression, to make sure that only the queries/boosts you
changed are affected?
Then you will have to implement tests that cover your specific
schema/boosts. I'm not aware of any frameworks that do this - we're using
Java based tests t
The solution, as pointed out on
http://stackoverflow.com/questions/14732713/solr-autosuggest-with-diacritics/14743278
,
is not to use a copyField but instead use the AnalyzingSuggester on the
StrField directly.
Cheers!
On 7 February 2013 17:30, Sebastian Saip wrote:
> It's the s
It's the same with whitespace removed unfortunately - still getting back
"testname" then.
I'm not quite sure how to test this via the Lucene API - in particular, how
to define the KeywordTokenizer with ASCII+LowerCase, so I can't test this
atm :/
BR Sebastian Saip
more, when I fed the document without index-analyzers, then added
the index-analyzers, restarted without refeeding and queried, it returned
the right value (so this seems to retrieve the index, rather than the
actual stored value?)
Or maybe I just configured it the wrong way :?
Theres not really much documentation about this yet :(
BR Sebastian Saip
10 matches
Mail list logo