How to best test possible performance impact of a new lucene patch

I've been following the Lucene/Solr community for a long time and finally have found (or: taken) the time to start implementing some of my ideas how to improve on it; this will be my first proposed patch. I'm working on some changes to the Collector API to significantly improve the performance of

Re: [Lucene.Net] Comparing APIs of two DLLs (something like Clirr for .NET)?

On 2011-09-07, Prescott Nasser wrote: > I have heard people use http://www.bitwidgets.com/ to success. I have > not used it myself though. This looks useful at first glance. Unless anything else is mentioned I'm going to apply for a free license for Open Source projects and share my experience h

[jira] [Commented] (LUCENE-3418) Lucene is not fsync'ing files on commit

[ https://issues.apache.org/jira/browse/LUCENE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098682#comment-13098682 ] Shai Erera commented on LUCENE-3418: Mike, just to make sure, did you actually see th

Re: svn commit: r1165902 - in /lucene/dev/trunk/lucene: CHANGES.txt src/java/org/apache/lucene/store/FSDirectory.java

Good point -- I'll sharpen that. Mike McCandless http://blog.mikemccandless.com On Tue, Sep 6, 2011 at 6:21 PM, Yonik Seeley wrote: > On Tue, Sep 6, 2011 at 6:12 PM,   wrote: >> +* LUCENE-3418: Lucene was failing to fsync index files on commit, >> +  meaning a crash or power loss could easily c

behavior when fl contains a non-stored term.

I'm wondering if there's any utility in returning the first term of an un-stored but indexed field. It wouldn't be much use in a field that broke the input stream up, but what about a "string" type? Or something with KeywordTokenizer? We could save some index storage space, maybe speed up things

Re: Rollback to old index stored with SolrDeletionPolicy

This could easily be done outside of Solr, too. Ie create a standalone command-line tool that opens an IndexWriter on the index, using a custom DeletionPolicy that deletes the "future" commits. The TestDeletionPolicy#testOpenPriorSnapshot unit test (in oal.index) has an example of how to do this.

Re: behavior when fl contains a non-stored term.

Hi, You can use the FieldCache to pull the single value of a field for a given document ID. I'm unsure about whether what you're suggesting is a good idea, but it would need to be a custom extension to how fields are retrieved currently. IndexReader.document(int) visits fields which are stored a

[jira] [Updated] (LUCENE-1824) FastVectorHighlighter truncates words at beginning and end of fragments

[ https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi updated LUCENE-1824: --- Attachment: LUCENE-1824.patch Patch. I added test cases for sentence boundary and line bound

[jira] [Updated] (LUCENE-3412) SloppyPhraseScorer returns non-deterministic results for queries with many repeats

[ https://issues.apache.org/jira/browse/LUCENE-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doron Cohen updated LUCENE-3412: Attachment: LUCENE-3412.patch Attached patch with fix to this bug. The fix is rather simple, - ju

[jira] [Commented] (SOLR-2066) Search Grouping: support distributed search

[ https://issues.apache.org/jira/browse/SOLR-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098878#comment-13098878 ] Michael McCandless commented on SOLR-2066: -- The changes to modules/grouping look g

[jira] [Assigned] (LUCENE-2945) Surround Query doesn't properly handle equals/hashcode

[ https://issues.apache.org/jira/browse/LUCENE-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Hatcher reassigned LUCENE-2945: Assignee: Erik Hatcher (was: Grant Ingersoll) > Surround Query doesn't properly handle eq

[jira] [Commented] (LUCENE-2945) Surround Query doesn't properly handle equals/hashcode

[ https://issues.apache.org/jira/browse/LUCENE-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098882#comment-13098882 ] Erik Hatcher commented on LUCENE-2945: -- The current patch is for trunk only. I'll g

Re: How to best test possible performance impact of a new lucene patch

This sounds like a neat patch -- what changes are you exploring to Collector? These days when I need to test indexing or searching performance I usually use the Python scripts from here: https://hg.codespot.com/a/apache-extras.org/luceneutil Unfortunately they are rather involved to set up (

[jira] [Commented] (LUCENE-2308) Separately specify a field's type

[ https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098899#comment-13098899 ] Michael McCandless commented on LUCENE-2308: I guess it's OK to remove the au

[jira] [Commented] (LUCENE-2308) Separately specify a field's type

[ https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098904#comment-13098904 ] Michael McCandless commented on LUCENE-2308: Should we also move numeric(), n

Re: behavior when fl contains a non-stored term.

I'm more throwing this out there for discussion rather than implementing it. Frankly, I suspect there are better things to spend time on Erick On Wed, Sep 7, 2011 at 7:13 AM, Chris Male wrote: > Hi, > You can use the FieldCache to pull the single value of a field for a given > document ID. >

[jira] [Commented] (LUCENE-2945) Surround Query doesn't properly handle equals/hashcode

[ https://issues.apache.org/jira/browse/LUCENE-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098919#comment-13098919 ] Erik Hatcher commented on LUCENE-2945: -- Committed patch to trunk. Slight modified -

Re: How to best test possible performance impact of a new lucene patch

Ah thanks. I will make the change, ensure all tests are succeeding, add some tests of my own, and commit a patch. Would be great to get a feeling of the performance impact. The change I'm making is changing the Collector interface from public void collect(int doc) to public boolean collect(int doc

Re: How to best test possible performance impact of a new lucene patch

On Wed, Sep 7, 2011 at 9:09 AM, Anne Veling wrote: > Ah thanks. I will make the change, ensure all tests are succeeding, add some > tests of my own, and commit a patch. Would be great to get a feeling of the > performance impact. > The change I'm making is changing the Collector interface from > p

Re: How to best test possible performance impact of a new lucene patch

Yes, I saw that. I would expect that to be slower. It also would not always work as expected if the collector would be combined in a booleanquery I guess. Anne On Wed, Sep 7, 2011 at 15:29, Robert Muir wrote: > On Wed, Sep 7, 2011 at 9:09 AM, Anne Veling wrote: > > Ah thanks. I will make the c

Re: How to best test possible performance impact of a new lucene patch

I think that a boolean or enum as return value is neater (api wise) than throwing an expection. On 7 September 2011 15:34, Anne Veling wrote: > Yes, I saw that. I would expect that to be slower. It also would not always > work as expected if the collector would be combined in a booleanquery I >

Re: How to best test possible performance impact of a new lucene patch

its not slower: http://blogs.oracle.com/jrose/entry/longjumps_considered_inexpensive I don't understand the thing about the booleanquery. On Wed, Sep 7, 2011 at 9:34 AM, Anne Veling wrote: > Yes, I saw that. I would expect that to be slower. It also would not always > work as expected if the col

Re: How to best test possible performance impact of a new lucene patch

but its a per-document if for the normal case of ranked results, just to look "pretty" ?! On Wed, Sep 7, 2011 at 9:36 AM, Martijn v Groningen wrote: > I think that a boolean or enum as return value is neater (api wise) than > throwing an expection. > > On 7 September 2011 15:34, Anne Veling wrot

[jira] [Created] (SOLR-2746) Use the released UIMA addons 2.3.1 in Solr-UIMA

Use the released UIMA addons 2.3.1 in Solr-UIMA --- Key: SOLR-2746 URL: https://issues.apache.org/jira/browse/SOLR-2746 Project: Solr Issue Type: Improvement Affects Versions: 3.3 R

Re: How to best test possible performance impact of a new lucene patch

...but slower, as you have to check the return value millions of times. For this type of early exit conditions, exceptions are better, as they only change control flow if they are throwed. If you preallocate the exception, the time for fill-in stack trace is minimized. With Java 7 throwable has

[jira] [Commented] (LUCENE-2308) Separately specify a field's type

[ https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098957#comment-13098957 ] Chris Male commented on LUCENE-2308: I will make the appropriate javadoc changes righ

[jira] [Commented] (LUCENE-3237) FSDirectory.fsync() may not work properly

[ https://issues.apache.org/jira/browse/LUCENE-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098958#comment-13098958 ] Yonik Seeley commented on LUCENE-3237: -- The man pages on fsync (which I assume FileD

Re: How to best test possible performance impact of a new lucene patch

In that case it is better to keep the mechanism of throwing an exeption to stop a search. I was just thinking about the collector api and how Anne's change would look. On 7 September 2011 15:49, Uwe Schindler wrote: > ** ...but slower, as you have to check the return value millions of times. > F

[jira] [Resolved] (SOLR-2703) Add support for the Lucene Surround Parser

[ https://issues.apache.org/jira/browse/SOLR-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Hatcher resolved SOLR-2703. Resolution: Fixed Fix Version/s: 4.0 Simon - thanks for the work on this. I went back and ch

Re: How to best test possible performance impact of a new lucene patch

I agree we should not introduce a condition here. this extra branch is totally unnecessary. simon On Wed, Sep 7, 2011 at 3:49 PM, Uwe Schindler wrote: > ...but slower, as you have to check the return value millions of times. For > this type of early exit conditions, exceptions are better, as the

[jira] [Updated] (LUCENE-2308) Separately specify a field's type

[ https://issues.apache.org/jira/browse/LUCENE-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Male updated LUCENE-2308: --- Attachment: LUCENE-2308-FT-interface.patch New patch based on the feedback from Mike. - Field now i

RE: [Lucene.Net] 2.9.4

2.9.4 would make it in I assume because that will be our next official release. Sent from my Windows Phone -Original Message- From: Michael Herndon Sent: Wednesday, September 07, 2011 5:12 AM To: lucene-net-...@lucene.apache.org Subject: Re: [Lucene.Net] 2.9.4 > What version is going to

[jira] [Commented] (LUCENE-3410) Make WordDelimiterFilter's instantiation more readable

[ https://issues.apache.org/jira/browse/LUCENE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098972#comment-13098972 ] Robert Muir commented on LUCENE-3410: - any objections to backporting? we could then r

[jira] [Commented] (LUCENE-3410) Make WordDelimiterFilter's instantiation more readable

[ https://issues.apache.org/jira/browse/LUCENE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098976#comment-13098976 ] Chris Male commented on LUCENE-3410: None whatsoever. > Make WordDelimiterFilter's i

[jira] [Commented] (LUCENE-3410) Make WordDelimiterFilter's instantiation more readable

[ https://issues.apache.org/jira/browse/LUCENE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098980#comment-13098980 ] Robert Muir commented on LUCENE-3410: - I can take it if you want Chris, unless you wa

[jira] [Commented] (LUCENE-3237) FSDirectory.fsync() may not work properly

[ https://issues.apache.org/jira/browse/LUCENE-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098981#comment-13098981 ] Shai Erera commented on LUCENE-3237: It could be, and generally I think that it makes

[jira] [Commented] (LUCENE-3410) Make WordDelimiterFilter's instantiation more readable

[ https://issues.apache.org/jira/browse/LUCENE-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098982#comment-13098982 ] Chris Male commented on LUCENE-3410: Go for it! > Make WordDelimiterFilter's instant

Re: How to best test possible performance impact of a new lucene patch

I understand. The cost of the additional IF statements in the caller of the Collector would not outweigh the cost of throwing an Exception for these use cases Anne On Wed, Sep 7, 2011 at 16:00, Simon Willnauer < simon.willna...@googlemail.com> wrote: > I agree we should not introduce a condition

[jira] [Commented] (LUCENE-3418) Lucene is not fsync'ing files on commit

[ https://issues.apache.org/jira/browse/LUCENE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098994#comment-13098994 ] Robert Muir commented on LUCENE-3418: - {quote} but I'd love to somehow have a test th

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

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

[jira] [Commented] (LUCENE-3417) DictionaryCompoundWordTokenFilter does not properly add tokens from the end compound word.

[ https://issues.apache.org/jira/browse/LUCENE-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099000#comment-13099000 ] Robert Muir commented on LUCENE-3417: - thanks for the patch: all tests pass here with

Re: behavior when fl contains a non-stored term.

In solr/trunk, we could do this with a pseudo field/transformer: https://svn.apache.org/repos/asf/lucene/dev/trunk/solr/core/src/java/org/apache/solr/response/transform/ In trunk, you can return a function value -- but i'm not sure what the syntax for the 'fieldvalue' function would be. To use ot

[jira] [Commented] (LUCENE-3418) Lucene is not fsync'ing files on commit

[ https://issues.apache.org/jira/browse/LUCENE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099012#comment-13099012 ] Michael McCandless commented on LUCENE-3418: bq. Mike, just to make sure, di

[jira] [Commented] (LUCENE-3419) Resolve JUnit assert deprecations

[ https://issues.apache.org/jira/browse/LUCENE-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099018#comment-13099018 ] Michael McCandless commented on LUCENE-3419: Yay, nice cleanup! > Resolve JU

[jira] [Assigned] (SOLR-2746) Use the released UIMA addons 2.3.1 in Solr-UIMA

[ https://issues.apache.org/jira/browse/SOLR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi reassigned SOLR-2746: Assignee: Koji Sekiguchi > Use the released UIMA addons 2.3.1 in Solr-UIMA > ---

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

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/234/ No tests ran. Build Log (for compile errors): [...truncated 18001 lines...] - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands,

[jira] [Commented] (LUCENE-3418) Lucene is not fsync'ing files on commit

[ https://issues.apache.org/jira/browse/LUCENE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099102#comment-13099102 ] Michael McCandless commented on LUCENE-3418: I think we should turnaround a 3

[jira] [Commented] (SOLR-2700) transaction logging

[ https://issues.apache.org/jira/browse/SOLR-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099138#comment-13099138 ] Jason Rutherglen commented on SOLR-2700: I'm not sure how this feature makes any se

[jira] [Commented] (LUCENE-3418) Lucene is not fsync'ing files on commit

[ https://issues.apache.org/jira/browse/LUCENE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099142#comment-13099142 ] Simon Willnauer commented on LUCENE-3418: - bq. I think we should turnaround a 3.4

[jira] [Commented] (SOLR-2746) Use the released UIMA addons 2.3.1 in Solr-UIMA

[ https://issues.apache.org/jira/browse/SOLR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099144#comment-13099144 ] Steven Rowe commented on SOLR-2746: --- Hi Koji, I have done some of the work here, but I s

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099146#comment-13099146 ] Shay Banon commented on LUCENE-3416: The only reason its synchronized is because the

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099154#comment-13099154 ] Simon Willnauer commented on LUCENE-3416: - bq. The only reason its synchronized i

[jira] [Commented] (SOLR-2066) Search Grouping: support distributed search

[ https://issues.apache.org/jira/browse/SOLR-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099153#comment-13099153 ] Martijn van Groningen commented on SOLR-2066: - Thanks for the review! I'll upda

[jira] [Commented] (LUCENE-1824) FastVectorHighlighter truncates words at beginning and end of fragments

[ https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099157#comment-13099157 ] Robert Muir commented on LUCENE-1824: - Thanks for adding breakiterator implementation

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099160#comment-13099160 ] Shay Banon commented on LUCENE-3416: > this make no sense to me. If you don't want to

Re: svn commit: r1165869 - in /lucene/dev/trunk/solr: ./ core/src/java/org/apache/solr/core/ core/src/java/org/apache/solr/handler/ core/src/java/org/apache/solr/handler/component/ core/src/java/org/a

On Wed, Sep 7, 2011 at 1:53 PM, Simon Willnauer wrote: > wow - from you last comment on SOLR-2700 this commit comes kid of > unexpected. I did say in the previous comment "OK, I think we're getting close to committing now." Then I found a bug. Then I fixed it and committed. I felt more comfortab

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

The Maven configuration for the queryparser module was out of sync after merging in the XML query parser module (LUCENE-3286). Fix committed in revision 1166304. > -Original Message- > From: Apache Jenkins Server [mailto:jenk...@builds.apache.org] > Sent: Wednesday, September 07, 2011 12

[jira] [Commented] (SOLR-2700) transaction logging

[ https://issues.apache.org/jira/browse/SOLR-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099187#comment-13099187 ] Yonik Seeley commented on SOLR-2700: bq. I'm not sure how this feature makes any sense,

[JENKINS] Lucene-trunk - Build # 1670 - Still Failing

Build: https://builds.apache.org/job/Lucene-trunk/1670/ 2 tests failed. REGRESSION: org.apache.lucene.index.TestNRTThreads.testNRTThreads Error Message: java.lang.AssertionError: Some threads threw uncaught exceptions! Stack Trace: java.lang.RuntimeException: java.lang.AssertionError: Some thre

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099195#comment-13099195 ] Simon Willnauer commented on LUCENE-3416: - bq. Reading a volatile var in x86 is n

[jira] [Updated] (SOLR-2746) Use the released UIMA addons 2.3.1 in Solr-UIMA

[ https://issues.apache.org/jira/browse/SOLR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Rowe updated SOLR-2746: -- Attachment: SOLR-2746.patch Here is a patch for trunk. I got the replacement binary jars from [http://

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099210#comment-13099210 ] Michael McCandless commented on LUCENE-3416: I made setMaxMergeWriteMBPerSec

Re: JCC crash when building

I'm sorry, I'm not ignoring you, but since I don't run Windows much and mingw not at all, I can't help you. It is very likely you've got some DLLs mixed up indeed. Maybe someone with mingw experience here can chime in ? Andi.. On Tue, 6 Sep 2011, Petrus Hyvönen wrote: Hi again, python -m

[jira] [Created] (LUCENE-3420) assertion derived class modifier from parent class silently breaks backward compatibility

assertion derived class modifier from parent class silently breaks backward compatibility - Key: LUCENE-3420 URL: https://issues.apache.org/jira/browse/LUCENE-3420

[jira] [Commented] (LUCENE-3420) assertion derived class modifier from parent class silently breaks backward compatibility

[ https://issues.apache.org/jira/browse/LUCENE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099227#comment-13099227 ] Yonik Seeley commented on LUCENE-3420: -- Hmmm, yeah. Perhaps this assert should have

[jira] [Updated] (SOLR-2746) Use the released UIMA addons 2.3.1 in Solr-UIMA

[ https://issues.apache.org/jira/browse/SOLR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Rowe updated SOLR-2746: -- Fix Version/s: 3.5 > Use the released UIMA addons 2.3.1 in Solr-UIMA > -

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099233#comment-13099233 ] Shay Banon commented on LUCENE-3416: I agree with Mike, I think it should remain sync

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099235#comment-13099235 ] Simon Willnauer commented on LUCENE-3416: - what about something like that: {code

[jira] [Commented] (SOLR-2700) transaction logging

[ https://issues.apache.org/jira/browse/SOLR-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099239#comment-13099239 ] Jason Rutherglen commented on SOLR-2700: This is going to best be amazing, I wonder

[jira] [Commented] (LUCENE-3420) assertion derived class modifier from parent class silently breaks backward compatibility

[ https://issues.apache.org/jira/browse/LUCENE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099241#comment-13099241 ] Robert Muir commented on LUCENE-3420: - {quote} This silently breaks backward compatib

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099242#comment-13099242 ] Michael McCandless commented on LUCENE-3416: That change looks fine to me Sim

[jira] [Commented] (LUCENE-3418) Lucene is not fsync'ing files on commit

[ https://issues.apache.org/jira/browse/LUCENE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099245#comment-13099245 ] Mark Miller commented on LUCENE-3418: - bq. I think we should turnaround a 3.4.0 relea

[jira] [Created] (LUCENE-3421) PayloadTermQuery's explain is broken when span score is

PayloadTermQuery's explain is broken when span score is Key: LUCENE-3421 URL: https://issues.apache.org/jira/browse/LUCENE-3421 Project: Lucene - Java Issue Type: Bug Compon

[VOTE] Release Lucene/Solr 3.4.0

Please vote to release the artifacts at: http://people.apache.org/~mikemccand/staging_area/lucene-solr-3.4.0-RC0-rev1166318 as Lucene 3.4.0 and Solr 3.4.0. Mike http://blog.mikemccandless.com - To unsubscribe, e-mail: dev-u

[jira] [Updated] (LUCENE-3421) PayloadTermQuery's explain is broken when span score is not included

[ https://issues.apache.org/jira/browse/LUCENE-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Drapkin updated LUCENE-3421: --- Summary: PayloadTermQuery's explain is broken when span score is not included (was: Payload

Re: [VOTE] Release Lucene/Solr 3.4.0

We have to add a changes.txt for the numeric flexible queryparser, I think this is still missing. Adriano? -- Uwe Schindler H.-H.-Meier-Allee 63, 28213 Bremen http://www.thetaphi.de Michael McCandless schrieb: Please vote to release the artifacts at: http://people.apache.org/~mikemccand/stag

Re: JCC crash when building

Thanks, I tried now to uninstall Java 7 completely, and recompile JCC, same problem. I should maybe mention that I'm on 64-bit Windows 7, and a 32 bit python (python xy) Regards /Petrus On Wed, Sep 7, 2011 at 9:04 PM, Andi Vajda wrote: > > I'm sorry, I'm not ignoring you, but since I don't ru

[jira] [Commented] (LUCENE-3416) Allow to pass an instance of RateLimiter to FSDirectory allowing to rate limit merge IO across several directories / instances

[ https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099287#comment-13099287 ] Shay Banon commented on LUCENE-3416: I must say that I am at a lost in trying to unde

[jira] [Commented] (LUCENE-3418) Lucene is not fsync'ing files on commit

[ https://issues.apache.org/jira/browse/LUCENE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099285#comment-13099285 ] Erick Erickson commented on LUCENE-3418: File corruptions really scare me, +1 >

[jira] [Created] (SOLR-2747) Include formatted Changes.html for release

Include formatted Changes.html for release -- Key: SOLR-2747 URL: https://issues.apache.org/jira/browse/SOLR-2747 Project: Solr Issue Type: Improvement Reporter: Martijn van Groningen

[jira] [Updated] (SOLR-2747) Include formatted Changes.html for release

[ https://issues.apache.org/jira/browse/SOLR-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martijn van Groningen updated SOLR-2747: Fix Version/s: 4.0 > Include formatted Changes.html for release > --

[jira] [Commented] (LUCENE-3420) assertion derived class modifier from parent class silently breaks backward compatibility

[ https://issues.apache.org/jira/browse/LUCENE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099298#comment-13099298 ] Uwe Schindler commented on LUCENE-3420: --- The problem behind the checks is that they

[jira] [Commented] (LUCENE-3420) assertion derived class modifier from parent class silently breaks backward compatibility

[ https://issues.apache.org/jira/browse/LUCENE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099306#comment-13099306 ] John Wang commented on LUCENE-3420: --- Maybe it is just my lack of understanding why the

[jira] [Commented] (SOLR-2366) Facet Range Gaps

[ https://issues.apache.org/jira/browse/SOLR-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099315#comment-13099315 ] Hoss Man commented on SOLR-2366: Jan: i took a look at r3 of your VariableRangeGaps wiki, h

[JENKINS] Lucene-Solr-tests-only-3.x-java7 - Build # 397 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x-java7/397/ 1 tests failed. REGRESSION: org.apache.lucene.index.TestIndexWriter.testThreadInterruptDeadlock Error Message: null Stack Trace: junit.framework.AssertionFailedError: at org.apache.lucene.util.LuceneTestCaseRun

[jira] [Commented] (LUCENE-3420) assertion derived class modifier from parent class silently breaks backward compatibility

[ https://issues.apache.org/jira/browse/LUCENE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099317#comment-13099317 ] Uwe Schindler commented on LUCENE-3420: --- Most of this is explained in the related i

[jira] [Created] (SOLR-2748) autocommit commits too many times

autocommit commits too many times - Key: SOLR-2748 URL: https://issues.apache.org/jira/browse/SOLR-2748 Project: Solr Issue Type: Bug Reporter: Yonik Seeley autocommit seems to commit more freque

[jira] [Updated] (LUCENE-3420) assertion derived class modifier from parent class silently breaks backward compatibility

[ https://issues.apache.org/jira/browse/LUCENE-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated LUCENE-3420: -- Attachment: LUCENE-3420.patch Here a patch that the assertion status of the actual class is us

[jira] [Assigned] (SOLR-2746) Use the released UIMA addons 2.3.1 in Solr-UIMA

[ https://issues.apache.org/jira/browse/SOLR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi reassigned SOLR-2746: Assignee: Steven Rowe (was: Koji Sekiguchi) Thanks, Steven! > Use the released UIMA addons

[jira] [Commented] (SOLR-1123) Change the JSONResponseWriter content type

[ https://issues.apache.org/jira/browse/SOLR-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099577#comment-13099577 ] Neil Hooey commented on SOLR-1123: -- Can we revive this issue? Does anyone have a patch fo

Re: behavior when fl contains a non-stored term.

: In trunk, you can return a function value -- but i'm not sure what the : syntax for the 'fieldvalue' function would be. To use other : functions, you just put it in the list: : &fl=name,id,ord(id) it's field("name_of_field_as_quoted_string") ...but i'm not sure how the DocTransformer code d

[jira] [Commented] (SOLR-2748) autocommit commits too many times

[ https://issues.apache.org/jira/browse/SOLR-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099598#comment-13099598 ] Yonik Seeley commented on SOLR-2748: So I think the culprit might be CommitTracker.run(

[jira] [Updated] (LUCENE-1824) FastVectorHighlighter truncates words at beginning and end of fragments

[ https://issues.apache.org/jira/browse/LUCENE-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Sekiguchi updated LUCENE-1824: --- Attachment: LUCENE-1824.patch Good point. The simpler version is attached. Still working...

[jira] [Commented] (SOLR-2748) autocommit commits too many times

[ https://issues.apache.org/jira/browse/SOLR-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099613#comment-13099613 ] Yonik Seeley commented on SOLR-2748: Hmmm, I'm not quite understanding the logic of thi

[jira] [Issue Comment Edited] (SOLR-2748) autocommit commits too many times

[ https://issues.apache.org/jira/browse/SOLR-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099613#comment-13099613 ] Yonik Seeley edited comment on SOLR-2748 at 9/7/11 10:17 PM: - H

[jira] [Commented] (LUCENE-1768) NumericRange support for new query parser

[ https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099626#comment-13099626 ] Uwe Schindler commented on LUCENE-1768: --- Hi Vinicius, any news for trunk? We want t

[jira] [Commented] (LUCENE-3412) SloppyPhraseScorer returns non-deterministic results for queries with many repeats

[ https://issues.apache.org/jira/browse/LUCENE-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099627#comment-13099627 ] Michael Ryan commented on LUCENE-3412: -- Thanks, Doron. I've tried applying your patc

[jira] [Updated] (LUCENE-3421) PayloadTermQuery's explain is broken when span score is not included

[ https://issues.apache.org/jira/browse/LUCENE-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-3421: Attachment: LUCENE-3421.patch patch, with some tests showing the bug. i also simplified some out

RE: [VOTE] Release Lucene/Solr 3.4.0

I added the missing changes.txt entries to the branch. This all went too fast J (I am still on vacation…) - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de From: Uwe Schindler [mailto:u...@thetaphi.de] Se

[jira] [Commented] (SOLR-2748) autocommit commits too many times

[ https://issues.apache.org/jira/browse/SOLR-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099675#comment-13099675 ] Yonik Seeley commented on SOLR-2748: Another interesting thing I ran into reviewing thi

  1   2   >