Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/3533/
1 tests failed.
FAILED: org.apache.lucene.util.TestVersion.testFilter
Error Message:
Forked Java VM exited abnormally. Please note the time in the report does not
reflect the time until the VM exit.
Stack Trace:
junit
[
https://issues.apache.org/jira/browse/SOLR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979264#action_12979264
]
Lance Norskog commented on SOLR-2129:
-
bq.Don't want to at least log this? } catch (
[
https://issues.apache.org/jira/browse/LUCENE-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979255#action_12979255
]
Uwe Schindler commented on LUCENE-2855:
---
One thing in your patch: Lucene tests shoul
[
https://issues.apache.org/jira/browse/LUCENE-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979253#action_12979253
]
Uwe Schindler commented on LUCENE-2855:
---
+1 to commit.
In general, one should never
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979252#action_12979252
]
Jason Rutherglen commented on LUCENE-2324:
--
{quote}I think segment 1 shouldn't be
[
https://issues.apache.org/jira/browse/LUCENE-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Crestani updated LUCENE-2855:
-
Attachment: lucene_2855_adriano_crestani_2011_01_08.patch
Here is the fix for the proble
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979248#action_12979248
]
Michael Busch commented on LUCENE-2324:
---
{quote}
I think start simple - the addDocum
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979247#action_12979247
]
Michael Busch commented on LUCENE-2324:
---
bq. I think the risk is a new DWPT likely w
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979243#action_12979243
]
Jason Rutherglen commented on LUCENE-2324:
--
To further clarify, we also no longer
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979229#action_12979229
]
Jason Rutherglen commented on LUCENE-2324:
--
{quote}the "flush the world" case? (I
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979193#action_12979193
]
Samuel García Martínez commented on SOLR-236:
-
The NPE noticed by Shekhar Nirkhe
[
https://issues.apache.org/jira/browse/LUCENE-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2829:
---
Attachment: LUCENE-2829.patch
New patch. I added VirtualMethods to Sim to make sure
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979189#action_12979189
]
Michael McCandless commented on LUCENE-2324:
bq. The proposed change is simply
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979190#action_12979190
]
Michael McCandless commented on LUCENE-2324:
{quote}
And there's the case of t
[
https://issues.apache.org/jira/browse/SOLR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979188#action_12979188
]
Hoss Man commented on SOLR-2288:
Reminder to self: feedback from rmuir on the mailing list t
: > + public static final Set EMPTY_STRING_SET =
Collections.emptySet();
: > +
:
: I don't know about this commit... i see a lot of EMPTY set's and maps
: defined statically here.
...
: I think we should be using the Collection methods, for example on your
: first file:
Hmmm... i am us
[
https://issues.apache.org/jira/browse/LUCENE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2854.
Resolution: Fixed
> Deprecate SimilarityDelegator and Similarity.lengthNorm
>
[
https://issues.apache.org/jira/browse/LUCENE-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979178#action_12979178
]
Michael McCandless commented on LUCENE-2828:
We won't fix this for 3.x or 4.0,
[
https://issues.apache.org/jira/browse/LUCENE-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2828:
---
Fix Version/s: 3.0.4
2.9.5
> SimilarityDelegator broke back-compa
[
https://issues.apache.org/jira/browse/LUCENE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979174#action_12979174
]
Michael McCandless commented on LUCENE-2854:
bq. Is it possible to remove this
[
https://issues.apache.org/jira/browse/LUCENE-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979164#action_12979164
]
Robert Muir commented on LUCENE-1260:
-
bq. Is there no way to remove this stupid stati
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979162#action_12979162
]
Jason Rutherglen commented on LUCENE-2324:
--
And there's the case of the thread ca
[
https://issues.apache.org/jira/browse/LUCENE-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979160#action_12979160
]
Uwe Schindler commented on LUCENE-1260:
---
bq. Here's a patch for the general case, an
[
https://issues.apache.org/jira/browse/LUCENE-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1260:
Attachment: LUCENE-1260_defaultsim.patch
Here's a patch for the general case, and it also adds a w
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979149#action_12979149
]
Jason Rutherglen commented on LUCENE-2324:
--
{quote}As soon as a DWPT is pulled fr
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979146#action_12979146
]
Michael McCandless commented on LUCENE-2324:
{quote}
What if the user wants a
[
https://issues.apache.org/jira/browse/SOLR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979144#action_12979144
]
Tommaso Teofili edited comment on SOLR-2129 at 1/8/11 11:09 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979144#action_12979144
]
Tommaso Teofili edited comment on SOLR-2129 at 1/8/11 11:09 AM:
--
[
https://issues.apache.org/jira/browse/SOLR-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SOLR-2129:
--
Attachment: SOLR-2129-version-5.patch
Changes are:
# drop StringBuffer for StringBuilder in UIMA
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/3511/
1 tests failed.
REGRESSION: org.apache.lucene.search.TestThreadSafe.testLazyLoadThreadSafety
Error Message:
unable to create new native thread
Stack Trace:
java.lang.OutOfMemoryError: unable to create new native thread
[
https://issues.apache.org/jira/browse/LUCENE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979141#action_12979141
]
Robert Muir commented on LUCENE-2854:
-
Is it possible to remove this method Query.getS
[
https://issues.apache.org/jira/browse/LUCENE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2854:
Attachment: LUCENE-2854_fuzzylikethis.patch
here is the patch for fuzzylikethis for trunk... so yo
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979139#action_12979139
]
Jason Rutherglen commented on LUCENE-2324:
--
Also, don't we need the global lock f
>>
Nope - wasn't me that added the license stuff into NOTICE.txt ;-)
But, including Jetty's NOTICE seems appropriate for our NOTICE. It's
just the license parts of the HSQLDB and SLF4J that should be moved to
LICENSE.txt
<<
The NOTICE text is actually different from the LICENSE text for
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979138#action_12979138
]
Jason Rutherglen commented on LUCENE-2324:
--
{quote}So all that's guaranteed after
On Sat, Jan 8, 2011 at 10:06 AM, Yonik Seeley
wrote:
> There also wasn't any business about "and then add _nothing_ unless
> you can find explicit policy documented
> somewhere in the ASF that says it is required." I was following
> examples from other projects and any docs I could find at the t
On Sat, Jan 8, 2011 at 8:10 AM, wrote:
> From svn, Yonik seems to be the go-to guy for LICENSE and NOTICE stuff.
> Yonik, do you remember why the HSQLDB and Jetty notice text was included in
> Solr's NOTICE.txt?
Nope - wasn't me that added the license stuff into NOTICE.txt ;-)
But, including
Because they are shipped with Solr. I don't see why it hurts to give people
information about what's in the download.
On Jan 8, 2011, at 8:10 AM,
wrote:
> From svn, Yonik seems to be the go-to guy for LICENSE and NOTICE stuff.
> Yonik, do you remember why the HSQLDB and Jetty notice text
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979129#action_12979129
]
Michael McCandless commented on LUCENE-2324:
bq. I guess we don't really need
[
https://issues.apache.org/jira/browse/LUCENE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979128#action_12979128
]
Michael McCandless commented on LUCENE-2854:
The above patch applies to 3.x
F
The weird thing is, all of our collectors, IMO, are optimized for the
non-paging scenario, when I would venture to guess that the very large majority
of users out there do paging. AFAICT, about the only people who don't do
paging are those who do deep, downstream analysis which requires them to
>From svn, Yonik seems to be the go-to guy for LICENSE and NOTICE stuff.
>Yonik, do you remember why the HSQLDB and Jetty notice text was included in
>Solr's NOTICE.txt? The incubator won't release ManifoldCF until we answer
>this question. ;-)
Karl
F
[
https://issues.apache.org/jira/browse/LUCENE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2854:
---
Attachment: LUCENE-2854.patch
I think we should simply make a hard break on the Sim.
[
https://issues.apache.org/jira/browse/LUCENE-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979118#action_12979118
]
Michael McCandless commented on LUCENE-2831:
bq. It seems we also need to migr
You are probably right... the LICENSE.txt also contains many instances
of incorrect capitalization, I noticed that all versions of of this
file I can find anywhere have this problem :)
On Sat, Jan 8, 2011 at 6:14 AM, wrote:
> This list might be interested to know that the current Solr LICENSE an
On Mon, Jan 3, 2011 at 18:18, Yonik Seeley wrote:
> On Thu, Nov 11, 2010 at 3:22 PM, Jan Høydahl /
> Cominvent wrote:
>> The problem with large "start" is probably worse when sharding is involved.
>> Anyone know how the shard component goes about fetching
>> start=100&rows=10 from say 10 sh
On Fri, Jan 7, 2011 at 10:47 PM, wrote:
>
> + public static final Set EMPTY_STRING_SET = Collections.emptySet();
> +
I don't know about this commit... i see a lot of EMPTY set's and maps
defined statically here.
There is no advantage to doing this, even the javadocs explain:
Implementation note
This list might be interested to know that the current Solr LICENSE and NOTICE
file contents are not Apache standard. The ManifoldCF project based its
LICENSE and NOTICE files on the Solr ones and got the following icy reception
in the incubator:
>>
The NOTICE file is still incorrect and i
48 matches
Mail list logo
