oh...@cox.net wrote:
- I'd have to create a (very small) index, for each sub-document, where I do
the Document.add() with just the (for example) two terms, then
- Run a query against the 1-entry index, which
- Would either give me a "yes" or "no" (for that sub-document)
As I said, I'm concerned
oh...@cox.net wrote:
Document1 subdoc1 term1 term2
subdoc2 term1a term2a
subdoc3 term1b term2b
However, I've now been asked to implement the ability to query the sub-documents.
In other words, rather t
Phil Whelan wrote:
It seems I have to use the same Analyzer for the all the fields in the
index?
Nope. Look at PerFieldAnalyzerWrapper, which is effectively a Map of
field names -> analyzers. This might help if different fields will have
very different values and semantics.
Cheers,
Paul
-
Matthew Hall wrote:
Place a delimiter between the email addresses that doesn't get removed
in your analyzer. (preferably something you know will never be searched
on)
Or add them separately (rather than:
doc.add(new Field("email", "f...@bar.com b...@foo.com c...@bar.foo" ...);
use
doc.add
iMe wrote:
This analyzer uses the StandardTokenizer which javadoc states:
Splits words at hyphens, unless there's a number in the token, in which case
the whole token is interpreted as a product number and is not split.
But looking to my index with luke, I saw that my product reference
AB-CD-
Dragon Fly wrote:
I'd like to get a hit if I do:
Field1:A AND Field2:C
This is fine because that's how Lucene works. However, I do not want to get a
hit if I do:
Field1:A AND Field2:D
The reason that I don't want a hit is because A is the first element in Field1
and D is the second el
Hi Jay,
Anyone knowledgeable on how to get unique hits using the BooleanQuery?
If I have 2 queries so the when the 1st query is processed then the 2nd
query will not anymore return the same results from the 1st query.
Do you mean you want to run two separate queries -- get all the results
fr
Michael Barbarelli wrote:
Can I instantiate a standard analyzer with an argument containing my own
stop words? If so, how? Will they be appended to or override the built-in
stop words?
You can do it with one of the alternate constructors, and they'll
override the build-in list.
---
String
pl.Entry class
should have an additional property, .locale, to ensure that different
locales get different comparators.
Does this make sense? Or am I totally full of it (it's Friday, it's
possible).
Cheers,
Paul Cowan
--
Hi Grant and Otis,
Thanks for the feedback, I appreciate it. You've given some good ideas.
Sounds like a really interesting system! I am curious, are your users
fluent in multiple languages or are you using some type of translation
component?
The former. We're talking about construction pro
this project goes ahead, it's possible (even likely) that it would be
contributed back to the Lucene sandbox. As such, I'm very interested to
hear about any suggestions, criticisms, or other feedback you might have.
Cheers,
Paul Cowan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
11 matches
Mail list logo
