Hi Siraj,
Even in the approach presented earlier we can have search capabilities for
the individual field by making the document with the individual fields and
the copy fields.
Let me know if I'm wrong.
On Thu, Oct 25, 2012 at 1:18 AM, Siraj Haider wrote:
> Any other suggestions?
>
> regards
You haven't given us much to go on here, you might review:
http://wiki.apache.org/solr/UsingMailingLists
But one can imagine that this must be something you're doing that's
unusual, or more people would have reported something similar.
At a guess (since you haven't really told us _anything_ abou
>From what I heard, taking search offline is solution that the
organization had said they wouldn't want. We plan to increase the
frequency of index reload every day and hence taking offline so many
times a day wouldn't be pragmatic.
Here is the current implementation: We use a store that has the
Just curious - why not take your search feature offline during the
reindexing? That would seem sensible from an operational perspective, I
think.
On Tue, Oct 23, 2012 at 2:03 PM, Raghavan Parthasarathy <
raghavan8...@gmail.com> wrote:
> Hi,
>
> We are using Lucene-core and we reindex once a day a
Small correction: UAX29URLEmailAnalyzer = StandardAnalyzer + URL + Email. (Full
support for URLs with the file:, ftp:, and http/s: protocols; full email
support.)
ClassicAnalyzer is a different beast altogether. First of all, it doesn't
implement Unicode segmentation - it has a non-standard to
Thanks... that's it... sorry to siturb with something that simple.
>
> De: Ian Lea
>Para: java-user@lucene.apache.org; Carlos de Luna Saenz
>
>Enviado: Miércoles, 24 de octubre, 2012 1:55 P.M.
>Asunto: Re: SortField.STRING
>
>SortField.Type.STRING maybe?
>
>
s/work break/word break/
-- Jack Krupansky
-Original Message-
From: Jack Krupansky
Sent: Wednesday, October 24, 2012 3:52 PM
To: java-user@lucene.apache.org ; kiwi clive
Subject: Re: StandardAnalyzer functionality change
I didn't explicitly say it, but ClassicAnalyzer does do exactly
I didn't explicitly say it, but ClassicAnalyzer does do exactly what you
want it to do - work break plus email and URL, or StandardAnalyzer plus
email and URL.
-- Jack Krupansky
-Original Message-
From: kiwi clive
Sent: Wednesday, October 24, 2012 1:27 PM
To: java-user@lucene.apache.
Any other suggestions?
regards
-Siraj
(212) 306-0154
-Original Message-
From: Siraj Haider [mailto:si...@jobdiva.com]
Sent: Tuesday, October 23, 2012 6:06 PM
To: java-user@lucene.apache.org
Cc: simon.willna...@gmail.com
Subject: RE: Scoring based on document
Thanks for the suggestion, bu
SortField.Type.STRING maybe?
Can't help with the other question. It's generally best to send one
question per message. Looking at the source code might help.
--
Ian.
On Wed, Oct 24, 2012 at 6:55 PM, Carlos de Luna Saenz
wrote:
> I am migrating code from Lucene 3 to Lucene 4... and i have th
I am migrating code from Lucene 3 to Lucene 4... and i have the following code
that i don't know how to change:
hits = searcher.search(queryGlobal, searcher.maxDoc(),
new Sort(new SortField(ordenarPor, SortField.STRING)));
I already change the searcher.maxDoc() to indxr.max
Thanks for the responses chaps, very informative, and most appreciated :-)
From: Ian Lea
To: java-user@lucene.apache.org
Sent: Wednesday, October 24, 2012 4:19 PM
Subject: Re: StandardAnalyzer functionality change
If you want email addresses, UAX29URLEmail
If you want email addresses, UAX29URLEmailAnalyzer is another alternative.
--
Ian.
On Wed, Oct 24, 2012 at 3:56 PM, Jack Krupansky wrote:
> Yes, by design. StandardAnalyzer implements "simple word boundaries" (the
> technical term is "Unicode text segmentation"), period. As the javadoc says,
>
Yes, by design. StandardAnalyzer implements "simple word boundaries" (the
technical term is "Unicode text segmentation"), period. As the javadoc says,
"As of Lucene version 3.1, this class implements the Word Break rules from
the Unicode Text Segmentation algorithm, as specified in Unicode Stand
Hi all,
Sorry if I'm asking an age old question but we have migrated to lucene 3.6.0
and I see StandardAnalyzer has changed its behaviour, particularly when
tokenizing email addresses. From reading the forums, I understand
StandardAnalyzer was renamed to ClassicAnalyzer - is this the case ?
I
15 matches
Mail list logo
