Re: TermsEnum.docFreq() returns 0

We ran the checkIndex and a simple test case. It passes. Actually, I had assumed problem with lucene, whereas it was an issue with our custom codec. I do not know how to confirm whether a new codec works correctly. Are there any tools/existing test-cases available for validation? -- Ravi On

RE: Performance of NULL check *:* -category:[* TO *]

Hi -We are using 3.0.3. Could you point me to a similar functionality prior to 4.0?-Vidhya -- View this message in context: http://lucene.472066.n3.nabble.com/Performance-of-NULL-check-category-TO-tp4063021p4063158.html Sent from the Lucene - Java Users mailing list archive at Nabble.com.

Re: Find index version with an index reader

Take a look at org.apache.lucene.index.CheckIndex. That displays the versions of the segment files. Note the plurals - that's a complication you may need to deal with. Or read|store whatever you want with IndexWriter.get|setCommitData(...). You can get the currently running version via

lucene and mongodb

Hi team, I'm working with apache lucene 4.2.1 and I would like to store lucene index in a NoSql database. So my questions are, - Can I store the lucene index in a mongodb database ? thanks you team!

Re: lucene and mongodb

Hi, On Tue, May 14, 2013 at 10:35 AM, Rider Carrion Cleger rider.carr...@gmail.com wrote: - Can I store the lucene index in a mongodb database ? I don't know whether it's possible, but even if it was, I would not recommend it. Lucene works best on local filesystems, and even better if the disk

Re: Find index version with an index reader

On Tue, May 14, 2013 at 1:58 PM, Ian Lea ian@gmail.com wrote: Take a look at org.apache.lucene.index.CheckIndex. That displays the versions of the segment files. Note the plurals - that's a complication you may need to deal with. Or read|store whatever you want with

Re: TermsEnum.docFreq() returns 0

On Tue, May 14, 2013 at 3:03 AM, Ravikumar Govindarajan ravikumar.govindara...@gmail.com wrote: We ran the checkIndex and a simple test case. It passes. Actually, I had assumed problem with lucene, whereas it was an issue with our custom codec. Phew, thanks for bringing closure! I do not know

Retrieving FieldInfo

Hi, I was looking to a way to obtain FieldInfo(s) from the IndexReader; we need in some way to describe the index. Can I do this? AtomicReader ar = indexReader.leaves().get(0).reader(); // than call ar.getFieldInfos(); What I mean is, can I suppose every AtomicReader in leaves()

Re: Retrieving FieldInfo

If your documents *always* contain the same fields then yes. But in general, you can do: addDocument(f:value); commit(); addDocument(c:value); commit(); And each AtomicReader will contain different fields. As getFieldInfos() documents Get the {@link FieldInfos} describing all fields in

Re: lucene and mongodb

Thank you Adrien. I did not think about index's scalability but a safe place to store them (like a SGBD relation... or NoSql). So, can I have for sure scalability and safety with a distribution on top of Lucene like Solr ? On Tue, May 14, 2013 at 11:08 AM, Adrien Grand jpou...@gmail.com wrote:

Re: Retrieving FieldInfo

OK, thanks for the reply! Nicola. On Tue, 2013-05-14 at 14:19 +0300, Shai Erera wrote: If your documents always contain the same fields then yes. But in general, you can do: addDocument(f:value); commit(); addDocument(c:value); commit(); And each AtomicReader will contain

Re: lucene and mongodb

Hi, On Tue, May 14, 2013 at 1:34 PM, Rider Carrion Cleger rider.carr...@gmail.com wrote: So, can I have for sure scalability and safety with a distribution on top of Lucene like Solr ? Yes, Solr can help you shard your index and add replicas, see http://wiki.apache.org/solr/SolrCloud. --

Re: lucene and mongodb

That was tried with Lucandra/Solandra, which stored the Lucene index in Cassandra, but was less than optimal, so that model was discarded in favor of indexing Cassandra data directly into Solr/Lucene, side-by-side in each Cassandra node, but in native Lucene. The latter approach is now

Re: Retrieving FieldInfo

I now this can sound horrible/flexible/... but this mean I can add two documents with the same field name, but different configurations, for example different IndexOptions? Nicola. On Tue, 2013-05-14 at 12:52 +0100, Nicola Buso wrote: OK, thanks for the reply! Nicola. On Tue,

unindexed field boost

Hello all, i was wondering why unindexed fields can't be boosted compare to lucene 3. since these fields are still in the score calculation when i checked the score explanation. Is there any clean way to pass this? Thanks Tamer

Re: TermsEnum.docFreq() returns 0

Thanks for the help Mike. Was quick to jump to a wrong conclusion My codec does not implement Term-Vectors, Payloads, DocValues and Norms. It should be trivial to implement Payloads, but I am not sure about others. Anyways, I can generate a HTML report and identify failures based on individual

Re: Retrieving FieldInfo

On Tue, May 14, 2013 at 10:02 AM, Nicola Buso nb...@ebi.ac.uk wrote: I now this can sound horrible/flexible/... but this mean I can add two documents with the same field name, but different configurations, for example different IndexOptions? Yes and no :) Lucene will happily index such

Re: Retrieving FieldInfo

Thanks for the explanation, I'm not in this situation but it's helpful to understand better lucene. Nicola Michael McCandless luc...@mikemccandless.com wrote: On Tue, May 14, 2013 at 10:02 AM, Nicola Buso nb...@ebi.ac.uk wrote: I now this can sound horrible/flexible/... but this mean I can

IndexReader doc method performance troubles

Hi there, We've been having troubles with performance regarding IndexReader's * documenthttp://lucene.apache.org/core/4_1_0/core/org/apache/lucene/index/IndexReader.html#document(int) *(int docID) method. In summary: Why would the

AW: lucene and mongodb

Hi mate, we did that (w/ lucene 3.6) and reconsidered it as very bad idea afterwards. Why? (a) out of the box, mongodb does only 16-mb files. Lucene files grow (much) larger than that. (b) lucene indices seem highly optimized to create good performance when reading them from disk. A layer

Re: why did I build index slower and slower ？

up - -- Email: wuqiu.m...@qq.com -- -- View this message in context: http://lucene.472066.n3.nabble.com/why-did-I-build-index-slower-and-slower-tp4062798p4063395.html Sent from the Lucene - Java Users mailing list archive at Nabble.com.