On Thu, Mar 1, 2012 at 6:20 PM, Sudarshan Gaikaiwari wrote:
> Hi
>
> https://builds.apache.org/job/Lucene-trunk/javadoc/core/org/apache/lucene/document/DocValuesField.html
>
> The documentation at the above link indicates that the optimal way to
> add a DocValues field is to create it once and cha
Hi
https://builds.apache.org/job/Lucene-trunk/javadoc/core/org/apache/lucene/document/DocValuesField.html
The documentation at the above link indicates that the optimal way to
add a DocValues field is to create it once and change the value as we
are indexing multiple documents.
It also mentions t
Good point. We will add that to our todo list.
-Vineet
On Wed, Feb 29, 2012 at 10:55 PM, Li Li wrote:
> ctrl+F don't support fuzzy searching. sometimes I can't remember the whole
> long class name. I need something like *MergePolicy instead of
> LogByteSizeMergePolicy. it's better if it can to
ctrl+F don't support fuzzy searching. sometimes I can't remember the whole
long class name. I need something like *MergePolicy instead of
LogByteSizeMergePolicy. it's better if it can tolerate some typo errors
On Thu, Mar 1, 2012 at 11:39 AM, Vineet Sinha wrote:
> Thanks a lot for the feedback.
Thanks a lot for the feedback.
Regarding the Code Tab:
Yes. Eclipse provides a lot of the features of the on the tab. We just
wanted to make it easy so that people can send links to one another easily
such as in this mailing list. LXR was a large part of the inspiration of
the inspiration here.
C
great website. though I used to Eclipse and it provide good tools for
reading codes, it may be useful when I haven't development environment
outside the office.
a problem, there is no searching function like eclipse's ctrl+shift+t which
searching classes that supporting query like '*Reader'
another
Hey guys,
We have been getting great feedback from people on this list and wanted to
let you guys know of major updates that we have made to the Lucene
Architecture/Documentation site that we have been building. We would love
more feedback when you guys get the chance.
You can find the site here:
We tracked down a large memory leak (effectively a leak anyway) caused
by how Analyzer users CloseableThreadLocal.
CloseableThreadLocal.hardRefs holds references to Thread objects as
keys. The problem is that it only frees these references in the set()
method, and SnowballAnalyzer will only call s
Sounds a bit like the thread starting with
http://www.mail-archive.com/lucene-user@jakarta.apache.org/msg08849.html.
Should be possible with some combination of boosts and should/must/not logic.
--
Ian.
On Tue, Feb 28, 2012 at 1:30 AM, ☼ 林永忠 ☼ (Yung-chung Lin)
wrote:
> Hi all,
>
> I have a qu
