[
https://issues.apache.org/jira/browse/LUCENE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494631
]
Doron Cohen commented on LUCENE-875:
I checked with 1.4 earlier today and didn't get these "Multiple sources"
wa
[
https://issues.apache.org/jira/browse/LUCENE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reopened LUCENE-875:
-
Grrr... it seems we may need to reopen this, i didn't realize until just now
that the previous patch (includ
FYI...
- Forwarded by Doron Cohen on 09/05/2007 22:04 -
Doron Cohen/Haifa/IBM wrote on 09/05/2007 22:04:05:
> This is a configuration issue, caused by:
>- contrib/db was added to javadoc creation
>- contrib/db jars are dynamically loaded
>
> This should solve it:
>- run targ
I think the topest thing lucene/solr should do:
1: more easy use and less code
2: distributed index and search
3: manage these index and search server
4: test method or tool
i don't agree
2007/5/8, Grant Ingersoll <[EMAIL PROTECTED]>:Yep, my advice always is use
a db for what a db is designed fo
On 5/2/07, Michael McCandless <[EMAIL PROTECTED]> wrote:
It would merge based on size (not # docs), would be free to merge
adjacent segments (not just rightmost segments), and would merge N
(configurable) at a time.
Hopefully it will always be easy to switch the meaning of "size" so it
could be
On 5/3/07, Michael McCandless <[EMAIL PROTECTED]> wrote:
I like your idea to keep "delete count per segment" in the segments
file. This information is certainly useful to the merge policy
because it should proportionally reducde a segments size according to
what %tg of its docs are deleted, and,
[
https://issues.apache.org/jira/browse/LUCENE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-877.
---
Resolution: Fixed
Fix Version/s: 2.2
> 2.1 Locking documentation in "Apache Lu
[
https://issues.apache.org/jira/browse/LUCENE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-877:
-
Assignee: Michael McCandless
> 2.1 Locking documentation in "Apache Lucene - Inde
[
https://issues.apache.org/jira/browse/LUCENE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494601
]
Michael McCandless commented on LUCENE-877:
---
Huh, I thought I fixed this with LUCENE-771. I'll take it.
>
2.1 Locking documentation in "Apache Lucene - Index File Formats" section "6.2
Lock File" out dated
---
Key: LUCENE-877
URL: https://issues.apache.org/jira/browse/LUCE
Grant Ingersoll wrote:
nightly docs and javadocs on p.a.o.
Why can't these be on zones? We can put a redirect on p.a.o if we like,
but what's the problem with serving these internal developer resources
from zones? Wouldn't that avoid a lot of hassle?
Doug
So, I think what we want is:
Nightly builds on zones (i.e. the jars)
nightly docs and javadocs on p.a.o.
The first is taken care of, the second will need a crontab setup to
export the docs from the SVN repo. I can set this up and then update
the appropriate docs and remove the redirect on p.
I was just looking at the new warnings -
You're right, no reason to enumerate the jars. I thought I tried
this way and it didn't work, but yours does work, so I must have
tried it somehow wrong.
Doron
>
> i just commited what i thought was a minor fix to teh build.xml to update
> the contrib lis
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project lucene-java has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project lucene-java has an issue affecting its community integration.
This issue affects
i just commited what i thought was a minor fix to teh build.xml to update
the contrib list in the javadoc task .. only afterwards did i realize this
exposed some new warnings/bugs in the contrib/db javadocs, which seem to
be because the jars it dpeends on arent' being included in the
javadoc.class
16 matches
Mail list logo
