Hi All,
After looking at all below discussions, i have one doubt which may be silly
or novice but i want to throw this to lucene user list.
if we have encryption layer included in our analyzer's flow of filters like
EncryptionFilter to control field-level encryption. what are the
consequences ?
Usually there's no very good reason, it's just with a bunch of people with
more or lest time and more or less pressure and different habits choose
variable names that reflect how they're thinking about the issue at the
time.
Generally when working on a bit of code if the names are confusing whoeve
I think I am hitting this problem. Since, maxIndexingThreads is not used
anymore, i see 330+ indexing threads (in the attached log:- "334 in-use
non-flushing threads states" )
The bugfix recommends using custom code to control concurrency in
IndexWriter, how can I configure it using solr6.6 ?
And this:
Similarity.SimWeight stats
I bet there are more these things. Just out of curiosity.
[邮件签名]
发件人: 马可阳
发送时间: 2017年8月6日 17:14
收件人: 'java-user@lucene.apache.org'
主题: local variable name question
In code I can see this:
final TermContext termState
while it is instance
In code I can see this:
final TermContext termState
while it is instance of TermContext, why not name it termContext rather than
termState? If termState is more describable name, why not change Class name to
TermState?
[邮件签名]
