Re: building PyLucene 3.0.2 on Win7/MinGW with Python 2.7

On Mon, Nov 22, 2010 at 9:45 PM, Bill Janssen jans...@parc.com wrote: Roman Chyla roman.ch...@gmail.com wrote: I had similar/same issue on win xp, it was the space in the java path, but i can't recall details. What happens if you change config.py to? C:\\Program\ Files\

Lucene-Solr-tests-only-trunk - Build # 1757 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/1757/ 1 tests failed. REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration Error Message: null Stack Trace: junit.framework.AssertionFailedError: at

Solr-trunk - Build # 1321 - Still Failing

Build: https://hudson.apache.org/hudson/job/Solr-trunk/1321/ All tests passed Build Log (for compile errors): [...truncated 18505 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,

[jira] Resolved: (SOLR-2249) ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/SOLR-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi resolved SOLR-2249. -- Resolution: Invalid Lucene/Solr cannot sort docs on tokenized field:

Lucene-Solr-tests-only-trunk - Build # 1760 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/1760/ 8 tests failed. REGRESSION: org.apache.solr.client.solrj.embedded.MultiCoreEmbeddedTest.testMultiCore Error Message: No such core: core0 Stack Trace: org.apache.solr.common.SolrException: No such core: core0

[jira] Updated: (SOLR-2245) MailEntityProcessor Update

[ https://issues.apache.org/jira/browse/SOLR-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Sturge updated SOLR-2245: --- Attachment: SOLR-2245.patch MailEntityProcessor Update --

[jira] Commented: (SOLR-2245) MailEntityProcessor Update

[ https://issues.apache.org/jira/browse/SOLR-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934800#action_12934800 ] Peter Sturge commented on SOLR-2245: This latest version of the updated

[jira] Issue Comment Edited: (SOLR-2245) MailEntityProcessor Update

[ https://issues.apache.org/jira/browse/SOLR-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934800#action_12934800 ] Peter Sturge edited comment on SOLR-2245 at 11/23/10 5:58 AM: --

[jira] Assigned: (SOLR-2244) Add Language Identification support

[ https://issues.apache.org/jira/browse/SOLR-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll reassigned SOLR-2244: - Assignee: Grant Ingersoll Add Language Identification support

[jira] Commented: (SOLR-2244) Add Language Identification support

[ https://issues.apache.org/jira/browse/SOLR-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934811#action_12934811 ] Grant Ingersoll commented on SOLR-2244: --- I'm going to suggest that we rename

[jira] Commented: (SOLR-2244) Add Language Identification support

[ https://issues.apache.org/jira/browse/SOLR-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934813#action_12934813 ] Tommaso Teofili commented on SOLR-2244: --- bq. I'm going to suggest that we rename

[jira] Created: (SOLR-2250) Add Boilerpipe support to Tika usage

Add Boilerpipe support to Tika usage Key: SOLR-2250 URL: https://issues.apache.org/jira/browse/SOLR-2250 Project: Solr Issue Type: Improvement Reporter: Grant Ingersoll Priority:

[jira] Commented: (SOLR-2244) Add Language Identification support

[ https://issues.apache.org/jira/browse/SOLR-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934816#action_12934816 ] Robert Muir commented on SOLR-2244: --- bq. Heck, it might even make sense at this point to

Lucene-Solr-tests-only-trunk - Build # 1763 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/1763/ 1 tests failed. REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration Error Message: expected:2 but was:3 Stack Trace: junit.framework.AssertionFailedError: expected:2 but was:3 at

[jira] Created: (SOLR-2251) Facet key not used when setting mincount, etc on individual facets

Facet key not used when setting mincount, etc on individual facets Key: SOLR-2251 URL: https://issues.apache.org/jira/browse/SOLR-2251 Project: Solr Issue Type:

Lucene-Solr-tests-only-trunk - Build # 1765 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/1765/ 2 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: Severe errors in solr configuration. Check your log files for more detailed information on what may be

[jira] Resolved: (LUCENE-2216) OpenBitSet#hashCode() may return false for identical sets.

[ https://issues.apache.org/jira/browse/LUCENE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler resolved LUCENE-2216. --- Resolution: Fixed Backported 3.0 revision: 1038096 Backported 2.9 revision: 1038098

Lucene-Solr-tests-only-trunk - Build # 1766 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/1766/ 1 tests failed. FAILED: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration Error Message: expected:2 but was:3 Stack Trace: junit.framework.AssertionFailedError: expected:2 but was:3 at

[jira] Issue Comment Edited: (SOLR-236) Field collapsing

[ https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934825#action_12934825 ] Luke Bochsler edited comment on SOLR-236 at 11/23/10 9:03 AM: --

[jira] Updated: (LUCENE-2729) Index corruption after 'read past EOF' under heavy update load and snapshot export

[ https://issues.apache.org/jira/browse/LUCENE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan te Beest updated LUCENE-2729: - Attachment: eof-extra-logging-4.log.zip Full log, stripped log and diffs against Lucene/Zoie.

[jira] Updated: (LUCENE-2729) Index corruption after 'read past EOF' under heavy update load and snapshot export

[ https://issues.apache.org/jira/browse/LUCENE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan te Beest updated LUCENE-2729: - Attachment: read-past-eof-debugging.zip The proper zip file containing full log, stripped log,

[jira] Updated: (LUCENE-2729) Index corruption after 'read past EOF' under heavy update load and snapshot export

[ https://issues.apache.org/jira/browse/LUCENE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan te Beest updated LUCENE-2729: - Attachment: (was: eof-extra-logging-4.log.zip) Index corruption after 'read past EOF'

[jira] Commented: (LUCENE-2729) Index corruption after 'read past EOF' under heavy update load and snapshot export

[ https://issues.apache.org/jira/browse/LUCENE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934857#action_12934857 ] Jan te Beest commented on LUCENE-2729: -- Hi Michael, I'm one of Nico's colleagues and

Re: Dismax Wiki page

Ahhh, thanks, that clears up some things for me... Erick On Mon, Nov 22, 2010 at 5:46 PM, Chris Hostetter hossman_luc...@fucit.orgwrote: : I'm running 1.4.1 on a Windows box. Trying to specify dismax via : defType=dismax fails, returning 0 results and doesn't look like it hits the : dismax

[jira] Commented: (LUCENE-2729) Index corruption after 'read past EOF' under heavy update load and snapshot export

[ https://issues.apache.org/jira/browse/LUCENE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934913#action_12934913 ] Michael McCandless commented on LUCENE-2729: On your workaround, I think that

[jira] Updated: (SOLR-2198) Grouping treats null values as equivalent to 0 or an empty string

[ https://issues.apache.org/jira/browse/SOLR-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-2198: --- Attachment: SOLR-2198.patch Here's an updated patch based on Harish's patch, with support for

Lucene-Solr-tests-only-trunk - Build # 1775 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/1775/ 2 tests failed. REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration Error Message: null Stack Trace: org.apache.solr.common.cloud.ZooKeeperException: at

[jira] Resolved: (SOLR-2198) Grouping treats null values as equivalent to 0 or an empty string

[ https://issues.apache.org/jira/browse/SOLR-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-2198. Resolution: Fixed OK, I added random testing support and committed. Grouping treats null values

Lucene-Solr-tests-only-3.x - Build # 1753 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/1753/ No tests ran. Build Log (for compile errors): [...truncated 781 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional

[jira] Commented: (LUCENE-2729) Index corruption after 'read past EOF' under heavy update load and snapshot export

[ https://issues.apache.org/jira/browse/LUCENE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935025#action_12935025 ] Xiaoyang Gu commented on LUCENE-2729: - Here's the code in zoie that exports index in

[jira] Commented: (SOLR-2068) Search Grouping: collapse by string specialization

[ https://issues.apache.org/jira/browse/SOLR-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935032#action_12935032 ] Yonik Seeley commented on SOLR-2068: I just enabled and committed the code to collapse

[jira] Resolved: (SOLR-2068) Search Grouping: collapse by string specialization

[ https://issues.apache.org/jira/browse/SOLR-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley resolved SOLR-2068. Resolution: Fixed Fix Version/s: 4.0 Search Grouping: collapse by string specialization

Lucene-Solr-tests-only-3.x - Build # 1754 - Still Failing

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/1754/ No tests ran. Build Log (for compile errors): [...truncated 4144 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For

Lucene-Solr-tests-only-trunk - Build # 1781 - Failure

Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/1781/ No tests ran. Build Log (for compile errors): [...truncated 1350 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For

[jira] Commented: (LUCENE-2729) Index corruption after 'read past EOF' under heavy update load and snapshot export

[ https://issues.apache.org/jira/browse/LUCENE-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935082#action_12935082 ] Michael McCandless commented on LUCENE-2729: bq. We accidentally opened the

Field Collapse backport for Solr 1.4 (1.4.1)?

Is there an easy way of enabling this feature on a stock build of solr 1.4 / 1.4.1 ? would very much like to incorporate it without having to carry over all the solr 4.0 trunk.. Thanks Adam

[jira] Commented: (LUCENE-2774) ant generate-maven-artifacts target broken for contrib

[ https://issues.apache.org/jira/browse/LUCENE-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935103#action_12935103 ] Steven Rowe commented on LUCENE-2774: - bq. after switching to maven-ant-tasks 2.0.9

'ant generate-maven-artifacts' oddities

In getting 'ant generate-maven-artifacts' to work for me (LUCENE-2774), I noticed two oddities: 1. On both trunk and branch_3x, Solr's maven artifacts are named without the embedded timestamp that everybody else (Lucene core/contrib/modules) gets, e.g.: