Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #335

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Updated] (SOLR-3497) Make HTTP error default for exceptions

[ https://issues.apache.org/jira/browse/SOLR-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lance Norskog updated SOLR-3497: Component/s: search > Make HTTP error default for exceptions > -

[jira] [Created] (SOLR-3497) Make HTTP error default for exceptions

Lance Norskog created SOLR-3497: --- Summary: Make HTTP error default for exceptions Key: SOLR-3497 URL: https://issues.apache.org/jira/browse/SOLR-3497 Project: Solr Issue Type: Improvement

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java7-64 #190

See -- [...truncated 11549 lines...] [junit4] 2> 789109 T3428 oasc.RequestHandlers.initHandlersFromConfig created standard: solr.StandardRequestHandler [junit4] 2> 7

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #334

See -- [...truncated 13497 lines...] [junit4] 2> 35266 T2811 oasc.RequestHandlers.initHandlersFromConfig adding lazy requestHandler: solr.StandardRequestHandler [junit

[jira] [Updated] (LUCENE-4096) impossible to CheckIndex if you use norms other than byte[]

[ https://issues.apache.org/jira/browse/LUCENE-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-4096: Attachment: LUCENE-4096.patch Patch: re-enabling checkindex for TestCustomNorms, enabling SimpleTe

[jira] [Created] (LUCENE-4096) impossible to CheckIndex if you use norms other than byte[]

Robert Muir created LUCENE-4096: --- Summary: impossible to CheckIndex if you use norms other than byte[] Key: LUCENE-4096 URL: https://issues.apache.org/jira/browse/LUCENE-4096 Project: Lucene - Java

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #333

See Changes: [rmuir] LUCENE-4095: remove deprecations from trunk (just the easy ones for now) -- [...truncated 13755 lines...] [junit4] [junit4] Suite: org.apa

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #332

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (LUCENE-4095) remove deprecations from trunk

[ https://issues.apache.org/jira/browse/LUCENE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286266#comment-13286266 ] Robert Muir commented on LUCENE-4095: - Committed to trunk. now backporting tests and

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #331

See -- [...truncated 16452 lines...] [junit4] 2> 26845 T3202 oass.SolrIndexSearcher. Opening Searcher@717a9137 main [junit4] 2> 26846 T3202 oass.SolrIndexSearcher. W

[jira] [Commented] (LUCENE-3842) Analyzing Suggester

[ https://issues.apache.org/jira/browse/LUCENE-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286249#comment-13286249 ] Sudarshan Gaikaiwari commented on LUCENE-3842: -- Hi Michael, Thanks a lot fo

[jira] [Assigned] (LUCENE-4091) FastVectorHighlighter: Getter for FieldFragList.WeightedFragInfo and FieldPhraseList.WeightedPhraseInfo

[ https://issues.apache.org/jira/browse/LUCENE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi reassigned LUCENE-4091: -- Assignee: Koji Sekiguchi > FastVectorHighlighter: Getter for FieldFragList.Weighte

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #329

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Updated] (SOLR-3473) Distributed deduplication broken

[ https://issues.apache.org/jira/browse/SOLR-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-3473: --- Attachment: SOLR-3473.patch Updated patch to include my (meager) attempt at fixing the problem by making proc

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #328

See Changes: [dweiss] Minor cleanups of LuceneTestCase and reproduce string builder. -- [...truncated 13642 lines...] [junit4] 2> 41023 T2892 oasc.SolrCore.close

[jira] [Updated] (LUCENE-4095) remove deprecations from trunk

[ https://issues.apache.org/jira/browse/LUCENE-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-4095: Attachment: LUCENE-4095.patch Patch taking care of the majority (but not all!) of the deprecations

[jira] [Created] (LUCENE-4095) remove deprecations from trunk

Robert Muir created LUCENE-4095: --- Summary: remove deprecations from trunk Key: LUCENE-4095 URL: https://issues.apache.org/jira/browse/LUCENE-4095 Project: Lucene - Java Issue Type: Task Aff

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286116#comment-13286116 ] Steven Rowe commented on LUCENE-4092: - {quote} Is there also a way we could improve t

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286106#comment-13286106 ] Steven Rowe commented on LUCENE-4092: - This one seems to work (from Perl against a re

[jira] [Updated] (SOLR-2993) Integrate WordBreakSpellChecker with Solr

[ https://issues.apache.org/jira/browse/SOLR-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer updated SOLR-2993: - Attachment: SOLR-2993.patch New patch. Clean things up, fix bugs, etc. This is getting close...

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286088#comment-13286088 ] Robert Muir commented on LUCENE-4092: - By the way: I'm not suggesting to make the reg

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286086#comment-13286086 ] Robert Muir commented on LUCENE-4092: - Is there also a way we could improve the outpu

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286078#comment-13286078 ] Dawid Weiss commented on LUCENE-4092: - This will be a killer regexp, I can feel it ;)

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286075#comment-13286075 ] Steven Rowe commented on LUCENE-4092: - bq. regex="(?s:\\[java4\\]\\s*Suite:.*?<<<\\s*

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286064#comment-13286064 ] Steven Rowe commented on LUCENE-4092: - I'll switch it to the following - hopefully it

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286042#comment-13286042 ] Dawid Weiss commented on LUCENE-4092: - Ok, so BUILD_LOG_REGEX should do! I don't know

Re: reindex trunk indexes

yes On Wed, May 30, 2012 at 4:44 PM, Jack Krupansky wrote: > That commit was for the "4x" branch as well as "trunk", right? > > -- Jack Krupansky > > -Original Message- From: Robert Muir Sent: Wednesday, May 30, 2012 > 4:32 PM To: dev@lucene.apache.org Subject: reindex trunk indexes > I j

[jira] [Commented] (LUCENE-4094) Randomize file.encoding

[ https://issues.apache.org/jira/browse/LUCENE-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286036#comment-13286036 ] Dawid Weiss commented on LUCENE-4094: - junit4 is already default encoding independent

[jira] [Commented] (LUCENE-4094) Randomize file.encoding

[ https://issues.apache.org/jira/browse/LUCENE-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286028#comment-13286028 ] Robert Muir commented on LUCENE-4094: - This would be really nice. The limitation befo

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286026#comment-13286026 ] Steven Rowe commented on LUCENE-4092: - bq. Yeah, but what is $\{FAILED_TESTS}? I mean

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14456 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14456/ All tests passed Build Log (for compile errors): [...truncated 24327 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

Re: reindex trunk indexes

That commit was for the "4x" branch as well as "trunk", right? -- Jack Krupansky -Original Message- From: Robert Muir Sent: Wednesday, May 30, 2012 4:32 PM To: dev@lucene.apache.org Subject: reindex trunk indexes I just committed LUCENE-4090, you should reindex any trunk indexes.

[jira] [Created] (LUCENE-4094) Randomize file.encoding

Dawid Weiss created LUCENE-4094: --- Summary: Randomize file.encoding Key: LUCENE-4094 URL: https://issues.apache.org/jira/browse/LUCENE-4094 Project: Lucene - Java Issue Type: Sub-task

[jira] [Created] (LUCENE-4093) Implement better equals() on PostingsFormats where possible

Robert Muir created LUCENE-4093: --- Summary: Implement better equals() on PostingsFormats where possible Key: LUCENE-4093 URL: https://issues.apache.org/jira/browse/LUCENE-4093 Project: Lucene - Java

[jira] [Resolved] (LUCENE-4090) PerFieldPostingsFormat cannot use name as suffix

[ https://issues.apache.org/jira/browse/LUCENE-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir resolved LUCENE-4090. - Resolution: Fixed Fix Version/s: 5.0 4.0 Thanks for bringing this up M

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285991#comment-13285991 ] Dawid Weiss commented on LUCENE-4092: - Yeah, but what is ${FAILED_TESTS}? I mean -- c

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #326

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Commented] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

[ https://issues.apache.org/jira/browse/LUCENE-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285981#comment-13285981 ] Steven Rowe commented on LUCENE-4092: - *Editable Email Notification*/*Default Content

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14455 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14455/ All tests passed Build Log (for compile errors): [...truncated 24335 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[jira] [Created] (LUCENE-4092) Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures).

Dawid Weiss created LUCENE-4092: --- Summary: Check what's Jenkins pattern for e-mailing log fragments (so that it includes failures). Key: LUCENE-4092 URL: https://issues.apache.org/jira/browse/LUCENE-4092

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #325

See Changes: [jdyer] LUCENE-3523: Javadoc fix [rmuir] fix lucenetestcase to report the actual codec used instead of always lucene40 when a test fails -- [...truncat

[jira] [Commented] (LUCENE-4083) RateLimited.pause() throws unchecked exception

[ https://issues.apache.org/jira/browse/LUCENE-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285930#comment-13285930 ] Dawid Weiss commented on LUCENE-4083: - bq. I agree: I think in general whoever does t

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14454 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14454/ 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.handler.TestReplicationHandler Error Message: ERROR: SolrIndexSearcher opens=74 closes=73 Stack Trace: java.lang.AssertionError: ERROR: SolrIndexSearcher o

[jira] [Updated] (LUCENE-4090) PerFieldPostingsFormat cannot use name as suffix

[ https://issues.apache.org/jira/browse/LUCENE-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-4090: Attachment: LUCENE-4090.patch updated patch. I beefed up randomcodec to add Memory(false) and Memo

[jira] [Commented] (LUCENE-4090) PerFieldPostingsFormat cannot use name as suffix

[ https://issues.apache.org/jira/browse/LUCENE-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285913#comment-13285913 ] Robert Muir commented on LUCENE-4090: - Patch is still buggy, new one coming. My test

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14453 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14453/ All tests passed Build Log (for compile errors): [...truncated 24329 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14452 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14452/ All tests passed Build Log (for compile errors): [...truncated 24335 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

RE: Metro port of Lucene.net

If you look at MSDN, the new WinRT (Windows Runtime) is designated "Metro style apps". There are indeed significant changes. Most of it relates to the asynchronous nature of the runtime and the sandboxed IO libraries. I understand that a wrapper has been written for SQLite, so it's possible. I don

[JENKINS] Lucene-Solr-tests-only-trunk-java7 - Build # 2711 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2711/ All tests passed Build Log (for compile errors): [...truncated 20613 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For addit

[jira] [Commented] (LUCENE-4090) PerFieldPostingsFormat cannot use name as suffix

[ https://issues.apache.org/jira/browse/LUCENE-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285832#comment-13285832 ] Michael McCandless commented on LUCENE-4090: Patch looks good! Nice having t

[jira] [Updated] (LUCENE-4090) PerFieldPostingsFormat cannot use name as suffix

[ https://issues.apache.org/jira/browse/LUCENE-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-4090: Attachment: LUCENE-4090.patch attached is a patch for trunk. tests pass (obviously TestBackCompat

[jira] [Updated] (LUCENE-4077) ToParentBlockJoinCollector provides no way to access computed scores and the maxScore

[ https://issues.apache.org/jira/browse/LUCENE-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-4077: --- Attachment: LUCENE-4077.patch New patch, using the collector's maxScore in TPBJC.get

[JENKINS] Lucene-Solr-tests-only-trunk - Build # 14451 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14451/ All tests passed Build Log (for compile errors): [...truncated 19647 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[jira] [Commented] (LUCENE-4083) RateLimited.pause() throws unchecked exception

[ https://issues.apache.org/jira/browse/LUCENE-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285799#comment-13285799 ] Michael McCandless commented on LUCENE-4083: bq. Still, I think this exceptio

[jira] [Commented] (LUCENE-4077) ToParentBlockJoinCollector provides no way to access computed scores and the maxScore

[ https://issues.apache.org/jira/browse/LUCENE-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285797#comment-13285797 ] Michael McCandless commented on LUCENE-4077: bq. Otherwise, topGroups.maxScor

[jira] [Assigned] (LUCENE-3523) WordBreakSpellChecker

[ https://issues.apache.org/jira/browse/LUCENE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer reassigned LUCENE-3523: -- Assignee: James Dyer It works. Thanks, Steven! > WordBreakSpellChecker > ---

[jira] [Commented] (LUCENE-3440) FastVectorHighlighter: IDF-weighted terms for ordered fragments

[ https://issues.apache.org/jira/browse/LUCENE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285787#comment-13285787 ] sebastian L. commented on LUCENE-3440: -- Hi Koji, bq. This is a great idea and it h

[jira] [Commented] (LUCENE-3523) WordBreakSpellChecker

[ https://issues.apache.org/jira/browse/LUCENE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285786#comment-13285786 ] Steven Rowe commented on LUCENE-3523: - bq. I do not seem to have the ability to re-as

[jira] [Updated] (LUCENE-4091) FastVectorHighlighter: Getter for FieldFragList.WeightedFragInfo and FieldPhraseList.WeightedPhraseInfo

[ https://issues.apache.org/jira/browse/LUCENE-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastian L. updated LUCENE-4091: - Attachment: LUCENE-4091.patch > FastVectorHighlighter: Getter for FieldFragList.WeightedFrag

[jira] [Created] (LUCENE-4091) FastVectorHighlighter: Getter for FieldFragList.WeightedFragInfo and FieldPhraseList.WeightedPhraseInfo

sebastian L. created LUCENE-4091: Summary: FastVectorHighlighter: Getter for FieldFragList.WeightedFragInfo and FieldPhraseList.WeightedPhraseInfo Key: LUCENE-4091 URL: https://issues.apache.org/jira/browse/LUCENE

[jira] [Resolved] (LUCENE-3523) WordBreakSpellChecker

[ https://issues.apache.org/jira/browse/LUCENE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer resolved LUCENE-3523. Resolution: Fixed committed: Trunk, r1344320 Branch_4x: r1344329 I do not seem to have the abil

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285773#comment-13285773 ] Mark Harwood commented on LUCENE-4069: -- bq. When I run all tests with the bloom 4.0

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285768#comment-13285768 ] Robert Muir commented on LUCENE-4069: - Right, its not bad. Separately I'm not happy t

Documenting document limits for Lucene and Solr

AFAICT, there is no clear documentation of the maximum number of documents that can be stored in a Lucene or Solr Index (single core/shard). It appears to be 2^31 since a Lucene document number and the value returned from IW.maxDoc is a Java “int”. Lucene users have that “hint” to guide them, bu

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285765#comment-13285765 ] Mark Harwood commented on LUCENE-4069: -- bq. its just an issue with PerFieldPostingsF

[jira] [Created] (LUCENENET-492) Investigate Improvements to Sharpen for 4.0 conversion

Prescott Nasser created LUCENENET-492: - Summary: Investigate Improvements to Sharpen for 4.0 conversion Key: LUCENENET-492 URL: https://issues.apache.org/jira/browse/LUCENENET-492 Project: Lucene.N

Re: [jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

On Wed, May 30, 2012 at 11:43 AM, Andrzej Bialecki wrote: > On 30/05/2012 17:09, Robert Muir (JIRA) wrote: >> >> I'm not sure this is true: e.g. if your postings format requires >> parameters to decode the segment, then this enforces that it records said >> parameters, >> e.g. Pulsing records thes

[jira] [Resolved] (LUCENENET-489) New spatial module

[ https://issues.apache.org/jira/browse/LUCENENET-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prescott Nasser resolved LUCENENET-489. --- Resolution: Fixed > New spatial module > -- > >

[jira] [Closed] (LUCENENET-489) New spatial module

[ https://issues.apache.org/jira/browse/LUCENENET-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prescott Nasser closed LUCENENET-489. - > New spatial module > -- > > Key: LUCENENET-489 >

[jira] [Closed] (LUCENENET-462) Spatial Search skipping records with small radius e.g. 1 mile

[ https://issues.apache.org/jira/browse/LUCENENET-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prescott Nasser closed LUCENENET-462. - > Spatial Search skipping records with small radius e.g. 1 mile >

[jira] [Resolved] (LUCENENET-462) Spatial Search skipping records with small radius e.g. 1 mile

[ https://issues.apache.org/jira/browse/LUCENENET-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prescott Nasser resolved LUCENENET-462. --- Resolution: Fixed Assignee: Itamar Syn-Hershko Resolved with the new module

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285757#comment-13285757 ] Robert Muir commented on LUCENE-4069: - Mark: I opened LUCENE-4090.. I broke it, so I'

Re: [jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

On 30/05/2012 17:09, Robert Muir (JIRA) wrote: I'm not sure this is true: e.g. if your postings format requires parameters to decode the segment, then this enforces that it records said parameters, e.g. Pulsing records these parameters. Codec parameters are at index-time, at read-time its your

[jira] [Created] (LUCENE-4090) PerFieldPostingsFormat cannot use name as suffix

Robert Muir created LUCENE-4090: --- Summary: PerFieldPostingsFormat cannot use name as suffix Key: LUCENE-4090 URL: https://issues.apache.org/jira/browse/LUCENE-4090 Project: Lucene - Java Issue

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285745#comment-13285745 ] Robert Muir commented on LUCENE-4069: - As far as your problem with parameters, this i

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285744#comment-13285744 ] Mark Harwood commented on LUCENE-4069: -- This fails if you add docs with title and te

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285746#comment-13285746 ] Michael McCandless commented on LUCENE-4069: When I run all tests with the bl

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285726#comment-13285726 ] Robert Muir commented on LUCENE-4069: - I'm not sure this is true: e.g. if your postin

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync

Thanks... I missed that one! On Wed, May 30, 2012 at 10:49 AM, Steven A Rowe wrote: > I just committed a fix: it was a version property in build.xml > > -Original Message- > From: Robert Muir [mailto:rcm...@gmail.com] > Sent: Wednesday, May 30, 2012 10:48 AM > To: dev@lucene.apache.org >

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync

Maven uses major.minor.bugfix format for versioning. I don't think it can be changed. Dawid On Wed, May 30, 2012 at 4:47 PM, Robert Muir wrote: > I figured this would happen. I saw quite a few places that are "4.0.0" > in the maven files, but it wasnt obvious to me which one was the one i > shou

RE: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync

I just committed a fix: it was a version property in build.xml -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Wednesday, May 30, 2012 10:48 AM To: dev@lucene.apache.org Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync I figured this would

Re: Contribute 4.0 NRT source

David: There is no commit with this approach, hence no closing of the SolrIndexSearcher object. Regarding the cache invalidation, there are some thoughts on selective dynamic update nothing has been implemented yet. The desired cache is disabled for now depending on the search needs. Regard

Re: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync

I figured this would happen. I saw quite a few places that are "4.0.0" in the maven files, but it wasnt obvious to me which one was the one i should change. I think this is because maven internally has "4.0.0" as the version of some files. Does anyone know? I think we should add an xml comment ab

Re: wiki software

https://issues.apache.org/jira/browse/INFRA-4864 On May 19, 2012, at 5:55 PM, Ryan McKinley wrote: > A *long* time ago we discussed converting to confluence to replace the > forest site. The key issue was that only commiters could have access > if we want to include the generated PDF in the dist

[jira] [Commented] (LUCENE-4069) Segment-level Bloom filters for a 2 x speed up on rare term searches

[ https://issues.apache.org/jira/browse/LUCENE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285706#comment-13285706 ] Mark Harwood commented on LUCENE-4069: -- Aaaargh. Unless I've missed something, I hav

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java6-64 #321

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: wiki software

On May 23, 2012, at 7:57 PM, Jan Høydahl wrote: > Agree with Grant that we need a better, more structured documentation set, > per version. > But let's first do what Ryan suggests - switch to Confluence - put all > converted MoinMoin pages in a separate legacy section of the Wiki. > > Then in

[jira] [Commented] (LUCENE-4077) ToParentBlockJoinCollector provides no way to access computed scores and the maxScore

[ https://issues.apache.org/jira/browse/LUCENE-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285702#comment-13285702 ] Christoph Kaser commented on LUCENE-4077: - Hi Mike, shouldn't TopGroups.maxScore

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #504: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/504/ 1 tests failed. REGRESSION: org.apache.lucene.index.TestCheckIndex.testLuceneConstantVersion Error Message: Invalid version: 4.0-SNAPSHOT Stack Trace: java.lang.AssertionError: Invalid version: 4.0-SNAPSHOT at __randomiz

[jira] [Commented] (SOLR-3178) Versioning - optimistic locking

[ https://issues.apache.org/jira/browse/SOLR-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285695#comment-13285695 ] Yonik Seeley commented on SOLR-3178: I had missed this last update during the crazy wee

Re: Contribute 4.0 NRT source

Nagendra, Simply open a JIRA issue and attach a patch. Lucene/Solr development largely centers around JIRA issues via the comments. Ideally you should provide tests as part of your patch; it certainly won't be committed if sufficient tests are never furnished. If your NRT implementation really

Contribute 4.0 NRT source

Hi! I would like to contribute a more granular NRT implementation as to soft-commit (enabled with the realtime tag). This does not close the SolrIndexSearcher instances but keeps passing the NRT reader as a parameter to the searcher maintaining the searcher paradigm of being lean and stateles

Build failed in Jenkins: Lucene-Solr-trunk-Windows-Java6-64 #320

See -- [...truncated 13237 lines...] [junit4] 2> 46564 T2761 C172 REQ [collection1] webapp=/solr path=/select params={wt=javabin&q=*:*&version=2} hits=497 status=0 QTime=

[jira] [Commented] (LUCENE-4082) Implement explain in ToParentBlockJoinQuery$BlockJoinWeight

[ https://issues.apache.org/jira/browse/LUCENE-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285654#comment-13285654 ] Christoph Kaser commented on LUCENE-4082: - Thank you, works perfectly!

Re: svn commit: r1344101 - in /lucene/dev/branches/lucene_solr_3_6/lucene/contrib: ./ analyzers/common/src/java/org/apache/lucene/analysis/hunspell/ analyzers/common/src/test/org/apache/lucene/analysi

Yup, done. On Thu, May 31, 2012 at 1:15 AM, Robert Muir wrote: > i didnt even look at the issue at all, i just noticed it has "New > Features" in changes.txt > > I think this is confusing: can we fix CHANGES if its really a bugfix > to be under "Bugfixes"? > > On Wed, May 30, 2012 at 9:10 AM, Ch

Re: svn commit: r1344101 - in /lucene/dev/branches/lucene_solr_3_6/lucene/contrib: ./ analyzers/common/src/java/org/apache/lucene/analysis/hunspell/ analyzers/common/src/test/org/apache/lucene/analysi

i didnt even look at the issue at all, i just noticed it has "New Features" in changes.txt I think this is confusing: can we fix CHANGES if its really a bugfix to be under "Bugfixes"? On Wed, May 30, 2012 at 9:10 AM, Chris Male wrote: > With that in mind, I shouldnt put it under New features. >

Re: svn commit: r1344101 - in /lucene/dev/branches/lucene_solr_3_6/lucene/contrib: ./ analyzers/common/src/java/org/apache/lucene/analysis/hunspell/ analyzers/common/src/test/org/apache/lucene/analysi

With that in mind, I shouldnt put it under New features. On Thu, May 31, 2012 at 1:03 AM, Chris Male wrote: > I would argue it is a bug fix, it fixes the handling of a certain kind of > dictionary. > > > On Thu, May 31, 2012 at 12:55 AM, Robert Muir wrote: > >> why are we backporting new featur

Re: svn commit: r1344101 - in /lucene/dev/branches/lucene_solr_3_6/lucene/contrib: ./ analyzers/common/src/java/org/apache/lucene/analysis/hunspell/ analyzers/common/src/test/org/apache/lucene/analysi

I would argue it is a bug fix, it fixes the handling of a certain kind of dictionary. On Thu, May 31, 2012 at 12:55 AM, Robert Muir wrote: > why are we backporting new features to a bugfix branch? > > On Wed, May 30, 2012 at 1:07 AM, wrote: > > Author: chrism > > Date: Wed May 30 05:07:31 2012

Jenkins build is back to normal : Lucene-Solr-trunk-Windows-Java7-64 #182

See - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

  1   2   >