Yes. The query is bit long, which is the major reason.
-- --
??: "Trejkaz";
: 2012??8??16??(??) 11:09
??: "java-user";
: Re: Why does this query slow down Lucene?
On Thu, Aug 16, 2012 at 11:27 AM, zhoucheng2008 wrote:
>
I'm curious as to whether it's possible to abuse merged segment warmers to
run some queries on all documents that have been newly added to an index.
This would be run in the context of a large, continuously growing index
(using NRT search), and would allow me to publish live streams of incoming
do
Although not directly related to UI, the syntax for span queries supported
by the LucidWorks Search platform may give you some ideas for how spans can
be composed into larger queries:
http://lucidworks.lucidimagination.com/display/lweug/Proximity+Operations
-- Jack Krupansky
-Original Mes
I would like to know if anyone has ideas (or pointers to discussions) about
good ways to support advanced search options, such as the various kinds of
SpanQuery, in a search application user interface that is understandable to
non-expert users.
Thanks,
Mike
#keyword values need to be stored in a separate table that references the
main table so that you can have multiple #keyword rows per document row in
the main table. I have no idea how to make your script do this and I don't
even know if it can. You might want to check the documentation or
discussio
Hi,
I have a situation in which I have many short documents (30-400 chars).
My goal is given a phrase, find an indexed document which is a prefix of the
phrase.
Is there a way to achieve this goal using lucene using a single query?
Thanks,
David.
--
View this message in context:
http://lucene
Is this a lucene question or a mysql question or what? Since this is
the lucene list let's assume you're asking about how to get multiple
values for a field from an index. Document.getValues("keyword") looks
promising: Returns an array of values of the field specified.
--
Ian.
On Wed, Aug 15,
Loads of stuff will have changed between those 2 versions - since you
can, I'd just reindex.
--
Ian.
On Tue, Aug 14, 2012 at 10:59 PM, sunil Kumar Verma
wrote:
> We have recently moved to 3.6 from lucene 2.2 and have seen that the way
> tokens get indexed are not the same.
>
> Although we are
