[
https://issues.apache.org/jira/browse/SOLR-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-2654:
--
Fix Version/s: 4.0
> not used consistently in all places Directory objects are
> instantiated
> --
[
https://issues.apache.org/jira/browse/SOLR-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080532#comment-13080532
]
Mark Miller commented on SOLR-2654:
---
My initial suspicion is actually that these where bu
[
https://issues.apache.org/jira/browse/SOLR-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-2654:
--
Attachment: SOLR-2654.patch
So with this patch, tests pass for me - but it scares me because I had to
c
[
https://issues.apache.org/jira/browse/SOLR-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080525#comment-13080525
]
Mark Miller commented on SOLR-2654:
---
Hmmm...the problem has something to do with this new
[
https://issues.apache.org/jira/browse/LUCENE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080480#comment-13080480
]
Yonik Seeley commented on LUCENE-2748:
--
bq. I'm more or less copying the layout of M
[
https://issues.apache.org/jira/browse/SOLR-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080474#comment-13080474
]
Eks Dev commented on SOLR-2701:
---
one hook for users to update content of this map would be to
[
https://issues.apache.org/jira/browse/LUCENE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080471#comment-13080471
]
Grant Ingersoll commented on LUCENE-2748:
-
If you wish to build/test locally, do
[
https://issues.apache.org/jira/browse/LUCENE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080463#comment-13080463
]
Grant Ingersoll commented on LUCENE-2748:
-
Making some progress on this. Here's
Expose IndexWriter.commit(Map commitUserData) to solr
-
Key: SOLR-2701
URL: https://issues.apache.org/jira/browse/SOLR-2701
Project: Solr
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LUCENE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Stancapiano updated LUCENE-3167:
-
Attachment: lucene_trunk.patch
I send a new patch.
- reorganized with the new update of
On Sat, Aug 6, 2011 at 4:17 PM, eks dev wrote:
> Thanks Yonik,
> assuming I am not going to index ID , than only an option 4. remains so far.
> I have no other ideas, and Log* merge policy would mean all 4 Indexing magic
> went to nothing :)
> Colud then the following do the job?
> clone DefaultIn
Thanks Yonik,
assuming I am not going to index ID , than only an option 4. remains so far. I
have no other ideas, and Log* merge policy would mean all 4 Indexing magic went
to nothing :)
Colud then the following do the job?
clone DefaultIndexWriterProvider into my codebase (ugly, keep in sync
On Sat, Aug 6, 2011 at 2:47 PM, eks dev wrote:
> Assuming there are no deletes, would the following work as a way to load
> *last added document*, surviving optimize as well?
> Order of documentId-s in Lucene survives optimize as far as I remember?
No longer... the default merge policy can now m
Assuming there are no deletes, would the following work as a way to load *last
added document*, surviving optimize as well?
Order of documentId-s in Lucene survives optimize as far as I remember?
IndexReader ir...
int maxDoc = ir.maxDoc() - 1;
if(maxDoc>0) //? What is the return value on empty
[
https://issues.apache.org/jira/browse/LUCENE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080442#comment-13080442
]
Yonik Seeley commented on LUCENE-3364:
--
Ah, gotcha - I see what you're saying now.
[
https://issues.apache.org/jira/browse/LUCENE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080439#comment-13080439
]
John Wang commented on LUCENE-3364:
---
Hi Yonik:
In Collector, the decision time to c
[
https://issues.apache.org/jira/browse/LUCENE-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080437#comment-13080437
]
Yonik Seeley commented on LUCENE-3364:
--
Perhaps it would be easiest to just create a
Add score threshold into Scorer.score()
---
Key: LUCENE-3364
URL: https://issues.apache.org/jira/browse/LUCENE-3364
Project: Lucene - Java
Issue Type: Improvement
Components: core/query/scoring
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x/10036/
2 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.MergeIndexesEmbeddedTest.testMergeIndexesByDirName
Error Message:
No such core: core1
Stack Trace:
org.apache.solr.common.SolrException: No such core: core1
[
https://issues.apache.org/jira/browse/SOLR-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-2700:
---
Attachment: SOLR-2700.patch
Here's a draft patch.
There is a tlog. file created for each commit. The
transaction logging
---
Key: SOLR-2700
URL: https://issues.apache.org/jira/browse/SOLR-2700
Project: Solr
Issue Type: New Feature
Reporter: Yonik Seeley
A transaction log is needed for durability of updates, for
[
https://issues.apache.org/jira/browse/LUCENE-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080416#comment-13080416
]
David Mark Nemeskey edited comment on LUCENE-3357 at 8/6/11 3:52 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Mark Nemeskey updated LUCENE-3357:
Attachment: LUCENE-3357.patch
Integration tests added. There are two of them; howe
[
https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikola Tankovic updated LUCENE-2308:
Attachment: LUCENE-2308-21.patch
21th patch :) Fixed Javadocs errors.
> Separately specif
The facet result for field productType will show the following count:
BOOK: 1
DVD: 0
So yes, because of post group faceting you'll miss the second facet.
This is basically the same example I described in LUCENE-3097.
I've also described three ways of calculating facet counts in combination
groupi
[
https://issues.apache.org/jira/browse/LUCENE-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Mark Nemeskey updated LUCENE-3220:
Attachment: LUCENE-3220.patch
Added a short explanation on the parameter for the J
[
https://issues.apache.org/jira/browse/LUCENE-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Mark Nemeskey updated LUCENE-3220:
Attachment: LUCENE-3220.patch
Done. Actually, I wanted to implement the norm table
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/10015/
1 tests failed.
REGRESSION: org.apache.solr.core.TestJmxIntegration.testJmxOnCoreReload
Error Message:
Number of registered MBeans is not the same as info registry size expected:<51>
but was:<45>
Stack Trace:
junit.framew
28 matches
Mail list logo
