Hi Steve,
MemoryIndex appears to be exactly what I'm looking for. Thank you!
Mark
On Mon, Mar 1, 2010 at 2:01 PM, Steven A Rowe wrote:
> Hi Mark,
>
> On 03/01/2010 at 3:35 PM, Mark Ferguson wrote:
> > I will be processing short bits of text (Tweets for example), and
>
that _text_ as query to my indexed location
list, and get a hit.
Is this something that is doable, or does someone envision a different
approach to the problem? Thanks for your time.
Mark Ferguson
One approach is to use dynamic fields, making the value of the second field
part of the name of the first field. So for example, you would have:
doc.Add (new Field ("Field1_A", "C", Field.Store.YES,
Field.Index.UN_TOKENIZED));
doc.Add (new Field ("Field1_B", "D", Field.Store.YES,
Field.Index.UN_TO
thing which has been
discussed here before. Thanks very much in advance,
Mark Ferguson
up example, but I think it describes pretty thoroughly the
problem I'm trying to solve. In my real world problem, I'm storing the
full-text of web pages, and I really don't want to be duplicating that much
text to set the granularity lower.
Mark Ferguson
On Tue, Nov 18, 2008 at
query that would be
equivalent to +username:ajax +page_title:news, or if it's even possible. (I
should also mention that I am creating the queries programmatically, not
using the query parser, so anything goes).
Any other ideas?
Mark Ferguson
On Tue, Nov 18, 2008 at 1:06 PM, Ian Lea &l
elds isn't required), but I do need to have one document per url. I am
looking for suggestions for a strategy on implementing this requirement.
Thanks,
Mark Ferguson
> Another approach is to use WildcardTernEnum and/or
> RegexTermEnum to build up a filter and use the filter as
> part of the query. What you loose with this approach is
> that the filter (and wildcards) then don't contribute to
> scoring. But this isn't a huge price to pa
Hello,
I am currently keeping an index of all our client's usernames. The search
functionality is implemented using a PrefixFilter. However, we would like to
expand the functionality to be able to search any part of a user's name,
rather than requiring that it begin with the query string. So for e
Hello,
I am currently keeping an index of all our client's usernames. The search
functionality is implemented using a PrefixFilter. However, we would like to
expand the functionality to be able to search any part of a user's name,
rather than requiring that it begin with the query string. So for e
Hi everyone,
I have written an extension of IndexWriter which overrides its
doAfterFlush() method. I had no problems with this in Lucene 2.2 but I
noticed that in Lucene 2.3 the behavior of doFlush() has been changed so as
to only call doAfterFlush() on deletions rather than on both deletions and
11 matches
Mail list logo
