Hi,
This is the first time I am encountering this kind of scenario. Lack
of knowledge might be the reason for my surprise.
- I am using myIndexWriter.explain(Query q, int docId).
- For the same query, the explanation for most of the docs is exactly what
it's supposed to be. However, for som
Another option is to use tmpfs (memory driven file system) as a backing storage
for index. This allows to minimize disc access latency. In average case this
doesn't make sense, because OS will cache file system access quite effective if
you have enough memory. But in worst case (if you measure r
Take a look at this document:
http://lucene.apache.org/core/4_0_0-ALPHA/facet/org/apache/lucene/facet/doc-files/userguide.html
On Jul 26, 2012, at 5:33 PM, "Subramanian, Ranjith"
wrote:
> Hi Team,
>
> I would like to know if Lucene 4.0 will support facetted search.
> Thanks in advance.
>
>
The main idea behind Lucene is search the data. In most fast and scalable way
possible. For achieving this goal Lucene give up on original data availability
and consistency. So you should be ready to discard your index and rebuild it
from scratch. To do this, you need to have your original data.
Thanks a lot Aditya and Andrzej .. Your responses were really helpful.
On Fri, Jul 27, 2012 at 6:15 AM, Andrzej Bialecki wrote:
> On 26/07/2012 22:04, Phanindra R wrote:
>
>> Thanks for the reply Abdul.
>>
>> I was exploring the API and I think we can retrieve all those words by
>> using a brute
Please forgive my lack of knowledge on this theme, but why cannot Lucene /
Solr cannot be used as primary database / data store?
On Fri, Jul 27, 2012 at 3:16 AM, Aditya wrote:
> Check out these articles on this topic. Hope it helps.
> http://www.findbestopensource.com/article-detail/lucene-solr-a
On Fri, Jul 27, 2012 at 9:10 AM, Andrzej Bialecki wrote:
>
> Catching up with this thread ... Luke 4.0-ALPHA makes a similar mistake. I
> fixed this in svn (to be released in a week or so) so that:
>
> * Luke now actually checks whether a doc has term vectors for a particular
> field and adjusts t
On 26/07/2012 22:04, Phanindra R wrote:
Thanks for the reply Abdul.
I was exploring the API and I think we can retrieve all those words by
using a brute-force approach.
1) Get all the terms using indexReader.terms()
2) Process the term only if it belongs to the target field.
3) Get all the do
On 27/07/2012 00:50, Mike O'Leary wrote:
Hi Robert,
Thanks for your help. This cleared up all of the things I was having trouble
understanding about offsets and positions in term vectors.
Mike
-Original Message-
From: Robert Muir [mailto:rcm...@gmail.com]
Sent: Friday, July 20, 2012 5:5
