Why won't Ian's suggestion work? You haven't really given us a clue what it
is about
your attempt that didn't work. The expected and actual output would be
useful...
But Ian's notion is the well-known issue that lexical and numeric sorting
aren't
at all the same. You'd get reasonable results if yo
Hi
I'll explain my use case more and then explain the out come of my
implementation:
I have lucene documents that look like this:
Field name Field Value
dataId TYX-CC-124
categoryCATEGORY A
What I would like to do is for a given collection of dat
hello, all, here comes my question:
as far as I know, lucene now offer the feature that ones can search some
doc while the index which contains that specific doc is modifying.
for example(pseudocode) :
while indexWriter(indexDir).add(docA) is doing, can indexReader(indexDir)
offer the query func
hello everyone
I have this test code:
IndexReader ir = getReader();
TermQuery q = new TermQuery(new
Term("sub_id",NumericUtils.intToPrefixCoded(57)));
Filter f = new QueryWrapperFilter(q);
try
{
DocIdSet s = f.getD
OK, maybe I'm catching on at last. Have you considered just skipping the
whole search thing entirely? Something like using one of the classes
implementing TermDocs to get the document for a particular term (one of
the elements of your list of dataIds in this case). That would give you the
doc numbe
Hi Uwe,
Erick explained it pretty well and i got it now, but generally you're right
RTFM ;-)
Nevertheless I'm in the need of the functionality to change the stored
value during analysis or tokenization or filtering (what ever works).
Thats how it can be done in FAST FDS/ESP (full processing) co
Hi Bernd,
> Nevertheless I'm in the need of the functionality to change the stored
value
> during analysis or tokenization or filtering (what ever works).
>
> Thats how it can be done in FAST FDS/ESP (full processing) compared to
> Lucene/Solr (sparse processing).
>
> Do you have any idea, how
