Hi Daniel,
Solr has (e)dismax just for the propose you described.
https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax+Query+Parser
Please see pf pf2 pf3 parameters
Ahmet
On Monday, June 27, 2016 3:55 PM, Daniel Bigham wrote:
Hi Ahmet,
Yes, thanks... that did come to mind a
No, it implies that Lucene is a low level library that allows people like
you and me, application developers, to develop applications that meet our
business and technical needs.
Like you, most of the things I work with prefer documents where the search
terms are close together, often preferably in
Hi Ahmet,
Yes, thanks... that did come to mind and is the strategy I'm playing with.
However, if you are giving a user a plain text field and using the Lucene query
parser, it doesn't create optional clauses for boosting purposes.
Does this imply that anyone wanting to use Lucene in conjunct
It looks like you have a casing issue maybe?
You indexed variableWithHelpString.
But searched for variablewithhelpstring*
Mike McCandless
http://blog.mikemccandless.com
On Mon, Jun 27, 2016 at 5:07 AM, Baskakov Daniel wrote:
> I've just noticed that not only dynamic adding/removing entities
I've just noticed that not only dynamic adding/removing entities tests
fail, but also a simple indexing.
Here is a boiled down structure of the test:
@BeforeClass
public static void beforeClass() throws Exception
{
// ContextManager is a domain model
contextManager = createContextMa
Can you boil this down to a small standalone test case showing the issue?
Mike McCandless
http://blog.mikemccandless.com
On Mon, Jun 27, 2016 at 4:03 AM, Baskakov Daniel wrote:
> Thank you Mike.
>
> Commit is performed after each indexing op in unit tests only:
>
> public void commitNow() th
Thank you Mike.
Commit is performed after each indexing op in unit tests only:
public void commitNow() throws IOException
{
if (getIndexWriter().hasUncommittedChanges())
{
getIndexWriter().commit();
}
}
In production environment I have a timer that performs commit periodi
