On Sep 10, 2007, at 7:56 PM, [EMAIL PROTECTED] wrote:
1) What are the various languages supported by Lucene.?
Looks like its able to handle only English . We are trying to see
if it works with Japanese / Chinese and other characters
Can some one answer
Lucene internally
Dear Gurus
We are evaluating the possibliity of using Lucene for our
Searching needs. I have few questions before we embark on this project
of evaluating Lucene
1) What are the various languages supported by Lucene.? Looks
like its able to handle only English . We are trying
On 10-Sep-07, at 3:00 PM, Grant Ingersoll wrote:
What I truly pine for is a way to globally override Similarity on
a per-field basis. Wishful thinking...
Instead of wishful thinking, let's figure out a patch... :-)
Someday, I will find the time to delve more deeply into lucene wishful
[
https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526305
]
Michael McCandless commented on LUCENE-847:
---
> In the while loop of optimize(), LogMergePolicy.findMergesF
[
https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-847:
--
Attachment: LUCENE-847.take6.patch
OK, another rev of the patch (take6). I think it's
On Sep 10, 2007, at 5:33 PM, Mike Klaas wrote:
This is the current api for scorePayload:
public float scorePayload(byte [] payload, int offset, int length) {
ISTM that this function depends greatly on the field--what if the
end user wants to store two completely different kinds of values
On 9/10/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> This is the current api for scorePayload:
>
>public float scorePayload(byte [] payload, int offset, int length) {
>
> ISTM that this function depends greatly on the field--what if the end
> user wants to store two completely different kinds of
This is the current api for scorePayload:
public float scorePayload(byte [] payload, int offset, int length) {
ISTM that this function depends greatly on the field--what if the end
user wants to store two completely different kinds of values in
different fields? Could fieldName be added?
[
https://issues.apache.org/jira/browse/LUCENE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-992.
---
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [Patch Available
