[jira] Commented: (LUCENE-2898) CMS merge throttling is not aggressive enough

[ https://issues.apache.org/jira/browse/LUCENE-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988540#action_12988540 ] Shai Erera commented on LUCENE-2898: Mike, now that you wait before you poll IW.getNex

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 4297 - Failure

Hmmm, looks like real bug (hopefully a test bug though). I'll dig. -Yonik http://lucidimagination.com On Sat, Jan 29, 2011 at 8:49 PM, Apache Hudson Server wrote: > Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4297/ > > 1 tests failed. > REGRESSION:  org.apache.solr

[jira] Resolved: (SOLR-2308) Race condition still exists in StreamingUpdateSolrServer which could cause it to hang

[ https://issues.apache.org/jira/browse/SOLR-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-2308. Resolution: Fixed Fix Version/s: 4.0 3.1 Oops, I saw Johannes fix posted i

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 4297 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4297/ 1 tests failed. REGRESSION: org.apache.solr.TestGroupingSearch.testRandomGrouping Error Message: mismatch: 'z'!='fp' @ grouped/foo_s/groups/[0]/groupValue Stack Trace: junit.framework.AssertionFailedError: mismatch:

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 4280 - Still Failing

Uh, sorry. Thanks Yonik! Koji (11/01/30 1:20), Yonik Seeley wrote: I'm looking at this now - seems due to koji's fix to minCount comparison. I'm trying to figure out if the test or the code is in error, but this test is hard to understand w/ it's get(0).get(1) type of stuff (w/ no comments abou

[jira] Updated: (LUCENE-2897) apply delete-by-Term and docID immediately to newly flushed segments

[ https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2897: --- Attachment: LUCENE-2897.patch Patch -- I think it's ready to commit! > apply delete

Re: Distributed Indexing

Lance, Firstly, we're proposing a ShardDistributionPolicy interface for which there is a default (mod of the doc ID) but other implementations are possible. Another easy implementation would be a randomised or round robin one. As to threading, the first task would be to put all of the source docu

Re: Distributed Indexing

I would suggest that a DistributedRequestUpdateHandler run single-threaded, doing only one document at a time. If I want more than one, I run it twice or N times with my own program. Also, this should have a policy object which decides exactly how documents are distributed. There are different tec

[jira] Updated: (LUCENE-2751) add LuceneTestCase.newSearcher()

[ https://issues.apache.org/jira/browse/LUCENE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated LUCENE-2751: - Attachment: LUCENE-2751.patch Whew, this code is complex, and I don't really have a solution I l

Re: Threading of JIRA e-mails in gmail?

I've created a jira request to the infrastructure team, it's here: https://issues.apache.org/jira/browse/INFRA-3403 Dawid On Sat, Jan 29, 2011 at 6:26 PM, Michael McCandless wrote: > On Sat, Jan 29, 2011 at 10:04 AM, Dawid Weiss > wrote: > I eventually went with procmail (with a little he

Re: Distributed Indexing

Hello Yonik, On Thu, 2011-01-27 at 08:01 -0500, Yonik Seeley wrote: > Making it easy for clients I think is key... one should be able to > update any node in the solr cluster and have solr take care of the > hard part about updating all relevant shards. This will most likely > involve an update p

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 4288 - Still Failing

Ugh -- I committed fix. Mike On Sat, Jan 29, 2011 at 3:29 PM, Apache Hudson Server wrote: > Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4288/ > > No tests ran. > > Build Log (for compile errors): > [...truncated 18 lines...] > + JAVA_HOME_16=/home/hudson/tools/java/l

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 4288 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4288/ No tests ran. Build Log (for compile errors): [...truncated 18 lines...] + JAVA_HOME_16=/home/hudson/tools/java/latest1.6 + TESTS_MULTIPLIER=3 + TEST_LINE_DOCS_FILE=/home/hudson/lucene-data/enwiki.random.lines.txt.gz +

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 4287 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4287/ No tests ran. Build Log (for compile errors): [...truncated 112 lines...] + cd /home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only-trunk/checkout + JAVA_HOME=/home/hudson/tools/java/latest1.5 /home/hudson/tools

[jira] Commented: (LUCENE-1076) Allow MergePolicy to select non-contiguous merges

[ https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988499#action_12988499 ] Michael McCandless commented on LUCENE-1076: Committed to trunk; I'll let this

[jira] Commented: (LUCENE-2671) Add sort missing first/last ability to SortField and ValueComparator

[ https://issues.apache.org/jira/browse/LUCENE-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988496#action_12988496 ] Ryan McKinley commented on LUCENE-2671: --- in r1065093, i deprecated the sortable* fie

[jira] Commented: (LUCENE-2671) Add sort missing first/last ability to SortField and ValueComparator

[ https://issues.apache.org/jira/browse/LUCENE-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988492#action_12988492 ] Yonik Seeley commented on LUCENE-2671: -- bq. Does this mean we should now deprecate: o

[jira] Resolved: (LUCENE-2671) Add sort missing first/last ability to SortField and ValueComparator

[ https://issues.apache.org/jira/browse/LUCENE-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley resolved LUCENE-2671. --- Resolution: Fixed This was fixed a while ago -- i think it fixes all concerns... Does this

[HUDSON-MAVEN] Lucene-Solr-Maven-trunk #5: POMs out of sync

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-Maven-trunk/5/ 1 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: Error executing query Stack Trace: org.apache.solr.client.solrj.SolrServerException: Error executing query at

Re: Threading of JIRA e-mails in gmail?

On Sat, Jan 29, 2011 at 10:04 AM, Dawid Weiss wrote: >>> > I eventually went with procmail (with a little help from guys that >>> > know it better). So, for folks who do have access to their MTA and can >>> > filter e-mails, here it is (postfix/procmail combo): >> >> From the email address it seem

[jira] Resolved: (LUCENE-2898) CMS merge throttling is not aggressive enough

[ https://issues.apache.org/jira/browse/LUCENE-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-2898. Resolution: Fixed > CMS merge throttling is not aggressive enough > --

[jira] Commented: (LUCENE-2897) apply delete-by-Term and docID immediately to newly flushed segments

[ https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988481#action_12988481 ] Michael McCandless commented on LUCENE-2897: bq. Instead we're building the de

[jira] Updated: (SOLR-2061) Generate jar containing test classes.

[ https://issues.apache.org/jira/browse/SOLR-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Drew Farris updated SOLR-2061: -- Attachment: SOLR-2061.patch Updated patch for latest rev > Generate jar containing test classes. >

[jira] Closed: (SOLR-717) Distribute Solr test jar so test code can be used by clients

[ https://issues.apache.org/jira/browse/SOLR-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll closed SOLR-717. Resolution: Duplicate SOLR-2061 should take care of this > Distribute Solr test jar so test code can

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 4281 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4281/ 4 tests failed. FAILED: org.apache.solr.client.solrj.SolrExampleBinaryTest.testPivotFacet Error Message: expected:<1> but was:<2> Stack Trace: junit.framework.AssertionFailedError: expected:<1> but was:<2> at

[jira] Commented: (LUCENE-2897) apply delete-by-Term and docID immediately to newly flushed segments

[ https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988474#action_12988474 ] Michael Busch commented on LUCENE-2897: --- Yeah this is nice. I was thinking we'd swi

[jira] Commented: (LUCENE-2897) apply delete-by-Term and docID immediately to newly flushed segments

[ https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988473#action_12988473 ] Jason Rutherglen commented on LUCENE-2897: -- bq. Well... I think we can't [easily]

[jira] Commented: (LUCENE-2897) apply delete-by-Term and docID immediately to newly flushed segments

[ https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988472#action_12988472 ] Michael McCandless commented on LUCENE-2897: bq. I had to read this a few time

Re: [HUDSON] Lucene-Solr-tests-only-trunk - Build # 4280 - Still Failing

I'm looking at this now - seems due to koji's fix to minCount comparison. I'm trying to figure out if the test or the code is in error, but this test is hard to understand w/ it's get(0).get(1) type of stuff (w/ no comments about what path it is). -Yonik http://lucidimagination.com On Sat, Jan

[jira] Updated: (LUCENE-2897) apply delete-by-Term and docID immediately to newly flushed segments

[ https://issues.apache.org/jira/browse/LUCENE-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2897: --- Attachment: LUCENE-2897.patch Initial patch. The approach is nice and simple ;) Al

[jira] Created: (LUCENE-2898) CMS merge throttling is not aggressive enough

CMS merge throttling is not aggressive enough - Key: LUCENE-2898 URL: https://issues.apache.org/jira/browse/LUCENE-2898 Project: Lucene - Java Issue Type: Bug Components: Index

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 4280 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4280/ 4 tests failed. FAILED: org.apache.solr.client.solrj.SolrExampleBinaryTest.testPivotFacet Error Message: expected:<1> but was:<2> Stack Trace: junit.framework.AssertionFailedError: expected:<1> but was:<2> at

Re: Threading of JIRA e-mails in gmail?

> without knowing how this actually happens...  is this something we > could get installed in the apache infrastructure?  could we filter > dev@lucene.apache.org, rather then each person? > > Does apache run procmail? Good idea, Ryan! people.apache.org sure does have procmail installed -- [dweiss

[HUDSON] Lucene-Solr-tests-only-trunk - Build # 4279 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/4279/ 4 tests failed. REGRESSION: org.apache.solr.client.solrj.SolrExampleBinaryTest.testPivotFacet Error Message: expected:<1> but was:<2> Stack Trace: junit.framework.AssertionFailedError: expected:<1> but was:<2>

[jira] Commented: (LUCENE-1076) Allow MergePolicy to select non-contiguous merges

[ https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988465#action_12988465 ] Michael McCandless commented on LUCENE-1076: Another benefit of the transactio

Re: Threading of JIRA e-mails in gmail?

On Sat, Jan 29, 2011 at 10:04 AM, Dawid Weiss wrote: >>> > I eventually went with procmail (with a little help from guys that >>> > know it better). So, for folks who do have access to their MTA and can >>> > filter e-mails, here it is (postfix/procmail combo): >> >> From the email address it seem

[HUDSON-MAVEN] Lucene-Solr-Maven-trunk #4: POMs out of sync

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-Maven-trunk/4/ 4 tests failed. REGRESSION: org.apache.solr.client.solrj.SolrExampleBinaryTest.testPivotFacet Error Message: expected:<1> but was:<2> Stack Trace: java.lang.AssertionError: expected:<1> but was:<2> at org.junit.Asser

Re: Threading of JIRA e-mails in gmail?

>> > I eventually went with procmail (with a little help from guys that >> > know it better). So, for folks who do have access to their MTA and can >> > filter e-mails, here it is (postfix/procmail combo): > > From the email address it seems you also had to modify the email address > registered to

[jira] Commented: (LUCENE-2324) Per thread DocumentsWriters that write their own private segments

[ https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988463#action_12988463 ] Jason Rutherglen commented on LUCENE-2324: -- I had to read this a few times, yes i

[jira] Commented: (LUCENE-2324) Per thread DocumentsWriters that write their own private segments

[ https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988462#action_12988462 ] Michael McCandless commented on LUCENE-2324: OK, I opened LUCENE-2897. > Per

[jira] Created: (LUCENE-2897) apply delete-by-Term and docID immediately to newly flushed segments

apply delete-by-Term and docID immediately to newly flushed segments Key: LUCENE-2897 URL: https://issues.apache.org/jira/browse/LUCENE-2897 Project: Lucene - Java Issue Ty

[jira] Commented: (LUCENE-2324) Per thread DocumentsWriters that write their own private segments

[ https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988460#action_12988460 ] Michael McCandless commented on LUCENE-2324: bq. Alternatively, we could keep

[jira] Commented: (LUCENE-1076) Allow MergePolicy to select non-contiguous merges

[ https://issues.apache.org/jira/browse/LUCENE-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988458#action_12988458 ] Michael McCandless commented on LUCENE-1076: bq. I saw this and thought it was

Re: Threading of JIRA e-mails in gmail?

This JIRA/gmail threads thing is driving me crazy too, thanks for sharing! There are a few discussions of this in atlassian - http://jira.atlassian.com/browse/JRA-12640 and http://jira.atlassian.com/browse/JRA-3609 - the latter allowed to customize the mail subject in JIRA as mentioned above. I t

[jira] Commented: (LUCENE-2324) Per thread DocumentsWriters that write their own private segments

[ https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988457#action_12988457 ] Michael McCandless commented on LUCENE-2324: Actually, instead of buffering th

Re: unassigned JIRA issues set for 3.1

I moved the unassigned ones out of 3.1... if you want to fix any of these issues for 3.1 please just assign it to yourself and put it back in 3.1... thanks On Sun, Jan 23, 2011 at 3:46 PM, Robert Muir wrote: > There are some unassigned JIRA issues in Lucene/Solr currently set > with Fix Version:

Re: Threading of JIRA e-mails in gmail?

I think this is akin to what some other projects do to automatically apply patches and validate whether they apply or not. I've always wanted such a system for Lucene, but never had the time to hook it together. I wish Hudson had a JIRA plugin that did it automatically (or maybe there is and I

[jira] Updated: (SOLR-2271) XSL features fail using turkish locale due to JVM/xalan bug

[ https://issues.apache.org/jira/browse/SOLR-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2271: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-2165) TestReplicationHandler test failure (branch_3x)

[ https://issues.apache.org/jira/browse/SOLR-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2165: -- Fix Version/s: (was: 4.0) (was: 3.1) Next Moving out all u

[jira] Updated: (SOLR-2018) waitFlush="false" currently doens't work

[ https://issues.apache.org/jira/browse/SOLR-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2018: -- Fix Version/s: (was: 4.0) (was: 3.1) Next Moving out all u

[jira] Updated: (SOLR-2075) SpatialQParserPlugin and HostIP adaptor

[ https://issues.apache.org/jira/browse/SOLR-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2075: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-2077) Spatial example solconfig updates

[ https://issues.apache.org/jira/browse/SOLR-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2077: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-1967) New Native PHP Response Writer Class

[ https://issues.apache.org/jira/browse/SOLR-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-1967: -- Fix Version/s: (was: 4.0) (was: 3.1) (was: 1.5) Moving

[jira] Updated: (SOLR-2076) Spatial example schema updates

[ https://issues.apache.org/jira/browse/SOLR-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2076: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-2074) GeoRSS ResponseWriter

[ https://issues.apache.org/jira/browse/SOLR-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2074: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-2292) Lock down NamedList API, remove inefficent and esoteric methods

[ https://issues.apache.org/jira/browse/SOLR-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2292: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-2079) Expose HttpServletRequest object from SolrQueryRequest object

[ https://issues.apache.org/jira/browse/SOLR-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2079: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-2124) SEVERE exceptions are being logged for expected PingRequestHandler SERVICE_UNAVAILABLE exceptions

[ https://issues.apache.org/jira/browse/SOLR-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2124: -- Fix Version/s: (was: 4.0) (was: 3.1) Next Moving out all u

[jira] Updated: (SOLR-2082) Geopost.jar for loading geonames data

[ https://issues.apache.org/jira/browse/SOLR-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2082: -- Fix Version/s: (was: 3.1) Next Moving out all unassigned issues set to 3.1 per th

[jira] Updated: (SOLR-2115) DataImportHandler config file *must* be specified in "defaults" or status will be "DataImportHandler started. Not Initialized. No commands can be run"

[ https://issues.apache.org/jira/browse/SOLR-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated SOLR-2115: -- Fix Version/s: (was: 1.4.2) (was: 4.0) (was: 3.1)

[jira] Updated: (LUCENE-2896) in advance(), don't try to skip if there is evidence it will fail

[ https://issues.apache.org/jira/browse/LUCENE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-2896: Attachment: LUCENE-2896.patch ||Query||QPS trunk||QPS patch||Pct diff |+united +states|10.29|1

[jira] Created: (LUCENE-2896) in advance(), don't try to skip if there is evidence it will fail

in advance(), don't try to skip if there is evidence it will fail - Key: LUCENE-2896 URL: https://issues.apache.org/jira/browse/LUCENE-2896 Project: Lucene - Java Issue Type: Im