Re: How much Lucene 4.0 capability is NOT in Solr 4.0?

On Thu, Jun 7, 2012 at 5:52 AM, Shawn Heisey wrote: > I was perusing email from this list and came across LUCENE-4069.  If it is > as good as it says, it looks like a fit for a couple of the fields in my > index. > > I will admit that I don't entirely understand all of what's being said > regardin

How much Lucene 4.0 capability is NOT in Solr 4.0?

I was perusing email from this list and came across LUCENE-4069. If it is as good as it says, it looks like a fit for a couple of the fields in my index. I will admit that I don't entirely understand all of what's being said regarding codecs, postings, and other such terms, but because I run

[jira] [Commented] (SOLR-2592) Pluggable shard lookup mechanism for SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290763#comment-13290763 ] Lance Norskog commented on SOLR-2592: - Hash-based distribution (deterministic pseudo-ra

[JENKINS] Lucene-Solr-4.x-Windows-Java7-64 - Build # 5 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java7-64/5/ 1 tests failed. REGRESSION: org.apache.solr.spelling.suggest.SuggesterTest.testRebuild Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Exception during query at __randomize

[jira] [Commented] (SOLR-3288) audit tutorial before 4.0 release

[ https://issues.apache.org/jira/browse/SOLR-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290730#comment-13290730 ] Hoss Man commented on SOLR-3288: Made a pass at some major changes because of the new UI an

[jira] [Created] (SOLR-3516) Should provide mechanism for clients to see if currentSearcher is "newest" available

Hoss Man created SOLR-3516: -- Summary: Should provide mechanism for clients to see if currentSearcher is "newest" available Key: SOLR-3516 URL: https://issues.apache.org/jira/browse/SOLR-3516 Project: Solr

[jira] [Created] (SOLR-3515) "schema-browser_autoload" cookie used by "verbose" option on analysis page

Hoss Man created SOLR-3515: -- Summary: "schema-browser_autoload" cookie used by "verbose" option on analysis page Key: SOLR-3515 URL: https://issues.apache.org/jira/browse/SOLR-3515 Project: Solr Is

[jira] [Updated] (SOLR-2592) Pluggable shard lookup mechanism for SolrCloud

[ https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Garski updated SOLR-2592: - Attachment: dbq_fix.patch Here is an updated patch that fixes an issue where a delete by query is

[jira] [Commented] (SOLR-3514) WeakHashMap in FileFloatSource's cache only cleaned by GC

[ https://issues.apache.org/jira/browse/SOLR-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290592#comment-13290592 ] Greg Bowyer commented on SOLR-3514: --- One thing I will add to this, although I dont reject

[JENKINS] Lucene-Solr-trunk-Windows-Java6-64 - Build # 461 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java6-64/461/ 1 tests failed. REGRESSION: org.apache.solr.spelling.suggest.SuggesterWFSTTest.testRebuild Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Exception during query at __r

[jira] [Resolved] (SOLR-2284) tests should not depend on indexes in example data dirs

[ https://issues.apache.org/jira/browse/SOLR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man resolved SOLR-2284. Resolution: Fixed This was dealt with at some point, the following steps... {code} echo BOGUS > multicore/c

[jira] [Updated] (SOLR-3211) Allow parameter override in conjunction with "spellcheck.maxCollationTries"

[ https://issues.apache.org/jira/browse/SOLR-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer updated SOLR-3211: - Attachment: SOLR-3211.patch Here is a patch for this with a unit test. This creates a new parameter synta

[jira] [Updated] (SOLR-3211) Allow parameter override in conjunction with "spellcheck.maxCollationTries"

[ https://issues.apache.org/jira/browse/SOLR-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Dyer updated SOLR-3211: - Affects Version/s: (was: 3.5) 4.0 3.6 Fix Version

[jira] [Commented] (LUCENE-2357) Reduce transient RAM usage while merging by using packed ints array for docID re-mapping

[ https://issues.apache.org/jira/browse/LUCENE-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290477#comment-13290477 ] Adrien Grand commented on LUCENE-2357: -- I ran a quick test that indexes a few millio

[jira] [Resolved] (SOLR-3257) Dedupe update.chain example should include DistribtedUpdateProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man resolved SOLR-3257. Resolution: Fixed > Dedupe update.chain example should include DistribtedUpdateProcessorFactory > --

[jira] [Assigned] (SOLR-3257) Dedupe update.chain example should include DistribtedUpdateProcessorFactory

[ https://issues.apache.org/jira/browse/SOLR-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man reassigned SOLR-3257: -- Assignee: Hoss Man > Dedupe update.chain example should include DistribtedUpdateProcessorFactory > -

[jira] [Resolved] (SOLR-1067) QueryParsing.parseFunction uses Singleton Core (SolrCore.getSolrCore())

[ https://issues.apache.org/jira/browse/SOLR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man resolved SOLR-1067. Resolution: Fixed no longer a problem in 4.0 due to both of these (deprecated) methods having been removed.

[jira] [Updated] (SOLR-3514) WeakHashMap in FileFloatSource's cache only cleaned by GC

[ https://issues.apache.org/jira/browse/SOLR-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregg Donovan updated SOLR-3514: Attachment: SOLR-3514.patch > WeakHashMap in FileFloatSource's cache only cleaned by GC > --

[jira] [Created] (SOLR-3514) WeakHashMap in FileFloatSource's cache only cleaned by GC

Gregg Donovan created SOLR-3514: --- Summary: WeakHashMap in FileFloatSource's cache only cleaned by GC Key: SOLR-3514 URL: https://issues.apache.org/jira/browse/SOLR-3514 Project: Solr Issue Type

Re: remove "via"

I think I understand your viewpoint but I'll stick with mine for now (that is: I don't care for 'via' attribution in CHANGES.txt, but I also don't object it -- I'll stick with whatever consensus there will be). Dawid On Wed, Jun 6, 2012 at 9:54 PM, Mark Miller wrote: > > On Jun 6, 2012, at 2:45

[jira] [Commented] (SOLR-3484) LogUpdateProcessor throws ConcurrentModificationException under multi-threading calls

[ https://issues.apache.org/jira/browse/SOLR-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290380#comment-13290380 ] Mikhail Khludnev commented on SOLR-3484: [~aaronsimmons], particularly your problem

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

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2786/ 4 tests failed. REGRESSION: org.apache.lucene.collation.TestCollationKeyAnalyzer.testFarsiRangeFilterCollating Error Message: The index Term should not be included. expected:<0> but was:<1> Stack Trace: java.lang.Ass

[jira] [Commented] (SOLR-2804) Logging error causes entire DIH process to fail

[ https://issues.apache.org/jira/browse/SOLR-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290375#comment-13290375 ] Mikhail Khludnev commented on SOLR-2804: misguiding attachments 1th 3rd Jan has bee

[jira] [Updated] (SOLR-2804) Logging error causes entire DIH process to fail

[ https://issues.apache.org/jira/browse/SOLR-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-2804: --- Attachment: (was: SOLR-2804-3x.patch) > Logging error causes entire DIH process to fai

[jira] [Updated] (SOLR-2804) Logging error causes entire DIH process to fail

[ https://issues.apache.org/jira/browse/SOLR-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-2804: --- Attachment: (was: SOLR-2804.patch) > Logging error causes entire DIH process to fail >

[JENKINS] Lucene-Solr-trunk-Windows-Java6-64 - Build # 460 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java6-64/460/ 1 tests failed. REGRESSION: org.apache.solr.handler.TestReplicationHandler.test Error Message: expected:<498> but was:<0> Stack Trace: java.lang.AssertionError: expected:<498> but was:<0> at __random

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

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14609/ No tests ran. Build Log: [...truncated 9829 lines...] [...truncated 9829 lines...] [...truncated 9829 lines...] [...truncated 9829 lines...] [...truncated 9766 lines...] FATAL: Unable to delete script file /var/tmp/hudso

[JENKINS] Lucene-Solr-tests-only-4.x-java7 - Build # 1 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x-java7/1/ 8 tests failed. FAILED: org.apache.lucene.collation.TestCollationKeyAnalyzer.testFarsiRangeFilterCollating Error Message: The index Term should not be included. expected:<0> but was:<1> Stack Trace: java.lang.AssertionErr

Added hunspell stemming to Contrib.Analyzers

Hi, I've just committed[1] the hunspell stuff to Contrib.Analyzers. I've added license headers, set svn:eol-style and ensured that the tests works. Could someone check if I've forgot something? [1] http://svn.apache.org/viewvc?view=revision&revision=1347076

[JENKINS] Lucene-Solr-tests-only-4.x - Build # 1 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/1/ 1 tests failed. FAILED: org.apache.solr.client.solrj.embedded.MultiCoreEmbeddedTest.testMultiCore Error Message: Stack Trace: java.lang.AssertionError at __randomizedtesting.SeedInfo.seed([91DCC44326D5077A:15F4DFB0E90

Re: remove "via"

On Jun 6, 2012, at 2:45 PM, Dawid Weiss wrote: > As > far as important stuff is done I wouldn't worry about who gets the > credit... I think that's kind of short sighted. These credits matter to some, and many of these things, while they may not matter to us personally, that does not make them

[jira] [Commented] (SOLR-3484) LogUpdateProcessor throws ConcurrentModificationException under multi-threading calls

[ https://issues.apache.org/jira/browse/SOLR-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290348#comment-13290348 ] Aaron Simmons commented on SOLR-3484: - I have read the related tickets [SOLR-2694, SOLR

[JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 3 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/3/ 6 tests failed. REGRESSION: org.apache.solr.handler.dataimport.TestSqlEntityProcessorDelta2.testCompositePk_DeltaImport_nodelta Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Excepti

Re: remove "via"

My initial +1 was because I guess I don't care if it's either way. As far as important stuff is done I wouldn't worry about who gets the credit... Dawid On Wed, Jun 6, 2012 at 8:03 PM, Erick Erickson wrote: > Following where Hoss bravely leads, I'll change too to -0 > > Erick > > On Wed, Jun 6,

Re: remove "via"

Following where Hoss bravely leads, I'll change too to -0 Erick On Wed, Jun 6, 2012 at 1:56 PM, Chris Hostetter wrote: > > : I've looked at the "via" in the changelog to figure out which committer > : works in which areas the most, and therefore who to ping about a patch. > > That's a user for t

Re: remove "via"

: I've looked at the "via" in the changelog to figure out which committer : works in which areas the most, and therefore who to ping about a patch. That's a user for the info that i hadn't really considered, and definitely gives me pause... I guess i'm changing my opinion: -0. -Hoss ---

[jira] [Updated] (LUCENE-4117) Add FST.BytesReader to all FST arc-reading APIs

[ https://issues.apache.org/jira/browse/LUCENE-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-4117: --- Attachment: LUCENE-4117.patch Patch. > Add FST.BytesReader to all F

[jira] [Created] (LUCENE-4117) Add FST.BytesReader to all FST arc-reading APIs

Michael McCandless created LUCENE-4117: -- Summary: Add FST.BytesReader to all FST arc-reading APIs Key: LUCENE-4117 URL: https://issues.apache.org/jira/browse/LUCENE-4117 Project: Lucene - Java

[jira] [Commented] (LUCENE-4114) Large docID / docvalue size combination produces arithmetic overflow

[ https://issues.apache.org/jira/browse/LUCENE-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290293#comment-13290293 ] Walt Elder commented on LUCENE-4114: Awesome. Thanks all. > Large do

Re: remove "via"

On 06/06/2012 00:40, Robert Muir wrote: Hello, Currently we do this in CHANGES.txt: LUCENE-: Fixed a horrible nasty bug. (Joe Contributor via John Doe Committer) I propose we remove "via" from CHANGES.txt. I don't think any users care about who committed changes and I think it de-emphas

[jira] [Resolved] (LUCENE-4114) Large docID / docvalue size combination produces arithmetic overflow

[ https://issues.apache.org/jira/browse/LUCENE-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-4114. Resolution: Fixed Thanks Walt! > Large docID / docvalue size comb

Re: remove "via"

> > Yes... I think it should be: > > LUCENE-: > Fixed a horrible nasty bug. (Joe Contributor) > > I think it's very clear who the author was with: LUCENE-: Fixed a horrible nasty bug. (Joe Contributor via Mr Committer) I agree that committers should be generous and low key about their o

[JENKINS] Lucene-Solr-4.x-Windows-Java6-64 - Build # 1 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/1/ 1 tests failed. FAILED: org.apache.solr.spelling.suggest.SuggesterFSTTest.testRebuild Error Message: Exception during query Stack Trace: java.lang.RuntimeException: Exception during query at __randomized

[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 785 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/785/ 1 tests failed. FAILED: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch Error Message: Server at http://localhost:48528/solr/collection1 returned non ok status:500, message:Server Error Stack Trace:

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290253#comment-13290253 ] Michael McCandless commented on LUCENE-4101: OK, I think the best compromise

Re: remove "via"

+1 to remove the via. If someone has done work other then reviewing and committing then he could add himself as one of the author (Order is important; contributor first then committer. Depending on the work done). Maybe the contributors that have contributed in a release can also be highlighted in

[jira] [Commented] (LUCENE-4101) Remove XXXField.TYPE_STORED

[ https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290228#comment-13290228 ] Grant Ingersoll commented on LUCENE-4101: - I can't see a situation where having t

[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 784 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/784/ 1 tests failed. FAILED: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch Error Message: Server at http://localhost:54801/solr/collection1 returned non ok status:500, message:Server Error Stack Trace:

Re: [JENKINS] Lucene-Solr-trunk-Windows-Java7-64 - Build # 253 - Still Failing!

I added a log line to help in debugging a test - that log method does not like getting a null though - fixed it. On Jun 6, 2012, at 10:54 AM, jenk...@sd-datasolutions.de wrote: > Build: > http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/253/ > > 1 tests failed. > FAILE

[JENKINS] Lucene-Solr-trunk-Windows-Java7-64 - Build # 253 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/253/ 1 tests failed. FAILED: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: expected:<409> but was:<500> Stack Trace: java.lang.AssertionError: expected:<409> but was:<500> a

Re: problem with mapping-iso accents

First, please post usage/configuration questions over on the user's list, see: http://lucene.apache.org/solr/discussion.html. The dev list is intended for discussing development issues/bugs/etc. You're probably being fooled by setting 'stored="true" '. When you return the value of a field in a doc

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

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/511/ 1 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: expected:<409> but was:<500> Stack Trace: java.lang.AssertionError: expected:<409> but was:<500> at __randomizedte

problem with mapping-iso accents

Hi, i have a problem ISOaccent tokenize filter. i have e field in my schema with this filter: if i try this filter with analyisis tool in solr admin panel it works. for example: sarà => sara. but when i create indexes it doesn't work. in the index the field is "sarà" with accent. why? i use

Re: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 1 - Failure!

This is just a typo...Uwe was close to the dark side when configuring this build :) On Wed, Jun 6, 2012 at 4:36 PM, wrote: > Build: > http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/1/ > > No tests ran. > > Build Log: > [...truncated 54 lines...] > > [...truncated 54 lines

[JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 1 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java6-64/1/ No tests ran. Build Log: [...truncated 54 lines...] [...truncated 54 lines...] [...truncated 54 lines...] [...truncated 54 lines...] [...truncated 42 lines...] FATAL: null java.lang.NullPointerException at

[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 783 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/783/ 2 tests failed. REGRESSION: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch Error Message: Server at http://localhost:59355/solr/collection1 returned non ok status:500, message:Server Error Stack Tra

[jira] [Assigned] (LUCENE-4116) Jenkins failure: control claims no stalled threads but waiter seems to be blocked

[ https://issues.apache.org/jira/browse/LUCENE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Willnauer reassigned LUCENE-4116: --- Assignee: Simon Willnauer > Jenkins failure: control claims no stalled threads b

[jira] [Created] (LUCENE-4116) Jenkins failure: control claims no stalled threads but waiter seems to be blocked

Uwe Schindler created LUCENE-4116: - Summary: Jenkins failure: control claims no stalled threads but waiter seems to be blocked Key: LUCENE-4116 URL: https://issues.apache.org/jira/browse/LUCENE-4116 P

[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 782 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/782/ 1 tests failed. FAILED: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: expected:<409> but was:<500> Stack Trace: java.lang.AssertionError: expected:<409> but was:<500> at

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

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14607/ 1 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: expected:<409> but was:<500> Stack Trace: java.lang.AssertionError: expected:<409> but was:<500> at __rando

[JENKINS] Lucene-Solr-trunk-Windows-Java6-64 - Build # 457 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java6-64/457/ 1 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: expected:<409> but was:<500> Stack Trace: java.lang.AssertionError: expected:<409> but was:<500>

[JENKINS] Lucene-Solr-trunk-Linux-Java6-64 - Build # 781 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java6-64/781/ 2 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: expected:<409> but was:<500> Stack Trace: java.lang.AssertionError: expected:<409> but was:<500>

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

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/2785/ 1 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZkTest.testDistribSearch Error Message: expected:<409> but was:<500> Stack Trace: java.lang.AssertionError: expected:<409> but was:<500> at __

RE: remove "via"

Hi Eric, I agree 100% with you, we should keep "via". Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Eric Pugh [mailto:ep...@opensourceconnections.com] > Sent: Wednesday, June 06, 2012 2:33 PM > T

[jira] [Commented] (SOLR-3416) HTTP ERROR 400. Problem accessing /solr/select/. Reason: undefined field text

[ https://issues.apache.org/jira/browse/SOLR-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290122#comment-13290122 ] Jack Krupansky commented on SOLR-3416: -- This is most certainly not a bug in Solr. Plea

[jira] [Commented] (SOLR-3416) HTTP ERROR 400. Problem accessing /solr/select/. Reason: undefined field text

[ https://issues.apache.org/jira/browse/SOLR-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290107#comment-13290107 ] sheethal Shreedhar commented on SOLR-3416: -- I have been having the same problems a

Re: remove "via"

On Jun 6, 2012, at 8:26 AM, Dawid Weiss wrote: > If you have contributed to > the issue and your gut feeling is you're part of the patch's effort, > you should include yourself as the author. Personally, I prefer the current std - where a strong review and the taking of responsibility earns yo

Re: remove "via"

I've looked at the "via" in the changelog to figure out which committer works in which areas the most, and therefore who to ping about a patch. And I do think that shepherding a patch file through to commit is worthy of some credit. It's often a fair amount of work to evaluate a patch file, of

[JENKINS] Lucene-Solr-trunk-Windows-Java7-64 - Build # 252 - Still Failing!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/252/ 1 tests failed. REGRESSION: org.apache.lucene.index.TestDocumentsWriterStallControl.testAccquireReleaseRace Error Message: control claims no stalled threads but waiter seems to be blocked Stack Trace: java.l

Re: remove "via"

> code change. I think *via* is pretty clear regarding credit, and I think it > has value in it's information. Even if you simply commit someone else work, > *you* are contributing to the issue. You better have reviewed it, you better > be willing to take responsibility for it. I don't think th

Re: [JENKINS] Lucene-Solr-trunk-Windows-Java7-64 - Build # 251 - Failure!

Well, I'm back from vaca, so started looking at this again. Unfortunately, even with Java 7, now I'm having trouble seeing it even once in any of my hundreds of runs. Bleh. Guess a crystal in my virtual machine shifted while I was away. Though on second glance, it also appears to be happening le

Re: remove "via"

On Jun 5, 2012, at 6:40 PM, Robert Muir wrote: > Opinions? I disagree - I think it makes it really easy to track who actually did the commit (the person *responsible* if it's a bad commit or a good commit) and I think there is some credit in a committer applying someones patch. They are doing

[JENKINS] Lucene-Solr-trunk-Linux-Java7-64 - Build # 183 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java7-64/183/ 1 tests failed. REGRESSION: org.apache.solr.cloud.FullSolrCloudTest.testDistribSearch Error Message: Server at http://localhost:48203/solr/collection1 returned non ok status:500, message:Server Error Stack Tra

[JENKINS] Lucene-Solr-trunk-Windows-Java7-64 - Build # 251 - Failure!

Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/251/ 1 tests failed. REGRESSION: org.apache.solr.handler.TestReplicationHandler.test Error Message: expected:<494> but was:<0> Stack Trace: java.lang.AssertionError: expected:<494> but was:<0> at __random

Re: remove "via"

+1. If the existing ones are removed, it'll be less likely for me to see one and think that's the way it _should_ be done On Wed, Jun 6, 2012 at 2:34 AM, Tommaso Teofili wrote: > 2012/6/6 Robert Muir >> >> Hello, >> >> Currently we do this in CHANGES.txt: >> >> LUCENE-: >>  Fixed a horri

[jira] [Commented] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module

[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290040#comment-13290040 ] Lance Norskog commented on LUCENE-2899: --- An explanation about the OpenNLPUtil facto

[JENKINS] Solr-trunk - Build # 1877 - Failure

Build: https://builds.apache.org/job/Solr-trunk/1877/ 1 tests failed. REGRESSION: org.apache.solr.cloud.RecoveryZkTest.testDistribSearch Error Message: Thread threw an uncaught exception, thread: Thread[Lucene Merge Thread #2,6,] Stack Trace: java.lang.RuntimeException: Thread threw an uncaught

[jira] [Resolved] (LUCENE-4108) Add replaceTaxonomy to DirectoryTaxonomyWriter

[ https://issues.apache.org/jira/browse/LUCENE-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera resolved LUCENE-4108. Resolution: Fixed Fix Version/s: (was: 3.6.1) Committed revision 1346793 to 4x. Since

[jira] [Comment Edited] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module

[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290007#comment-13290007 ] Lance Norskog edited comment on LUCENE-2899 at 6/6/12 9:03 AM:

[jira] [Commented] (LUCENE-4108) Add replaceTaxonomy to DirectoryTaxonomyWriter

[ https://issues.apache.org/jira/browse/LUCENE-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290024#comment-13290024 ] Shai Erera commented on LUCENE-4108: Committed revision 1346784 to trunk, now porting

[jira] [Commented] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module

[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290023#comment-13290023 ] Lance Norskog commented on LUCENE-2899: --- I consider the code and feature set mostly

[jira] [Commented] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module

[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290020#comment-13290020 ] Lance Norskog commented on LUCENE-2899: --- About the build- # This should be a Lucene

[jira] [Commented] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module

[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290015#comment-13290015 ] Lance Norskog commented on LUCENE-2899: --- Notes for a Wiki page: OpenNLP Integratio

[jira] [Updated] (LUCENE-2899) Add OpenNLP Analysis capabilities as a module

[ https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lance Norskog updated LUCENE-2899: -- Attachment: opennlp_trunk.patch This is a patch for the trunk (as of a few days ago) that supp