[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463203
]
Jed Wesley-Smith commented on LUCENE-140:
-
Alas, this doesn't appear to be the problem. We are still getting
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463202
]
Jed Wesley-Smith commented on LUCENE-140:
-
Hi Michael,
This is awesome, I have prepared a patched 1.9.1:
ht
I just meant that the discussion (on the Java board) included an
incorrect testcase, since the code should not have worked according
to the specification.
It may still be relevant, I was just pointing out that it is suspect.
Unless the bug has been posted & verified in the Java Bug Database,
robert engels <[EMAIL PROTECTED]> wrote on 08/01/2007 17:39:45:
> The Java discussion that is cited is not valid (at least in terms of
> the test case provided).
... right ... that discussion really is irrelevant - I read that too quick,
sorry for that.
>
> The javadoc for RandomAccessFile state
The Java discussion that is cited is not valid (at least in terms of
the test case provided).
The javadoc for RandomAccessFile states:
/**
* Sets the file-pointer offset, measured from the beginning of
this
* file, at which the next read or write occurs. The offset may be
*
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463176
]
Doron Cohen commented on LUCENE-140:
Amazed by this long lasting bug report I was going similar routes to Mike, a
Can anyone help answer the question or at least point
out if the question is vague or should be directed to
some other place.
Thanks
--- Ming Lei <[EMAIL PROTECTED]> wrote:
> Can I solely rely on RMI's remote object cleanup
> mechanism for this?
> It seems that RemoteSeachable.close() has to be
[
https://issues.apache.org/jira/browse/LUCENE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463124
]
Hoss Man commented on LUCENE-718:
-
i recently realized that let's you specify the level of messages to
be logged -
[
https://issues.apache.org/jira/browse/LUCENE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-718:
Attachment: check.bootclasspath.patch
> possible build.xml addition to ensure 1.4 class compatibility
> ---
On Monday 08 January 2007 20:33, Ali Salehi wrote:
> 1. The search time for simple queries such as precision:\+0002 is
> really high (4-10 seconds). I want to know if this search time is normal
> 2. The search gives TooManyClauses exception when I'm searching for a
> data item with the queries
Holy Rabbit Batman! Take that merge factor down. 100,000 is much to high. I
think I have seen that above 90 wont help you much. 100,000 is just insane
though...try like 50 and call me in the morning.
- Mark
On 1/8/07, Ali Salehi <[EMAIL PROTECTED]> wrote:
Hello,
I have a question about the sca
Hi there,
I am using lucene 2.0.0 in an open-source project:
http://m-m-m.googlecode.com/svn/trunk/mmm-search/
It is still work in progress but it has nice features such as a fault tolerant
query parser and a nice plugable parser collection for various fileformats.
For the presentation I use luc
[
https://issues.apache.org/jira/browse/LUCENE-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved LUCENE-732.
-
Resolution: Fixed
I've commited queryparser_datetools2.patch with two changes...
1) revised the class le
Hello,
I have a question about the scalability of the Lucene.
I'm a lucene beginner and I would like to use it to index several
million measurements (400 Millions). A measurement has a type,
owner, id, precision and data.
As an experiment, I tried to insert 5M values into a lucene index using
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-140:
-
Assignee: Michael McCandless (was: Lucene Developers)
> docs out of order
>
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-140:
-
Assignee: Michael McCandless (was: Lucene Developers)
> docs out of order
>
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463093
]
Michael McCandless commented on LUCENE-140:
---
I've committed a fix for this one case to the trunk.
I'm lea
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463093
]
Michael McCandless commented on LUCENE-140:
---
I've committed a fix for this one case to the trunk.
I'm lea
I don't have the sources handy to check, but my guess would be this extension
is/was for Term Vectors with Positions.
Like somebody else said recently, it would be good to make all these into
static finals, so we don't have to chase "string" values in the code.
Otis
- Original Message
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463029
]
Michael McCandless commented on LUCENE-140:
---
OK: I finally found one way that this corruption can occur! I
[
https://issues.apache.org/jira/browse/LUCENE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463029
]
Michael McCandless commented on LUCENE-140:
---
OK: I finally found one way that this corruption can occur! I
Le Mercredi 3 Janvier 2007 14:46, Nadav Har'El a écrit :
> On Wed, Dec 20, 2006, Michael Busch wrote about "Payloads":
> >..
> > Some weeks ago I started working on an improved design which I would
> > like to propose now. The new design simplifies the API extensions (the
> > Field API remains unch
[
https://issues.apache.org/jira/browse/LUCENE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated LUCENE-766:
---
Attachment: bugfix.patch
> Two same new field with and without Term vector make an IllegalSta
[
https://issues.apache.org/jira/browse/LUCENE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated LUCENE-766:
---
Description:
On a empty index, adding a document with two fields with the same name but wit
Two same new field with and without Term vector make an IllegalStateException
-
Key: LUCENE-766
URL: https://issues.apache.org/jira/browse/LUCENE-766
Project: Lucene - Java
Le Samedi 23 Décembre 2006 00:32, Michael Busch a écrit :
> Nicolas Lalevée wrote:
> > I have just looked at it. It looks great :)
>
> Thanks! :-)
>
> > But I still doesn't understand why a new entry in the fieldinfo is
> > needed.
>
> The entry is not really *needed*, but I use it for
> backwards-
26 matches
Mail list logo
