On Tue, Feb 19, 2013 at 12:57 PM, Jack Krupansky wrote:
> Oops, sorry for the "Solr" answer. In Lucene you need to simply index the
> same value, once as a raw string and a second time as a tokenized text
> field. Grouping would use the raw string version of the data.
>
> Yeah, thanks Jack. Was ju
Hey Eric,
the problem here is more tricky than it seems. and IndexReader is a
point in time snapshot that should be shared as long as possible. If
you share this across threads you can not just call close you need to
count references. We have utilities for this (ReferenceManager /
SearcherManager)
Any other Lucene/Solr enthusiasts attending ApacheCon in Portland next week?
Maybe we can pick a time and place to grab a few beers and exchange some ideas
and user knowledge.
--
Nico Krijnen
-
To unsubscribe, e-mail: java-user-
Hi Simon,
Many thx for this info. I am just digging into the new Lucene3/4
goodies, so excuse my stupid questions.
Having a SearcherManager sounds great, I will try it.
Still I like the paragdim to 'close' the resources I have created. Why
not having a close() that simply does nothing for no
What replaces the computeNorm method in DefaultSimilarity in 4.1
Ive always subclassed DefaultSimilarity to resolve an issue whereby when
document has multiple values in a field (because has one-many
relationship) its score worse then a document which just has single
value but the computeNorm
Well, you don't need to "store" both copies since they will be the same.
They both need to be "indexed" (string form for grouping, text form for
keyword search), but only one needs to be "stored".
-- Jack Krupansky
-Original Message-
From: Ramprakash Ramamoorthy
Sent: Tuesday, Februa
IndexSearcher in Lucene 4.0 does not hook resources and never will.
IndexSearcher is a thin wrapper class which is not IO related so implementing
Closeable is simply wrong. This is the same paradigm like a input stream should
never be closed by a method unless explicitly documented. The code tha
Hi Uwe,
Thx for to point that IndexSearcher does not retain resources.
If we continue the analogy with the FilterInputStream which decorates
the InputStream, you can see that FIS.close calls close() on the wrapped
IS [1]. But this may be not to be compared with the Searcher/Reader way
of work
This example lacks some similarities: FilterInputStream is itsself an
InputStream. IndexSearcher is a completely different class with totally
different functionality. The Index Reader holds the resources. This was never
different in previous Lucene versions! In earlier version you were able to o
: Subject: ApacheCon meetup
:
: Any other Lucene/Solr enthusiasts attending ApacheCon in Portland next week?
I won't make it to ApacheCon this year (first time in a long time
actually) but I'm fairly certain there will be a Lucene MeetUp of some
kind -- there always is.
This is usually organi
I've added a Lucene meetup to the Wednesday night meetup proposed schedule.
I'm speaking on Wednesday morning.
Let's get the word spread to the Portland tech community as well, making it a
good way to bring in folks in the area that may not be also attending ApacheCon.
Erik
On Feb 1
Ok, as we can not construct the searcher with a directory, we don't need
to close it anymore.
Agree that InputStream is not analogous, but I was thinking you were
refering to it in your previous mail.
Thx again, Eric
On 19/02/2013 17:59, Uwe Schindler wrote:
This example lacks some similar
Strange test failure after converting code from Lucene 3.6 to Lucene 4.1
public void testIndexPuid() throws Exception {
addReleaseOne();
RAMDirectory ramDir = new RAMDirectory();
createIndex(ramDir);
IndexReader ir = IndexReader.open(ramDir);
Fields fiel
On 19/02/2013 20:56, Paul Taylor wrote:
Strange test failure after converting code from Lucene 3.6 to Lucene 4.1
public void testIndexPuid() throws Exception {
addReleaseOne();
RAMDirectory ramDir = new RAMDirectory();
createIndex(ramDir);
IndexReader ir = Inde
phew! thanks for clarifying
simon
On Tue, Feb 19, 2013 at 11:19 PM, Paul Taylor wrote:
> On 19/02/2013 20:56, Paul Taylor wrote:
>>
>>
>> Strange test failure after converting code from Lucene 3.6 to Lucene 4.1
>>
>> public void testIndexPuid() throws Exception {
>>
>> addReleaseOne();
>
Hi,
On Tue, Feb 19, 2013 at 11:04 AM, A. L. Benhenni wrote:
> I am currently writing an indexer class to index texts from stdin. I also
> need the text to be tokenized and stored to access the termvector of the
> document.
Actually, you don't need to store documents to access their term
vectors,
On Tue, Feb 19, 2013 at 9:09 PM, Jack Krupansky wrote:
> Well, you don't need to "store" both copies since they will be the same.
> They both need to be "indexed" (string form for grouping, text form for
> keyword search), but only one needs to be "stored".
>
> Yeah, yeah Jack, understood. That wa
17 matches
Mail list logo
