Many thanks Mike.
In a given document, I usually have 15-20 fields out of which 6-7 fields
are plain key-value fields.
Typically these key-value fields don't involve prefixes, reflexes, fuzzies
etc...It's always a full match. Non-existent values are also not possible
during search.
In such a cas
Initially, I queried our (v4.4) index with a single MultiFieldQueryParser andÂ
Operator.AND to ensure that all search terms appeared in the results.
Since then, however, we've needed to query more flexibly, using a BooleanQuery
to merge several subqueries (in order to apply different analyzers to
What are you getting from looking at your admin/analysis page? That should
help a lot. Otherwise you haven't provided much info about what's failing,
for instance debug=query output to see what gets through your parser.
You might review:
http://wiki.apache.org/solr/UsingMailingLists
Best,
Erick
As I indicated in my previous message, we need actual queries and the actual
indexed data where matches are failing.
Note that *NALYZE will not match ANALYZER. So, it might be that you have
composed queries in which some of the terms match properly and only some
fail.
-- Jack Krupansky
Jack,
I am using WhitespaceAnalyzer while both indexing and searching the data. To
avoid the case-sensitive dependency, I ensure that both of them are upper-cased.
I generally search against the space separated CONTENTS field for the search
terms. Hence while searching, I can imagine Whitespace
For free deployments I use www.openshift.com
but only if the expected load is very low or experimental, otherwise
you need a paid for hosting.
Sanne
On 18 November 2013 04:43, Goutham Tholpadi wrote:
> Thanks for the heads up, Uwe!
>
> Which (free) java web app hosting service do people generall
