Build: https://hudson.apache.org/hudson/job/Solr-trunk/1389/
All tests passed
Build Log (for compile errors):
[...truncated 18778 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands,
[
https://issues.apache.org/jira/browse/LUCENE-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986281#action_12986281
]
Simon Willnauer commented on LUCENE-2868:
-
bq.Here's my take on the patch,
F**ck! I am posting a comment, the stack trace looks different!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Apache Hudson Server [mailto:hud...@hudson.apache.org]
Sent: Tuesday, January 25, 2011 9:53
[
https://issues.apache.org/jira/browse/LUCENE-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986346#action_12986346
]
Michael McCandless commented on LUCENE-2010:
bq. Do you want to fix the rest
[
https://issues.apache.org/jira/browse/LUCENE-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated LUCENE-2868:
Attachment: lucene-2868.patch
Oops, forgot to add a key file.
Seriously, the weight caching is of
Hi Paul,
This is a good question. The two methods, i.e., VSE and AFOR, are very
similar. The two methods can be considered as an extension of FOR to
make it less sensitive to outliers by adapting the encoding to the value
distribution. To achieve this, the two methods are encoding a list of
-- sorry, resending it as I don't know what happens to the layout of the
previous one
Hi Paul,
This is a good question. The two methods, i.e., VSE and AFOR, are very
similar. The two methods can be considered as an extension of FOR to
make it less sensitive to outliers by adapting the
[
https://issues.apache.org/jira/browse/LUCENE-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986364#action_12986364
]
Doron Cohen commented on LUCENE-2887:
-
I think it is correct to say that if the result
[
https://issues.apache.org/jira/browse/LUCENE-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986364#action_12986364
]
Doron Cohen edited comment on LUCENE-2887 at 1/25/11 7:49 AM:
--
[
https://issues.apache.org/jira/browse/LUCENE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-942.
-
Resolution: Not A Problem
TopDocsCollector documents that you cannot call topDocs() more than once for
[
https://issues.apache.org/jira/browse/LUCENE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir closed LUCENE-423.
--
Resolution: Fixed
Fix Version/s: 3.1
Assignee: (was: Lucene Developers)
You can
[
https://issues.apache.org/jira/browse/LUCENE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-522.
Resolution: Duplicate
This is fixed in LUCENE-2754, you can use any multitermquery in spans.
[
https://issues.apache.org/jira/browse/LUCENE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-538.
Resolution: Fixed
Fix Version/s: 3.1
This is now fixed by Mike's cleanup to MultiSearcher
[
https://issues.apache.org/jira/browse/LUCENE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera reassigned LUCENE-1250:
--
Assignee: Shai Erera
Some equals methods do not check for null argument
[
https://issues.apache.org/jira/browse/LUCENE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1250:
---
Lucene Fields: [New, Patch Available] (was: [New])
Affects Version/s: (was: 2.3.2)
[
https://issues.apache.org/jira/browse/LUCENE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-901.
Resolution: Fixed
Fix Version/s: 3.1
This one is fixed (there is a Nan/Inf check in
[
https://issues.apache.org/jira/browse/LUCENE-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-1148.
-
Resolution: Fixed
Fix Version/s: 3.1
This one is fixed by LUCENE-2754, you can just wrap
[
https://issues.apache.org/jira/browse/LUCENE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-522:
-
Fix Version/s: 3.1
SpanFuzzyQuery
--
Key: LUCENE-522
[
https://issues.apache.org/jira/browse/LUCENE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-943.
Resolution: Fixed
This one is available as CollationKeyAnalyzer/ICUCollationKeyAnalyzer
[
https://issues.apache.org/jira/browse/LUCENE-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986378#action_12986378
]
Robert Muir commented on LUCENE-1360:
-
Now that we have custom norm encoders, is this
[
https://issues.apache.org/jira/browse/LUCENE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-1250.
Resolution: Fixed
Committed revision 1063271 (3x).
Committed revision 1063272 (trunk).
Thanks
[
https://issues.apache.org/jira/browse/LUCENE-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986385#action_12986385
]
Uwe Schindler commented on LUCENE-1165:
---
This was once fixed by adding a robots.txt
[
https://issues.apache.org/jira/browse/LUCENE-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1165:
--
Component/s: (was: Javadocs)
Website
Assignee: Uwe Schindler
[
https://issues.apache.org/jira/browse/LUCENE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-83.
Resolution: Not A Problem
Assignee: (was: Lucene Developers)
I verified on both 3x and trunk,
[
https://issues.apache.org/jira/browse/LUCENE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-507.
-
Resolution: Not A Problem
Assignee: (was: Lucene Developers)
This is not a problem. First,
[
https://issues.apache.org/jira/browse/LUCENE-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-1074.
--
Resolution: Not A Problem
Searcher is removed from trunk and deprecated in 3x. Also, I see the
[
https://issues.apache.org/jira/browse/LUCENE-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986396#action_12986396
]
Uwe Schindler commented on LUCENE-1165:
---
I opened INFRA-3389.
Reduce exposure of
[
https://issues.apache.org/jira/browse/LUCENE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1391:
--
Affects Version/s: 2.9
3.0
This issue is still valid,
[
https://issues.apache.org/jira/browse/LUCENE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1391:
--
Fix Version/s: 4.0
3.1
Token type and flags values get lost when using
[
https://issues.apache.org/jira/browse/LUCENE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-1391:
-
Assignee: Uwe Schindler (was: Karl Wettin)
Token type and flags values get lost when
[
https://issues.apache.org/jira/browse/SOLR-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986402#action_12986402
]
Eric Pugh commented on SOLR-2326:
-
So I did discover one odd thing. If I don't have a
[
https://issues.apache.org/jira/browse/LUCENE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-1263.
--
Resolution: Cannot Reproduce
This problem could not be reproduced, and the person reporting it did
[
https://issues.apache.org/jira/browse/LUCENE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-487.
-
Resolution: Not A Problem
Not active since 2006 and we already have DBDirectory.
Database as a lucene
[
https://issues.apache.org/jira/browse/LUCENE-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986419#action_12986419
]
Uwe Schindler commented on LUCENE-1263:
---
The issue is definitely fixed:
- since 2.9
[
https://issues.apache.org/jira/browse/LUCENE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-856.
---
Resolution: Not A Problem
We've already made good improvements here, with stored
[
https://issues.apache.org/jira/browse/LUCENE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed LUCENE-401.
Resolution: Fixed
Assignee: (was: Lucene Developers)
Closing, because we no longer
+1 Makes sense to me.
On Jan 24, 2011, at 4:07 AM, Shai Erera wrote:
Hi
Few days ago Robert and I discussed this matter over IRC and thought it's
something we should bring forward to the list. This issue arise due to recent
index format change introduced in LUCENE-2720, and the
[
https://issues.apache.org/jira/browse/LUCENE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed LUCENE-505.
Resolution: Fixed
Fix Version/s: 2.9
Since Lucene 2.9 we search on each segment separately,
[
https://issues.apache.org/jira/browse/LUCENE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-406.
--
Resolution: Fixed
Fix Version/s: 4.0
This is resolved / is being resolved by the new
[
https://issues.apache.org/jira/browse/LUCENE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986438#action_12986438
]
Uwe Schindler commented on LUCENE-770:
--
In my opinion, this tool is not needed and
[
https://issues.apache.org/jira/browse/LUCENE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-770.
--
Resolution: Not A Problem
CfsExtractor tool
-
Key:
[
https://issues.apache.org/jira/browse/LUCENE-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-1418.
--
Resolution: Not A Problem
I don't think QP should support 'null' passed as the default field, and I
[
https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986442#action_12986442
]
Grant Ingersoll commented on LUCENE-2878:
-
I haven't looked at the patch, but one
[
https://issues.apache.org/jira/browse/LUCENE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed LUCENE-663.
Resolution: Fixed
Fix Version/s: 2.9
Since Lucene 2.9 we have FastVectorHighlighter which
Several DocsEnum / DocsAndPositionsEnum return wrong docID when next() /
advance(int) return NO_MORE_DOCS
-
Key: LUCENE-2888
URL:
[
https://issues.apache.org/jira/browse/LUCENE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-753.
--
Resolution: Fixed
This issue was resolved a long time ago, but left open for the stupid
[
https://issues.apache.org/jira/browse/LUCENE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-72.
Resolution: Won't Fix
Assignee: (was: Lucene Developers)
As per the discussion, this should have
[
https://issues.apache.org/jira/browse/LUCENE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2888:
Attachment: LUCENE-2888.patch
here is a patch including the ported testcase from
[
https://issues.apache.org/jira/browse/SOLR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned SOLR-445:
Assignee: Grant Ingersoll (was: Erick Erickson)
XmlUpdateRequestHandler bad documents mid
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-855.
-
Resolution: Duplicate
We already have FieldCacheRangeFilter (introduced in LUCENE-1461), so closing
as
[
https://issues.apache.org/jira/browse/LUCENE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-320.
-
Resolution: Not A Problem
Assignee: (was: Lucene Developers)
This API is already public, so I
[
https://issues.apache.org/jira/browse/LUCENE-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-988.
-
Resolution: Not A Problem
Closing because I'm not sure what's the license level of The Pirate Bay DB
[
https://issues.apache.org/jira/browse/LUCENE-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986457#action_12986457
]
Simon Willnauer commented on LUCENE-2878:
-
{quote}
I haven't looked at the patch,
[
https://issues.apache.org/jira/browse/LUCENE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-666.
--
Resolution: Not A Problem
This is not a problem of QueryParser, its more a problem of the
[
https://issues.apache.org/jira/browse/LUCENE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-666:
-
Comment: was deleted
(was: This is not a problem of QueryParser, its more a problem of the
[
https://issues.apache.org/jira/browse/LUCENE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-666:
--
Sorry, misunderstood the issue!
TERM1 OR NOT TERM2 does not perform as expected
[
https://issues.apache.org/jira/browse/LUCENE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986465#action_12986465
]
Andre Schild commented on LUCENE-547:
-
The reason for this implementation is the
[
https://issues.apache.org/jira/browse/LUCENE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-1155.
--
Resolution: Won't Fix
We don't have BoostingTermQuery anymore, and there was never consensus here to
[
https://issues.apache.org/jira/browse/LUCENE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986471#action_12986471
]
Shai Erera commented on LUCENE-547:
---
If you don't have a server, where does the Directory
[
https://issues.apache.org/jira/browse/LUCENE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2888:
Attachment: LUCENE-2888.patch
there was a wrong assignment in the last patch... I will go
[
https://issues.apache.org/jira/browse/LUCENE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed LUCENE-798.
Resolution: Not A Problem
This patch does not apply anymore, as Filters no longer use BitSets, but
[
https://issues.apache.org/jira/browse/LUCENE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-2888.
-
Resolution: Fixed
Committed revision 1063332.
Several DocsEnum /
[
https://issues.apache.org/jira/browse/SOLR-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-482:
-
Attachment: SOLR-482.patch
Working through some old patches, this one is pretty tame and gives a
[
https://issues.apache.org/jira/browse/LUCENE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-218.
-
Resolution: Not A Problem
Assignee: (was: Lucene Developers)
Note that the query has OR FIVE
[
https://issues.apache.org/jira/browse/LUCENE-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-1159.
--
Resolution: Not A Problem
This seems to be fixed already. From common-build.xml:
{noformat}
!-- If
[
https://issues.apache.org/jira/browse/LUCENE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986490#action_12986490
]
Andre Schild commented on LUCENE-547:
-
The problem with RAMDirectory is, that it uses
[
https://issues.apache.org/jira/browse/LUCENE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-149.
-
Resolution: Not A Problem
Assignee: (was: Lucene Developers)
This looks more like a tool to
[
https://issues.apache.org/jira/browse/LUCENE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-150.
-
Resolution: Not A Problem
Assignee: (was: Lucene Developers)
We have DBDirectory in contrib.
[
https://issues.apache.org/jira/browse/LUCENE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera closed LUCENE-151.
-
Resolution: Not A Problem
Assignee: (was: Lucene Developers)
RAMDirectory has a ctor which
[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986502#action_12986502
]
Yonik Seeley commented on LUCENE-2883:
--
One issue here is the different purposes for
[
https://issues.apache.org/jira/browse/LUCENE-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-1188.
---
Resolution: Fixed
Fix Version/s: 2.9
The equals and hashCode implementations in
[
https://issues.apache.org/jira/browse/SOLR-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-2320.
Resolution: Fixed
Committed revision 1063339. - trunk
Committed revision 1063343. - 3x
[
https://issues.apache.org/jira/browse/SOLR-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986514#action_12986514
]
Jayendra Patil commented on SOLR-2317:
--
For the extra index. you can try the patch
[
https://issues.apache.org/jira/browse/SOLR-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-482.
--
Resolution: Fixed
Fix Version/s: 4.0
3.1
committed on trunk and 3.x
[
https://issues.apache.org/jira/browse/LUCENE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2723:
Attachment: LUCENE-2723-BulkEnumWrapper.patch
This patch adds a BulkPostingsEnumWrapper
[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986529#action_12986529
]
Simon Willnauer commented on LUCENE-2883:
-
bq. One issue here is the different
[
https://issues.apache.org/jira/browse/LUCENE-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2392:
Attachment: LUCENE-2392_take2.patch
here's a really really rough take 2 at the problem.
The
[
https://issues.apache.org/jira/browse/LUCENE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986542#action_12986542
]
Uwe Schindler commented on LUCENE-403:
--
Mark Miller: What do you think, is this issue
[
https://issues.apache.org/jira/browse/LUCENE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986544#action_12986544
]
Mark Miller commented on LUCENE-403:
Yeah - I would totally close this. This work has
[
https://issues.apache.org/jira/browse/LUCENE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-403.
Resolution: Won't Fix
Assignee: Mark Miller
Some of this work moved into other issues. Some
[
https://issues.apache.org/jira/browse/LUCENE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller closed LUCENE-403.
--
Alternate Lucene Query Highlighter
--
Key: LUCENE-403
[
https://issues.apache.org/jira/browse/LUCENE-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler closed LUCENE-990.
Resolution: Won't Fix
ParallelMultiSearcher was dropped with MultiSearcher in Lucene trunk
[
https://issues.apache.org/jira/browse/LUCENE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-1264.
---
Resolution: Won't Fix
This issue is quite old and no response was given to Hoss' comment.
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986556#action_12986556
]
Jason Rutherglen commented on LUCENE-2324:
--
The compilation errors are gone,
[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986558#action_12986558
]
Michael McCandless commented on LUCENE-2883:
Can't we consolidate them under a
[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986561#action_12986561
]
Yonik Seeley commented on LUCENE-2883:
--
Not sure if I communicated the issue clearly:
[
https://issues.apache.org/jira/browse/LUCENE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986566#action_12986566
]
Michael McCandless commented on LUCENE-2666:
Hmmm --- given that exception, I
[
https://issues.apache.org/jira/browse/LUCENE-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986568#action_12986568
]
Robert Muir commented on LUCENE-2723:
-
Simon, just took a quick glance (not a serious
[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986569#action_12986569
]
Robert Muir commented on LUCENE-2883:
-
Wait, why again did we merge lucene and solr?
[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986571#action_12986571
]
Yonik Seeley commented on LUCENE-2883:
--
bq. We can mark the classes as
[
https://issues.apache.org/jira/browse/SOLR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986581#action_12986581
]
Grant Ingersoll commented on SOLR-445:
--
This patch looks pretty reasonable from the
[
https://issues.apache.org/jira/browse/SOLR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986584#action_12986584
]
Grant Ingersoll commented on SOLR-445:
--
Oh, one other thing. You don't need to produce
[
https://issues.apache.org/jira/browse/SOLR-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-2171.
---
Resolution: Duplicate
See SOLR-1298
Using stats feature over a function, Function returning
[
https://issues.apache.org/jira/browse/LUCENE-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2010.
Resolution: Fixed
Remove segments with all documents deleted in
[
https://issues.apache.org/jira/browse/SOLR-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved SOLR-2177.
---
Resolution: Fixed
Add More Facet demonstrations to the /browse example
[
https://issues.apache.org/jira/browse/LUCENE-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll closed LUCENE-805.
--
Resolution: Won't Fix
New Lucene Demo
---
Key: LUCENE-805
Hi everyone,
There's a fair bit of info on the internet about this, apparently
gmail groups by subject only and JIRA includes varying content in an
issue's subject, depending on the action (comment, update, etc.). Did
anybody find a solution to thread ALL of an issue's messages into a
single
This is an awful problem!
I made a Python script to workaround this... it's kinda scary: it logs
in (over IMAP), finds the messages, removes the old ones, and puts
back new ones with the corrected subject line so that gmail groups
them properly. If you want I can send the Python script... but
[
https://issues.apache.org/jira/browse/LUCENE-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986630#action_12986630
]
Michael McCandless commented on LUCENE-1574:
I've been testing on a 25M doc
1 - 100 of 133 matches
Mail list logo
