Build: https://hudson.apache.org/hudson/job/Solr-3.x/213/
All tests passed
Build Log (for compile errors):
[...truncated 20564 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-ma
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/3205/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.SolrExampleStreamingTest.testCommitWithin
Error Message:
expected:<1> but was:<0>
Stack Trace:
junit.framework.AssertionFailedError: expected:<1> but
is there anyone familiar with MG4J(http://mg4j.dsi.unimi.it/)
it says Multithreading. Indices can be queried and scored concurrently.
maybe we can learn something from it.
2010/12/31 Li Li :
> plus
> 2 means search a term need seek many times for tis(if it's not cached in tii)
>
> 2010/12/31 Li Li
Build: https://hudson.apache.org/hudson/job/Lucene-trunk/1411/
All tests passed
Build Log (for compile errors):
[...truncated 17900 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
plus
2 means search a term need seek many times for tis(if it's not cached in tii)
2010/12/31 Li Li :
> searching multi segments is a alternative solution but it has some
> disadvantages.
> 1. idf is not global?(I am not familiar with its implementation) maybe
> it's easy to solve it by share glob
searching multi segments is a alternative solution but it has some
disadvantages.
1. idf is not global?(I am not familiar with its implementation) maybe
it's easy to solve it by share global idf
2. each segments will has it's own tii and tis files, which may make
search slower(that's why optimizati
[
https://issues.apache.org/jira/browse/SOLR-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976154#action_12976154
]
Edward Rudd commented on SOLR-975:
--
>From looking at the diff it looks like it could fix it.
Build: https://hudson.apache.org/hudson/job/Lucene-3.x/227/
All tests passed
Build Log (for compile errors):
[...truncated 20926 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-
[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976149#action_12976149
]
Hoss Man commented on SOLR-2303:
I'm an idiot .. trying to catch up on mail i completely mis
[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976146#action_12976146
]
Robert Muir commented on SOLR-2303:
---
hoss, exactly what I tested... I think it doesn't sho
[
https://issues.apache.org/jira/browse/SOLR-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976145#action_12976145
]
Hoss Man commented on SOLR-975:
---
FYI: i'm pretty sure yonik fixed this as part of SOLR-1930, bu
[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976143#action_12976143
]
Hoss Man commented on SOLR-2303:
I think the purpose of the log4j-over-slf4j jars was so tha
[
https://issues.apache.org/jira/browse/SOLR-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-2301.
Resolution: Not A Problem
Based on the info you have provided, it seems that your problem has nothing to
do
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/3195/
2 tests failed.
FAILED: org.apache.solr.util.DateMathParserTest.testCoreRegistration
Error Message:
Forked Java VM exited abnormally. Please note the time in the report does not
reflect the time until the VM exit.
S
You might want to push it back a week later than that. Some take extended
vacations during the week of new years. (*shogatsu* or *oshogatsu) *is
pretty popular in japan, Some people take extra days off to account for
having to spend time with family during christmas etc.
On Thu, Dec 30, 2010 at
[
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2611:
Attachment: LUCENE-2611-branch-3x.patch
branch_3x version of IntelliJ config files, including code
Scott,
We should communicate on the public list as much as possible. I'll put
together the draft proposal today, post it here, and ask for feedback
from both the Lucene PMC and the community. We will wait over the
weekend and Monday to allow people who might have additional input the
opportunity t
I would take an existing Incubator Proposal and copy and paste it into a new
one and then send the link here and get people to start editing on it.
-Grant
On Dec 30, 2010, at 2:45 PM, Lombard, Scott wrote:
>
> From everything that was said it seems apparent to me that the only way for
> Lucen
[
https://issues.apache.org/jira/browse/LUCENE-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2611:
Attachment: LUCENE-2611.patch
Added IntelliJ codestyle definition and instructions for putting it
[
https://issues.apache.org/jira/browse/LUCENE-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2838:
--
Attachment: LUCENE-2838-no-topscorer-opt.patch
After thinking one day about it, I found some p
Scott,
I will gladly help put this proposal together and would like to
volunteer as a committer. I am communicating with others to find some
additional candidates to be committers.
Regarding Heath, a quote from his last message in this thread:
"While I have developed extensively against Lucene.
>>>until we fix Lucene to run a single search concurrently (which we
>>>badly need to do).
> I am interested in this idea.(I have posted it before) do you have some
> resources such as papers or tech articles about it?
> I have tried but it need to modify index format dramatically and we use
> solr
I did another test using lucene 4 trunk with default codecs. it's file
is the same as lucene 2.9.
the speed is almost the same as lucene 2.9
>> I think it could be the
>>fact that AND query does block reads (64 doc/freqs at once) instead of
>>doc-at-once? Ie, because of this, the query is efficit
remove unnecessary (and problematic) log4j jars in contribs
---
Key: SOLR-2303
URL: https://issues.apache.org/jira/browse/SOLR-2303
Project: Solr
Issue Type: Improvement
Compo
[
https://issues.apache.org/jira/browse/SOLR-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2303:
--
Attachment: SOLR-2303.patch
> remove unnecessary (and problematic) log4j jars in contribs
>
[
https://issues.apache.org/jira/browse/LUCENE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976035#action_12976035
]
Robert Muir commented on LUCENE-2837:
-
Mike, also if you apply LUCENE-2751, tests rand
[
https://issues.apache.org/jira/browse/LUCENE-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2838:
--
Attachment: LUCENE-2838.patch
Cleaned up patch:
- removed a useless testcase, no longer needed
[
https://issues.apache.org/jira/browse/LUCENE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976032#action_12976032
]
Robert Muir commented on LUCENE-2837:
-
{quote}
OK so we have to fix the multi-threaded
[
https://issues.apache.org/jira/browse/LUCENE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976031#action_12976031
]
Robert Muir commented on LUCENE-2837:
-
i noticed the comment about the shutting down o
[
https://issues.apache.org/jira/browse/LUCENE-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976027#action_12976027
]
Earwin Burrfoot commented on LUCENE-2840:
-
I use the following scheme:
* There is
[
https://issues.apache.org/jira/browse/LUCENE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976020#action_12976020
]
Uwe Schindler commented on LUCENE-2837:
---
bq. That sounds like a great improvement -
Multi-Threading in IndexSearcher (after removal of MultiSearcher and
ParallelMultiSearcher)
---
Key: LUCENE-2840
URL: https://issues.apache.org/jira/browse/LUCENE-2840
Basically, we are moving the thread state "upwards" in Lucene's indexing chain.
Ie, very early on when indexing a doc you pick a thread-private state.
Then, the thread does all indexing into this private state,
unfettered by any sync blocks.
This is akin to moving to a process-based concurrency
On Mon, Dec 27, 2010 at 5:08 AM, Li Li wrote:
> I integrated pfor codec into lucene 2.9.3 and the search time
> comparsion is as follows:
> single term and query or query
> VINT in lucene 2.9.3 11.2 36.5 38.6
> PFor in lucene 2.9.3
[
https://issues.apache.org/jira/browse/LUCENE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976012#action_12976012
]
Michael McCandless commented on LUCENE-2837:
bq. We should discuss about how m
[
https://issues.apache.org/jira/browse/LUCENE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976013#action_12976013
]
Michael McCandless commented on LUCENE-2831:
I like ReaderContext as the name
[
https://issues.apache.org/jira/browse/LUCENE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976011#action_12976011
]
Michael McCandless commented on LUCENE-2837:
{quote}
bq. but before committing
[
https://issues.apache.org/jira/browse/LUCENE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976010#action_12976010
]
Michael McCandless commented on LUCENE-2831:
bq. The same IR could be a sub-re
38 matches
Mail list logo
