Possible to use span queries to avoid stepping over null index positions

2011-08-26 Thread ikoelliker
Hello, In our indexes we have a field that is a combination of other various metadata fields (i.e. subject, from, to, etc.). Each field that is added has a null position at the beginning. As an example, in Luke the field data looks like: null_1 this is a test subject null_1 ikoelliker email addr

Re: Lucene test documents (TREC)

2011-08-26 Thread Erick Erickson
I think it depends on the organization that provides the collections, see: http://trec.nist.gov/data/docs_eng.html Best Erick On Fri, Aug 26, 2011 at 1:37 AM, Sara naznazi wrote: > hi > I want to know is TREC documents (a test collection) free or not? Is there > any other collection like TREC to

Re: Searching behaviour with content containing decimal points

2011-08-26 Thread Erick Erickson
You have to do some normalizing here, and I don't think there's anything available out of the box, so you'll probably have to roll your own filter that does the normalization for this field. Be a little cautious, though. Your example, while fine itself, may not generalize. Your rule for normalizat

Re: Code for Precision in Lucene

2011-08-26 Thread Yakob
I did, go here http://jacobian.web.id/2010/12/01/calculating-precision-and-recall-in-lucene/ On 8/26/11, Sara naznazi wrote: > hi > I have some text files and want to calculate Precision and Recall. dont > refer me to Lucen in action book, I already studied it and just want to know > is there an

Re: SSD Experience (on developer machine)

2011-08-26 Thread Toke Eskildsen
On Wed, 2011-08-24 at 11:46 +0200, David Nemeskey wrote: > Theoretically, in the case described above, it would be possible to move > 'static' data (data of cells that have not been written to for a long time) > to > the 5GB in question and use the 'fresher' cells as free space; this could be >

Re: SSD Experience (on developer machine)

2011-08-26 Thread Toke Eskildsen
On Wed, 2011-08-24 at 13:42 +0200, Federico Fissore wrote: > I add a question. Toke you said that "the current state of wear can be > queried". How? With a S.M.A.R.T.-tool, preferably up-to-date to get it to display the vendor-specific properties in an easy to understand manner. On my Ubuntu-box