Seems like we don't respect segments that don't return hits for a
certain query
Index: lucene/src/java/org/apache/lucene/search/IndexSearcher.java
===
--- lucene/src/java/org/apache/lucene/search/IndexSearcher.java (revision
10667
[
https://issues.apache.org/jira/browse/LUCENE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2609:
---
Attachment: LUCENE-2609.patch
Fix some more Ant targets and adds javadocs-test-framework and
jar-te
[
https://issues.apache.org/jira/browse/LUCENE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2609:
---
Attachment: LUCENE-2609.patch
Last patch had misplaced text outside a target.
> Generate jar contai
committed a fix in revision 1066764
simon
On Thu, Feb 3, 2011 at 9:35 AM, Simon Willnauer
wrote:
> Seems like we don't respect segments that don't return hits for a
> certain query
>
> Index: lucene/src/java/org/apache/lucene/search/IndexSearcher.java
> ==
[
https://issues.apache.org/jira/browse/LUCENE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990027#comment-12990027
]
Uwe Schindler commented on LUCENE-2609:
---
Hi Shai, patch looks fine (applies only to
Hey folks,
we had some issues / test failure with the newSearcher due to the
initial value of TopDocs#maxScore. It is initialized to NaN which
outrules anything if we do Math.max(current, topDocs.getMaxScore());
and topDocs.totalHits == 0. I added a conditional as a quickfix but I
think we should
[
https://issues.apache.org/jira/browse/LUCENE-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2609:
---
Attachment: LUCENE-2609.patch
Patch fixes the manifest issue Uwe raised. I exposed a title attribute
[
https://issues.apache.org/jira/browse/SOLR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990038#comment-12990038
]
Salman Akram commented on SOLR-1604:
Reminder! Any updates regarding integration with C
Thank you Jens - that has worked perfectly. And with a little modification,
my query now looks like this:
q=+(CookBook foo bar) rating_value:1^0.1 rating_value:2^0.2 ...
Many thanks for your invaluable help!
Seb
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boosting-score
can you please backport to branch_3x too? there are the same problems
there, including a test method in TestSort that i had to completely
@Ignore!
On Thu, Feb 3, 2011 at 4:11 AM, Simon Willnauer
wrote:
> committed a fix in revision 1066764
>
> simon
>
> On Thu, Feb 3, 2011 at 9:35 AM, Simon Willn
[
https://issues.apache.org/jira/browse/LUCENE-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toke Eskildsen updated LUCENE-2369:
---
Attachment: LUCENE-2369.patch
Maintenance patch bringing the code up to date with Lucene tru
[
https://issues.apache.org/jira/browse/SOLR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990060#comment-12990060
]
Robert Muir commented on SOLR-2346:
---
{noformat}
String id = (String) resulDocument.getFir
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned SOLR-96:
-
Assignee: Uwe Schindler
> Solr should support alternate charsets for XML update messages
> -
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-96:
--
Attachment: SOLR-96.patch
Here is a patch to fix this.
The whole problem *everywhere* in solr (even for c
Woah!
(by the way, Hudson is now renamed to Jenkins).
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
--- Begin Message ---
[
http://issues.jenkins-ci.org/browse/JENKINS-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:co
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-96:
--
Fix Version/s: 4.0
3.1
> Solr should support alternate charsets for XML update messages
[
https://issues.apache.org/jira/browse/SOLR-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed SOLR-190.
--
Resolution: Duplicate
Duplicate of SOLR-96.
> Encoding declaration of POSTed XML documents is ignored
>
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990104#comment-12990104
]
Uwe Schindler commented on SOLR-96:
---
Just a comment for Robert:
RFC-3023 say, text/xml wit
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990104#comment-12990104
]
Uwe Schindler edited comment on SOLR-96 at 2/3/11 2:12 PM:
---
Just a
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990107#comment-12990107
]
Robert Muir commented on SOLR-96:
-
Thanks Uwe, I can only trust the XML policeman here!
> So
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990111#comment-12990111
]
Yonik Seeley commented on SOLR-96:
--
Thanks Uwe, patch looks good!
> Solr should support alt
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-96:
--
Attachment: SOLR-96.patch
DocumentAnalysisReqHandler had the same problem, tis patch fixes this. It also
[
https://issues.apache.org/jira/browse/LUCENENET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990114#comment-12990114
]
Ivan Zlatev commented on LUCENENET-383:
---
This issue is still present in the 2.9 s
[
https://issues.apache.org/jira/browse/LUCENENET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990117#comment-12990117
]
Digy commented on LUCENENET-383:
Hi Ivan,
Can you send a *small* test case (without EP
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved SOLR-96.
---
Resolution: Fixed
Committed trunk revision: 1066819
Committed 3.x revision: 1066823
> Solr should suppo
[
https://issues.apache.org/jira/browse/SOLR-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-96:
--
Attachment: SOLR-96-3.x.patch
Here the patch for 3.x as reference (AnalysisRequestHandler was fixed, too).
I think Float.NEG_INF is good?
Mike
On Thu, Feb 3, 2011 at 4:26 AM, Simon Willnauer
wrote:
> Hey folks,
>
> we had some issues / test failure with the newSearcher due to the
> initial value of TopDocs#maxScore. It is initialized to NaN which
> outrules anything if we do Math.max(current, topDocs
Hi all,
Just a couple of questions that have arisen.
1. For handling non-distributed update requests (shards param is not present
or is invalid), our code currently
- assumes the user would like the data indexed, so gets the request
handler assigned to "/update"
- executes the request u
On Thu, Feb 3, 2011 at 8:41 AM, Uwe Schindler wrote:
> Woah!
Yay :)
> (by the way, Hudson is now renamed to Jenkins).
Yes, see eg here:
http://pelegri.wordpress.com/2011/01/29/jenkins-hudson-is-now-officially-independent/?utm_source=twitterfeed&utm_medium=twitter
At some point I expect inf
On Thu, Feb 3, 2011 at 10:12 AM, Michael McCandless
wrote:
> I think Float.NEG_INF is good?
Yeah, I'm pretty sure that's what it was for much of the past.
-Yonik
http://lucidimagination.com
-
To unsubscribe, e-mail: dev-unsubsc
[
https://issues.apache.org/jira/browse/LUCENE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990123#comment-12990123
]
Michael McCandless commented on LUCENE-2843:
bq. Thank you. I will use the Fi
[
https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1076:
---
Fix Version/s: (was: 3.2)
3.1
I think we can do this for 3.1,
[
https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2897:
---
Fix Version/s: (was: 3.2)
3.1
I think we can do this for 3.1.
Use InputStream and not Reader for XML parsing
--
Key: SOLR-2347
URL: https://issues.apache.org/jira/browse/SOLR-2347
Project: Solr
Issue Type: Bug
Reporter: Uwe Schindler
A
[
https://issues.apache.org/jira/browse/SOLR-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990132#comment-12990132
]
Uwe Schindler commented on SOLR-2347:
-
To again post the most important info from XML s
[
https://issues.apache.org/jira/browse/LUCENE-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2886:
---
Attachment: LUCENE-2886_simple64_varint.patch
New patch, including Robert's patch, a
I think we should even go one step further and make NaN an illegal
value for maxScore. I think we should add an assert in the setter and
the ctor. Objections?
On Thu, Feb 3, 2011 at 4:19 PM, Yonik Seeley wrote:
> On Thu, Feb 3, 2011 at 10:12 AM, Michael McCandless
> wrote:
>> I think Float.NEG_I
On Thu, Feb 3, 2011 at 12:19 PM, Robert Muir wrote:
> can you please backport to branch_3x too? there are the same problems
> there, including a test method in TestSort that i had to completely
> @Ignore!
I will check that - but it seems that if we go for a different default
in TopDocs#maxScore w
[
https://issues.apache.org/jira/browse/LUCENE-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990143#comment-12990143
]
Michael McCandless commented on LUCENE-2886:
OK I committed the two new Simpl
Hello,
Per Shai's previous note, we decided we wanted to work towards a 3.1
release (he mentioned a target date of march 1, don't think this will
happen)
Despite this, I propose we do a 'casual freeze' on the 3.x code base
in 7 days time, in other words we agree for a few weeks we will focus
on b
On Thu, Feb 3, 2011 at 10:52 AM, Simon Willnauer
wrote:
> I think we should even go one step further and make NaN an illegal
> value for maxScore. I think we should add an assert in the setter and
> the ctor. Objections?
If we don't initialize w/ NaN, maxScore will never be set to NaN, right?
And
+1
On Feb 3, 2011, at 11:00 AM, Robert Muir wrote:
> Hello,
>
> Per Shai's previous note, we decided we wanted to work towards a 3.1
> release (he mentioned a target date of march 1, don't think this will
> happen)
>
> Despite this, I propose we do a 'casual freeze' on the 3.x code base
> in 7
On Thu, Feb 3, 2011 at 5:05 PM, Yonik Seeley wrote:
> On Thu, Feb 3, 2011 at 10:52 AM, Simon Willnauer
> wrote:
>> I think we should even go one step further and make NaN an illegal
>> value for maxScore. I think we should add an assert in the setter and
>> the ctor. Objections?
>
> If we don't i
On Thu, Feb 3, 2011 at 11:00 AM, Robert Muir wrote:
> Despite this, I propose we do a 'casual freeze' on the 3.x code base
> in 7 days time, in other words we agree for a few weeks we will focus
> on bugs and tests only in branch_3x and try to shorten, not length the
> list of issues in JIRA (unle
[
https://issues.apache.org/jira/browse/LUCENENET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990155#comment-12990155
]
Ivan Zlatev commented on LUCENENET-383:
---
I will extract a small test case from my
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/4447/
1 tests failed.
REGRESSION:
org.apache.lucene.search.payloads.TestPayloadTermQuery.testIgnoreSpanScorer
Error Message:
MockDirectoryWrapper: cannot close: there are still open files: {_4.prx=1,
_4.fdx=1, _4.frq=1, _4.
Just to be clear, are you proposing to release 3.1 of Lucene, Solr, or
both?
Upayavira
On Thu, 03 Feb 2011 11:00 -0500, "Robert Muir" wrote:
> Hello,
>
> Per Shai's previous note, we decided we wanted to work towards a 3.1
> release (he mentioned a target date of march 1, don't think this will
[
https://issues.apache.org/jira/browse/SOLR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990172#comment-12990172
]
Yonik Seeley commented on SOLR-2346:
>From the email thread:
{quote}
One problem is tha
On Thu, Feb 3, 2011 at 5:21 PM, Yonik Seeley wrote:
> On Thu, Feb 3, 2011 at 11:00 AM, Robert Muir wrote:
>> Despite this, I propose we do a 'casual freeze' on the 3.x code base
>> in 7 days time, in other words we agree for a few weeks we will focus
>> on bugs and tests only in branch_3x and try
On Thu, 03 Feb 2011 15:12 +, "Alex Cowell"
wrote:
Hi all,
Just a couple of questions that have arisen.
1. For handling non-distributed update requests (shards param
is not present or is invalid), our code currently
* assumes the user would like the data indexed, so gets the
req
On Thu, Feb 3, 2011 at 11:37 AM, Upayavira wrote:
> Just to be clear, are you proposing to release 3.1 of Lucene, Solr, or
> both?
its all the same now
+1
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For addition
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/4448/
1 tests failed.
FAILED:
org.apache.lucene.search.payloads.TestPayloadTermQuery.testIgnoreSpanScorer
Error Message:
MockDirectoryWrapper: cannot close: there are still open files: {_0.tis=1,
_3.frq=1, _3.tvd=1, _1.frq=
[
https://issues.apache.org/jira/browse/SOLR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990185#comment-12990185
]
Robert Muir commented on SOLR-2346:
---
Right, I agree solr should work with a non-UTF8 enco
[
https://issues.apache.org/jira/browse/LUCENE-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990186#comment-12990186
]
Paul Elschot commented on LUCENE-2903:
--
When the IntBuffer is produced by ByteBuffer
[
https://issues.apache.org/jira/browse/SOLR-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990191#comment-12990191
]
Grant Ingersoll commented on SOLR-2345:
---
Hi Bill,
Can you clarify what you are tryin
FYI - I am about to commit a fix for those failures.
The problem is that the settings for field sort scoring are not
propagated to the subs
Index: lucene/src/java/org/apache/lucene/search/IndexSearcher.java
===
--- lucene/src/java/o
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/4451/
1 tests failed.
REGRESSION:
org.apache.lucene.search.payloads.TestPayloadTermQuery.testIgnoreSpanScorer
Error Message:
MockDirectoryWrapper: cannot close: there are still open files: {_g4.frq=1,
_e9.tvd=1, _g2.tvf=1,
ported to 3x in revision 1066904
On Thu, Feb 3, 2011 at 10:11 AM, Simon Willnauer
wrote:
> committed a fix in revision 1066764
>
> simon
>
> On Thu, Feb 3, 2011 at 9:35 AM, Simon Willnauer
> wrote:
>> Seems like we don't respect segments that don't return hits for a
>> certain query
>>
>> In
[
https://issues.apache.org/jira/browse/LUCENE-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990214#comment-12990214
]
hao yan commented on LUCENE-2903:
-
I think essentially the above step also need to do int
Not sure I get to vote, but a big +1
On Thu, Feb 3, 2011 at 12:02 PM, Ryan McKinley wrote:
> On Thu, Feb 3, 2011 at 11:37 AM, Upayavira wrote:
> > Just to be clear, are you proposing to release 3.1 of Lucene, Solr, or
> > both?
>
> its all the same now
>
> +1
>
> ---
Committed revision 1066904.
simon
On Thu, Feb 3, 2011 at 7:10 PM, Simon Willnauer
wrote:
> FYI - I am about to commit a fix for those failures.
>
> The problem is that the settings for field sort scoring are not
> propagated to the subs
>
>
> Index: lucene/src/java/org/apache/lucene/search/Index
[
https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990217#comment-12990217
]
Simon Willnauer commented on LUCENE-2878:
-
{quote}
How does/should scoring work?
[
https://issues.apache.org/jira/browse/LUCENE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990221#comment-12990221
]
Simon Willnauer commented on LUCENE-2751:
-
Robert, I committed a fix with revisio
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990227#comment-12990227
]
Hsiu Wang commented on SOLR-236:
I applied the SOLR-236-1_4_1-paging-totals-working.patch to
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/4454/
1 tests failed.
REGRESSION:
org.apache.lucene.benchmark.byTask.feeds.TrecContentSourceTest.testTrecFeedDirAllTypes
Error Message:
expected: but was:
Stack Trace:
at
org.apache.lucene.benchmark.byTask.feeds.Tr
[
https://issues.apache.org/jira/browse/LUCENE-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990260#comment-12990260
]
Paul Elschot commented on LUCENE-2903:
--
The conversion is done in place, no data is
On Thu, 3 Feb 2011, Wylie, Brian wrote:
Mistype (exceptions.xml) -> (extensions.xml)
This is about trunk or 3.x ?
Not the same thing, trunk is highly unstable and PyLucene is not following
it too closely. What used to be trunk at the Lucene project is now the
so-called 3.x branch, consider
I just verified, at this moment, the HEAD of the 3.x branch
http://svn.apache.org/repos/asf/lucene/pylucene/branches/branch_3x/
builds and passes all tests.
Andi..
On Thu, 3 Feb 2011, Wylie, Brian wrote:
Mistype (exceptions.xml) -> (extensions.xml)
On 2/3/11 11:29 AM, "Wylie, Brian" wrote:
[
https://issues.apache.org/jira/browse/LUCENE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990319#comment-12990319
]
Robert Muir commented on LUCENE-2751:
-
I think we are good to resolve this? I expect/
On Thu, Feb 3, 2011 at 11:37 AM, Upayavira wrote:
> Just to be clear, are you proposing to release 3.1 of Lucene, Solr, or
> both?
Both: because our development is merged, I think it makes sense to
merge release engineering too.
The users can be mostly unaware of this: for example the generated
On Thu, Feb 3, 2011 at 4:43 PM, Robert Muir wrote:
> On Thu, Feb 3, 2011 at 11:37 AM, Upayavira wrote:
>> Just to be clear, are you proposing to release 3.1 of Lucene, Solr, or
>> both?
>
> Both: because our development is merged, I think it makes sense to
> merge release engineering too.
>
> The
[
https://issues.apache.org/jira/browse/LUCENE-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990342#comment-12990342
]
Robert Muir commented on LUCENE-2208:
-
Hi Hsiu, thanks for uploading a patch to the i
[
https://issues.apache.org/jira/browse/LUCENE-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990365#comment-12990365
]
Michael McCandless commented on LUCENE-2903:
Hmm the last patch still seems t
No error reported when using a FieldCached backed ValueSource for a field Solr
knows won't work
---
Key: SOLR-2348
URL: https://issues.apache.org/jira/browse/SOLR-2348
[
https://issues.apache.org/jira/browse/SOLR-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-2339:
---
Summary: No error reported when sorting on a multiValued field (was: No
error reported when sorting on a fiel
: Despite this, I propose we do a 'casual freeze' on the 3.x code base
: in 7 days time, in other words we agree for a few weeks we will focus
: on bugs and tests only in branch_3x and try to shorten, not length the
: list of issues in JIRA (unless these issues are bugs!).
+1
Looking over the op
[
https://issues.apache.org/jira/browse/SOLR-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990378#comment-12990378
]
Hoss Man commented on SOLR-2339:
Committed revision 1067030. - trunk
Still working on the
non-contiguous LogMergePolicy should be careful to not select merges already
running
Key: LUCENE-2904
URL: https://issues.apache.org/jira/browse/LUCENE-2904
Project:
[
https://issues.apache.org/jira/browse/LUCENE-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2904:
---
Attachment: LUCENE-2904.patch
Patch.
LogMP now skips any segments that are currentl
On Thu, Feb 3, 2011 at 6:38 PM, Chris Hostetter
wrote:
>
> : Despite this, I propose we do a 'casual freeze' on the 3.x code base
> : in 7 days time, in other words we agree for a few weeks we will focus
> : on bugs and tests only in branch_3x and try to shorten, not length the
> : list of issues
[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cameron updated SOLR-236:
-
Attachment: SOLR-236-1_4_1-NPEfix.patch
Uploading SOLR-236-1_4_1-NPEfix.patch as a simple patch for the
NullPointe
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4477/
No tests ran.
Build Log (for compile errors):
[...truncated 59 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
Issue is:
Checking for files containing nocommit (exits build with failure if list is
non-empty):
./solr/src/test/org/apache/solr/BaseDistributedSearchTestCase.java
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
Apache Hudson Server schrieb:
Build: https://hudson.
[
https://issues.apache.org/jira/browse/SOLR-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-2339.
Resolution: Fixed
Committed revision 1067042.
backported to 3x
> No error reported when sorting on a multi
: Checking for files containing nocommit (exits build with failure if list is
non-empty):
: ./solr/src/test/org/apache/solr/BaseDistributedSearchTestCase.java
my bad ... on it.
-Hoss
-
To unsubscribe, e-mail: dev-unsubscr...@
[
https://issues.apache.org/jira/browse/SOLR-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-1057:
-
Attachment: SOLR-1057.patch
A new patch. To respond Ryan's requirement, I added the following test
Wrong matches count with groupped results
-
Key: SOLR-2349
URL: https://issues.apache.org/jira/browse/SOLR-2349
Project: Solr
Issue Type: Bug
Affects Versions: 4.0
Environment: windows xp,
[
https://issues.apache.org/jira/browse/LUCENE-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990439#comment-12990439
]
Robert Muir commented on LUCENE-2886:
-
We are still not using 2 of the simple64 selec
[
https://issues.apache.org/jira/browse/SOLR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990444#comment-12990444
]
Prasad Deshpande commented on SOLR-2346:
I agree, I was just trying to decode the g
[
https://issues.apache.org/jira/browse/SOLR-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990455#comment-12990455
]
Bill Bell commented on SOLR-2345:
-
Here is more info:
id=56
store=43,-96
store=42,-97.5
id
[
https://issues.apache.org/jira/browse/SOLR-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990456#comment-12990456
]
Bill Bell commented on SOLR-2155:
-
Instead of geodist() would you create a new one, or exte
[
https://issues.apache.org/jira/browse/SOLR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Deshpande updated SOLR-2346:
---
Environment: Solr 1.4.1, Packaged Jetty as servlet container, Windows XP
SP1, Machine was boot
[
https://issues.apache.org/jira/browse/SOLR-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990444#comment-12990444
]
Prasad Deshpande edited comment on SOLR-2346 at 2/4/11 5:23 AM:
-
[
https://issues.apache.org/jira/browse/SOLR-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Bell resolved SOLR-2317.
-
Resolution: Fixed
See SOLR-2156
> Slaves have leftover index.x directories, and leftover files in ind
[
https://issues.apache.org/jira/browse/SOLR-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990463#comment-12990463
]
Ryan McKinley commented on SOLR-1057:
-
I was totally unaware of CharFilters and how the
[
https://issues.apache.org/jira/browse/LUCENE-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990477#comment-12990477
]
Toke Eskildsen commented on LUCENE-2843:
Michael, I think I'll use a TermsEnum-wr
[
https://issues.apache.org/jira/browse/LUCENE-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990480#comment-12990480
]
hao yan commented on LUCENE-2903:
-
Yes. Other PFOR impls (FrameOfRef and PatchedFrameOfRe
97 matches
Mail list logo
