Do we have any plan to decouple the index process?
Lucene was design for search, but according the question people ask in the
thread it beyonds search functionality sometimes. Like we might want to
customize our scoring function based on payload. Sometimes i dont need to
store TF/IDF information.
Thx very much!
Lingpipe and Gate are very useful, and new to me,
but is it too larger to realize the custom like
class TestPostingItem
{
int termId;
long startOffset;
long endOffset;
float score;
int segId;
long timeStamp;
} ?
-
---
+10
These are the kind of things you can do in GATE[1] using annotations[2].
A VERY useful feature.
-Glen
[1]http://gate.ac.uk
[2]http://gate.ac.uk/wiki/jape-repository/annotations.html
On Wed, Dec 12, 2012 at 3:02 PM, Wu, Stephen T., Ph.D.
wrote:
>>> Is there any (preliminary) code checked in
>> Is there any (preliminary) code checked in somewhere that I can look at,
>> that would help me understand the practical issues that would need to be
>> addressed?
>
> Maybe we can make this more concrete: what new attribute are you
> needing to record in the postings and access at search time?
We are actually in the [slow] process of trying to simplify the DV
APIs (calling it DV 2.0 for now...), at this branch:
https://svn.apache.org/repos/asf/lucene/dev/branches/lucene4547
If you have the itch, feel free to check it out and iterate! There
are lots of changes there, roughly summari
I think you just forgot to call iw.addDocument(doc)?
Typically one needs DocValues in a Collector or a FieldComparator or
Filter or a Similarity Scorer, etc., which already operate per-segment
and provide you an AtomicReaderContext from which you can get the
AtomicReader to lookup DocValues from .
We are hoping for 4.1 very soon! With the holidays it will be difficult to say
- but 4.1 talk has been going on for some time now. Its really a matter of
wrapping up some short term work and getting some guys to do the release work.
I dont think anyone can give you a date, but it's certainly in
Hi Uwe,
Unfortunately my IDE (Intellij) does not warn me about calling a static method
on a different class name, a nice idea I shall request the feature.
Anyway, my suggestion to avoid the confusion still holds; that the FSDirectory
open method is overridden in the subclasses, thus "NIOFSDire
Hi,
> Thanks for that, I had not realised that the open method was simply
> inherited from the FSDirectory, I should have read the docs.
>
> However, it makes no sense to me that a call to NIOFSDirectory.open() can
> end up opening a MMapDirectory, and in general that a call to one subclass
> can
Thanks for that, I had not realised that the open method was simply inherited
from the FSDirectory, I should have read the docs.
However, it makes no sense to me that a call to NIOFSDirectory.open() can end
up opening a MMapDirectory, and in general that a call to one subclass can end
up openin
If you want a specific directory implementation, instantiate it directly (new
NIOFSDirectory)? If you use FSDirectory.open() it will use the autodetected one
depending on OS and bitness.
About configuring your server from MMAP in a correct way, read
http://blog.thetaphi.de/2012/07/use-lucenes-m
Hi all,
I run my code on a cluster where I have to preset resource limits and therefore
the processes have limited virtual memory causing OOME when using MMapDirectory
on large indexes.
This means I explicitly use NIOFSDirectory (i.e. Directory indexDirectory =
NIOFSDirectory.open(indexFile);)
12 matches
Mail list logo
