My mistake. You're so right- it should be 64.0 as a first try, not 1024.
On Fri, Dec 17, 2010 at 7:44 PM, Jason Rutherglen
wrote:
> Probably best to add something here as it currently has nothing
> regarding merge policies and has a long standing TODO on the
> indexDefaults. http://wiki.apache.o
[
https://issues.apache.org/jira/browse/SOLR-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lance Norskog closed SOLR-2101.
---
Resolution: Duplicate
SOLR-2116 duplicates this and it is more recent.
A thousand pardons for filing t
[
https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-2819.
-
Resolution: Fixed
committed and merged to 3.x
in 3.x i kept the test code in CMS (even though u
[
https://issues.apache.org/jira/browse/LUCENE-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972880#action_12972880
]
Robert Muir commented on LUCENE-2816:
-
committed revision 1050737. I'll wait a bit for
Hello,
Regardless of Set fields parameter,
SolrPluginUtils#docListToSolrDocumentList method loads all of the stored
fields. Shouldn't it just load the fields given in the set? Should I file a
jira ticket?
When small bug in TestCase is seen what is the preffered way to inform it? Open
an issue
[
https://issues.apache.org/jira/browse/SOLR-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet Arslan updated SOLR-2291:
---
Attachment: SOLR-2291.patch
> JSONWriter.writeSolrDocument() does not respect its Set returnFields
>
JSONWriter.writeSolrDocument() does not respect its Set returnFields
parameter.
---
Key: SOLR-2291
URL: https://issues.apache.org/jira/browse/SOLR-2291
Project: Solr
[
https://issues.apache.org/jira/browse/LUCENE-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2820:
---
Attachment: LUCENE-2820.patch
Patch.
I changed CMS.sync to .join() to any still-ali
contrib/demo's tests leave threads running
--
Key: LUCENE-2823
URL: https://issues.apache.org/jira/browse/LUCENE-2823
Project: Lucene - Java
Issue Type: Bug
Components: Examples
R
FilterManager starts threads with no way to stop, and should be in
contrib/remote, not core
---
Key: LUCENE-2821
URL: https://issues.apache.org/jira/browse/LUCENE-2821
TimeLimitingCollector starts thread in static {} with no way to stop them
-
Key: LUCENE-2822
URL: https://issues.apache.org/jira/browse/LUCENE-2822
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/LUCENE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972869#action_12972869
]
Michael McCandless commented on LUCENE-2723:
Looks good Yonik!
> Speed up Luc
CMS fails to cleanly stop threads
-
Key: LUCENE-2820
URL: https://issues.apache.org/jira/browse/LUCENE-2820
Project: Lucene - Java
Issue Type: Bug
Reporter: Michael McCandless
Assignee:
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2708/
1 tests failed.
FAILED:
org.apache.lucene.search.TestRemoteCachingWrapperFilter.testTermRemoteFilter
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some thr
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2707/
1 tests failed.
FAILED:
org.apache.lucene.search.TestRemoteCachingWrapperFilter.testTermRemoteFilter
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some thr
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2706/
1 tests failed.
REGRESSION:
org.apache.lucene.search.TestRemoteCachingWrapperFilter.testTermRemoteFilter
Error Message:
Some threads threw uncaught exceptions!
Stack Trace:
junit.framework.AssertionFailedError: Some
[
https://issues.apache.org/jira/browse/LUCENE-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972855#action_12972855
]
Jason Rutherglen commented on LUCENE-2500:
--
DirectIOLinuxDirectory is in trunk an
[
https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2819:
Attachment: LUCENE-2819.patch
ok final patch.
We can't quite fail() yet (it just warns for now) b
[
https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972850#action_12972850
]
Jason Rutherglen commented on LUCENE-2814:
--
bq. backporting to 3.x...
Out of cu
[
https://issues.apache.org/jira/browse/SOLR-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972847#action_12972847
]
Jason Rutherglen commented on SOLR-2290:
Tom, I think this can be generified to use
[
https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972842#action_12972842
]
Michael McCandless commented on LUCENE-2814:
OK I committed to trunk. I'll le
[
https://issues.apache.org/jira/browse/LUCENE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-2723:
-
Attachment: LUCENE-2723_openEnum.patch
Here's a small patch that may be sufficient to enable dro
[
https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2819:
Attachment: LUCENE-2819.patch
here's an updated patch, I think its much better.
The core tests are
I committed a fix for this.
I think there was actually only one failure, which cascaded due still
running threads spilling over to other test methods (LUCENE-2819).
The one failure was caused by LUCENE-2811 (SI tracks hasVectors) in
addIndexes(Directory[]); we were failing to copy over the vector
the termsInfosDivisor for readers opened by indexWriter should be configurable
in Solr
--
Key: SOLR-2290
URL: https://issues.apache.org/jira/browse/SOLR-2290
Project:
[
https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972816#action_12972816
]
Michael McCandless commented on LUCENE-2818:
I think a bw compat exception is
[
https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2819:
Attachment: LUCENE-2819.patch
I worked on mike's patch a bit... here's an updated version.
I thin
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2691/
4 tests failed.
FAILED:
org.apache.solr.util.SolrPluginUtilsTest.testAddToNamedListPrimitiveTypes
Error Message:
Forked Java VM exited abnormally. Please note the time in the report does not
reflect the time until t
[
https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2819:
---
Attachment: LUCENE-2819.patch
Attaching current patch; includes lots of noise and do
[
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2694:
--
Attachment: LUCENE-2694-FTE.patch
Here just the patch for a correct behaving FilteredTermsEnum
[
https://issues.apache.org/jira/browse/LUCENE-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972776#action_12972776
]
Robert Muir commented on LUCENE-2819:
-
I think this is the problem: lets say the main
LuceneTestCase's check for uncaught exceptions in threads causes collateral
damage?
---
Key: LUCENE-2819
URL: https://issues.apache.org/jira/browse/LUCENE-2819
Project: L
[
https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972772#action_12972772
]
Shai Erera commented on LUCENE-2818:
I offered a default impl just to not break the AP
[
https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2814:
Attachment: LUCENE-2814.patch
Synced to trunk.
bq. Also, on the nocommit on exc in DW.add
I haven't seen nocommit in the code, neither as String nor as member. But we
can decide that we do @nocommit@ or something, which is less likely to be
contained in code :).
Uwe, I didn't understand your response - do you mean that if the code
contains a 'nocommit' in any of the .java files, Hudson
[
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972769#action_12972769
]
Uwe Schindler edited comment on LUCENE-2694 at 12/18/10 5:43 AM:
---
[
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972769#action_12972769
]
Uwe Schindler commented on LUCENE-2694:
---
I have also some things:
- We currently don
[
https://issues.apache.org/jira/browse/LUCENE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972767#action_12972767
]
Michael McCandless commented on LUCENE-2814:
Patch looks great! Nice work Ear
[
https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-2818:
Priority: Minor (was: Major)
This change is really minor, but I think, convinient.
You d
[
https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972765#action_12972765
]
Earwin Burrfoot commented on LUCENE-2818:
-
bq. I think we can make a default impl
[
https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972764#action_12972764
]
Earwin Burrfoot commented on LUCENE-2818:
-
bq. Can abort() have a default impl in
I like this idea, too. But I think we have no control on this, it would be as
complicated as the mergeprops...
What we have: Hudson halfly hour builds fail when svn contains commits, so you
see it latest 30 Min later.
Uwe
"Shai Erera" schrieb:
>Hi
>
>Out of curiosity, I searched if we can
But. Er. What if we happen to have "nocommit" in a string, or in some
docs, or as a name of variable?
On Sat, Dec 18, 2010 at 12:47, Michael McCandless
wrote:
> +1 this would be great :)
>
> Mike
>
> On Fri, Dec 17, 2010 at 10:45 PM, Shai Erera wrote:
>> Hi
>> Out of curiosity, I searched if we
[
https://issues.apache.org/jira/browse/LUCENE-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972763#action_12972763
]
Michael McCandless commented on LUCENE-2818:
+1 I think this'd be a good simpl
+1 this would be great :)
Mike
On Fri, Dec 17, 2010 at 10:45 PM, Shai Erera wrote:
> Hi
> Out of curiosity, I searched if we can have a nocommit comment in the code
> fail the commit. As far as I see, we try to avoid accidental commits (of say
> debug messages) by putting a nocommit comment, but
[
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972758#action_12972758
]
Michael McCandless commented on LUCENE-2694:
If I force scoring BQ rewrite for
[
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972759#action_12972759
]
Michael McCandless commented on LUCENE-2694:
I love seeing cacheCurrentTerm re
Build: https://hudson.apache.org/hudson/job/Solr-trunk/1346/
All tests passed
Build Log (for compile errors):
[...truncated 20163 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e
48 matches
Mail list logo
