Re: [VOTE] Lucene and Solr 3.1 release candidate

2011/3/14 slaava slaav...@gmail.com: Hi, when could we expect final 3.1 version with maven-repository? We need some functionality included in 3.1 and I don't know if I have to wait or create own maven project from sources... Hi, I hope soon as well, in the meantime we've been testing with the

Re: IndexReader.indexExists declares throwing IOE, but never does

2011/3/21 Earwin Burrfoot ear...@gmail.com: Technically, there's a big difference between I checked, and there was no index, and I was unable to check the disk because file system went BANG!. So the proper behaviour is to return false IOE (on proper occasion)? +1 to throw the exception when

Re: IndexReader.indexExists declares throwing IOE, but never does

, 2011 at 4:12 PM, Sanne Grinovero sanne.grinov...@gmail.com wrote: 2011/3/21 Earwin Burrfoot ear...@gmail.com: Technically, there's a big difference between I checked, and there was no index, and I was unable to check the disk because file system went BANG!. So the proper behaviour

Re: Index File

Hi, 2011/3/21 soheila dehghanzadeh sally...@gmail.com: Hi All, I have created Index folder, and i tried to open .CFS,.CFX,.GEN, segments file with notpad . but they are unreadable. i want to see their structure for my sample directory which i have passed to Indexfiles . ihave red this

Re: Code Freeze on realtime_search branch

Hello, this is totally awesome! Does it imply we don't need the IndexWriter lock anymore? And hence that people sharing the Lucene Directory across multiple JVMs can have both write at the same time? I had intentions to *try* removing such limitations this summer, but if this is the case I will

Re: Code Freeze on realtime_search branch

of those participant threads in the remote nodes. I'll keep you updated, but unfortunately can't start working on it sooner. Sanne http://blog.mikemccandless.com On Fri, Apr 29, 2011 at 2:16 PM, Sanne Grinovero sanne.grinov...@gmail.com wrote: Hello, this is totally awesome! Does it imply we

Re: [VOTE] release 3.3 (take two)

+1 All tests are fine on both Infinispan and Hibernate Search. While I understand that often APIs needed changes, I'm very happy to state that for the first time three mayor releases are fully API compatible! (As far as tested on these projects, Lucene versions 3.1.0, 3.2.0, 3.3.0 are drop-in

Re: [VOTE] Drop Java 5 support for trunk (Lucene 4.0)

+1 Sanne 2011/6/27 Michael McCandless luc...@mikemccandless.com: +1 Mike McCandless http://blog.mikemccandless.com On Mon, Jun 27, 2011 at 1:38 PM, Simon Willnauer simon.willna...@googlemail.com wrote: This issue has been discussed on various occasions and lately on LUCENE-3239

Re: [VOTE] Release Lucene/Solr 3.4.0, RC1

+1 all tests on all Lucene-using projects I contribute to pass without any change needed (a sure sign I should add more...). Once more, great work and thank so much to everyone involved. Sanne On 11 September 2011 16:11, Robert Muir rcm...@gmail.com wrote: +1, thanks for creating this release

Re: Source Control

If Lucene was moved to use GIT, I would love that. Not going into details now, but having used GIT for two years on other open source projects I'm pretty sure that it makes collaboration significantly easier. We use GitHub, but the star is GIT: GitHub makes it easier for non-power users and is

Re: ideas for alphas/betas?

On 7 March 2012 15:42, Tommaso Teofili tommaso.teof...@gmail.com wrote: 2012/3/7 Robert Muir rcm...@gmail.com On Tue, Mar 6, 2012 at 1:42 AM, Shai Erera ser...@gmail.com wrote: I agree. Maybe we should also tag issues as 4.0-alpha, 4.0-beta in JIRA? For 4.0-alpha we'll tag all the

Re: wind down for 3.1?

Hello all, Is there any update on the 3.1 status? I'm really looking forward to it :) Regards, Sanne 2011/2/16 Chris Hostetter hossman_luc...@fucit.org: : 1. javadocs warnings/errors: this is a constant battle, its worth : considering if the build should actually fail if you get one of

Re: wind down for 3.1?

2011/3/3 Robert Muir rcm...@gmail.com: On Thu, Mar 3, 2011 at 7:43 AM, Sanne Grinovero sanne.grinov...@gmail.com wrote: Hello all, Is there any update on the 3.1 status? I'm really looking forward to it :) Yes, we are currently in the feature freeze, but it seems to be coming in shape

Re: [VOTE] Lucene and Solr 3.1 release candidate

Hello, the lucene-solr-grandparent pom [1] file mentions a jetty version 6.1.26-patched-JETTY-1340 which is not available in the repositories where I would expect it. Do I need to enable some additional repository? This seems related to SOLR-2381. I think for people using Solr as their

Re: [VOTE] Lucene and Solr 3.1 release candidate

all aware of it and making a conscious decision, I don't think waiting for a Jetty release is a reasonable option, but I'd add at least a warning in the release notes. Regards, Sanne -Original Message- From: Sanne Grinovero [mailto:sanne.grinov...@gmail.com] Sent: Tuesday, March 08

Infinispan JGroups migrating to Apache License

Hello all, as some of you already know the Infinispan project includes several integration points with the Apache Lucene project, including a Directory implementation, but so far we had a separate community because of the license incompatibility. I'm very happy to announce now that both

Re: Indexing file with security problem

To be honest I am not familiar with ManifoldCF, so I won't say if Hibernate Search is better or not, but it would definitely not be too hard with Hibernate Search: 1) You annotate with @Indexed the entity referring to your PostgreSQL table containing the metadata; with @TikaBridge you point it to

Re: VOTE: release 3.6.2

+1 tested the Maven artifacts with the testsuites from Infinispan and Hibernate Search On 21 December 2012 13:22, Tommaso Teofili tommaso.teof...@gmail.com wrote: +1 Tommaso 2012/12/21 Simon Willnauer simon.willna...@gmail.com same here +1 On Fri, Dec 21, 2012 at 1:11 PM, Martijn v

Re: The Old Git Discussion

+1 David and Mark I also like Lajos have - very sadly - not contributed as much as I'd want to Lucene, but having followed this thread with interest for a while, I hope my contribution is well received. I do sympathize with all the problems which have been highlighted about Git as I've had the

Re: [VOTE] Release Lucene/Solr 4.6.1 RC1

+1 Run integration tests with: - Hibernate Search - Infinispan (indexing/searching entries with Lucene) - Infinispan (storing indexes from Lucene) All perfect, great job! (For long we've been stuck on Lucene 3.x but that's finally resolved) Sanne On 18 January 2014 01:51, Steve Rowe

Re: [VOTE] Lucene / Solr 4.6.0 Take 3

+1 On 20 November 2013 18:00, Tommaso Teofili tommaso.teof...@gmail.com wrote: +1 Tommaso 2013/11/20 Jan Høydahl jan@cominvent.com +1 Happy smoketester on Mac -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 19. nov. 2013 kl. 15:11 skrev Simon

Re: [VOTE] Move trunk to Java 8

Unrelated for the vote, but since it came up: Oracle isn't the only large corporation to employ high calibre skilled committers on the OpenJDK project. Oracle decides support of its own builds on its own terms, but Red Hat for example supports the JVM for much longer to its customers, and being an

Re: Welcome Anshum Gupta to the PMC

Congratulations Anshum! Regards, Sanne - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Optimisations proposal for FacetsConfig

ate a user > ID on the JIRA system, but that's a "self-serve" option. > > Best, > Erick > > On Mon, Nov 23, 2015 at 8:21 AM, Sanne Grinovero > <sanne.grinov...@gmail.com> wrote: >> Hello all, >> I was looking into the source code for >> org.apach

Optimisations proposal for FacetsConfig

Hello all, I was looking into the source code for org.apache.lucene.facet.FacetsConfig as it's being highlighted as an hotspot of allocations during a performance analysis session. Our code was allocating a new instance of FacetsConfig for each Document being built; there are several maps being

Re: Moving Lucene / Solr from SVN to Git

Thanks for finally switching, I have been looking forward to this. I've been doing release management and generally helping with the switch from SVN to Git for the Hibernate project in the past 5 years, so I'm happy to share hints and tips from our experience there. Feel free to ask me for help

Re: [VOTE] Release Lucene/Solr 5.5.2 RC2

+1 [from the Hibernate Search integration testsuite] On 22 June 2016 at 06:35, Shalin Shekhar Mangar wrote: > +1 > > SUCCESS! [2:19:37.075305] > > On Tue, Jun 21, 2016 at 10:18 PM, Steve Rowe wrote: >> >> Please vote for release candidate 2 for

Re: Congratulations to the new Lucene/Solr PMC Chair, Tommaso Teofili

That's great, congratulations!

Re: [VOTE] Release Lucene/Solr 5.3.2-RC1

Since the release had passed, could we please get further fixes in further micro versions? I'm looking forward for Lucene 5.3.2 for the other fixes it brings already. On 15 January 2016 at 17:03, Yonik Seeley wrote: > On Fri, Jan 15, 2016 at 11:34 AM, Erick Erickson >

Re: [VOTE] Release Lucene/Solr 5.5.5 RC2

SUCCESS! [1:15:56.228143] +1 Thanks! Sanne On 20 October 2017 at 16:28, Steve Rowe wrote: > Please vote for release candidate 2 for Lucene/Solr 5.5.5 > > The artifacts can be downloaded from: >

Lock API, throwing IOException

using the resource. */ public abstract boolean isLocked(); not throwing an IOException as other methods do? Could you please add it? It looks like it should be trivial, as all clients of this API are already declaring to throw the same Exception. Regards, Sanne Grinovero

Re: Lock API, throwing IOException

Thanks a lot! This makes error management much simpler. Sanne 2009/11/1 Michael McCandless luc...@mikemccandless.com: OK, this makes sense.  I'll add it. Mike On Sat, Oct 31, 2009 at 9:43 AM, Sanne Grinovero sanne.grinov...@gmail.com wrote: Hello, I'm implementing a distributed directory

Re: A new Lucene Directory available

-John On Sat, Nov 14, 2009 at 11:44 AM, Sanne Grinovero s.grinov...@sourcesense.com wrote: Hello all, I'm a Lucene user and fan, I wanted to tell you that we just released a first technology preview of a distributed in memory Directory for Lucene. The release announcement: http

Re: A new Lucene Directory available

, Lukas http://blog.lukas-vlcek.com/ On Sun, Nov 15, 2009 at 5:33 AM, Sanne Grinovero s.grinov...@sourcesense.com wrote: Hi John, I didn't run a long running reliable benchmark, so at the moment I can't really speak of numbers. Suggestions and help on performance testing are welcome: I

Re: A new Lucene Directory available

, Sanne Grinovero s.grinov...@sourcesense.com wrote: Hi John, I didn't run a long running reliable benchmark, so at the moment I can't really speak of numbers. Suggestions and help on performance testing are welcome: I guess it will shine in some situations, not necessarily all, so really

Re: A new Lucene Directory available

- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org -- Sanne Grinovero Sourcesense - making sense of Open Source: http://www.sourcesense.com

StressTest: Document not guaranteed to be found after write and commit

same behavior on 2.4.1. Best regards, Sanne Grinovero P.S. congratulations with the release of 3.0.0 :-) lucene-stresstest.patch Description: Binary data - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org

Re: StressTest: Document not guaranteed to be found after write and commit

an issue attach this as a patch?  Thanks. Mike On Wed, Nov 25, 2009 at 12:30 PM, Sanne Grinovero sanne.grinov...@gmail.com wrote: Hello, I developed a stress test to assert that a new document containing a specific term X is always found after a commit on the IndexWriter. This works most

Re: Socket and file locks

Hello, Together with the Infinispan Directory we developed such a LockFactory; I'd me more than happy if you wanted to add some pointers to it in the Lucene documention/readme. This depends on Infinispan for multiple-machines communication (JGroups, indirectly) but it's not required to use an

Re: Socket and file locks

) for interesting LockFactory implementations/tradeoffs, and add this there? Mike On Sat, Nov 28, 2009 at 9:26 AM, Sanne Grinovero sanne.grinov...@gmail.com wrote: Hello, Together with the Infinispan Directory we developed such a LockFactory; I'd me more than happy if you wanted to add some

nightly build deploy to Maven repositories

Hello, I'm needing to depend on some recently committed bugfix from Lucene's 2.9 branch in other OSS projects, using Maven2 for dependency management. Are there snapshots uploaded somewhere regularly? Could Hudson do that? Looking into Hudson it appears that it regularly builds trunk; wouldn't it

Re: Lucene 2.4.1 src .zip issue

, Sanne Grinovero 2009/12/10 Erik Hatcher erik.hatc...@gmail.com: I was doing some research on past releases of Lucene and downloaded the archived 2.4.1 src .zip and got this: ~/Downloads: unzip lucene-2.4.1-src.zip Archive:  lucene-2.4.1-src.zip  End-of-central-directory signature not found

Re: nightly build deploy to Maven repositories

I would be happy with 3.0.1-SNAPSHOT too, that will also fix my problem. Will I have to wait for next release before I can share my patches? Best Regards, Sanne Grinovero 2009/12/3 Sanne Grinovero sanne.grinov...@gmail.com: Hello, I'm needing to depend on some recently committed bugfix from

Re: update doc by query

If the demand is the problem: I would really love that: in most scenarios a single term is not enough to identify a Document: I need at least two so I use usually remove-by-query first and then add again. This sometimes needs some application level lock to make the changes consistent. Sanne

Re: update doc by query

delete by query, then add? Back when IW had autoCommit=true, it was compelling to have an atomic update, but now with only autoCommit=false, the app has full control over visibility to readers, so do we even need update-by-term anymore? Mike On Sun, Jan 10, 2010 at 2:13 PM, Sanne Grinovero

Re: update doc by query

Then I wouldn't need it and can still improve performance by using periodic commits, nice! thanks for explaining this, Sanne On Mon, Jan 11, 2010 at 10:57 AM, Michael McCandless luc...@mikemccandless.com wrote: On Sun, Jan 10, 2010 at 6:13 PM, Sanne Grinovero s.grinov...@sourcesense.com wrote

Re: Lucene 2.9.0 Near Real Time Indexing and lock timeouts

A common error I see is that people assume the IndexWriter to be not threadsafe, and open several different instances. You should use just one IndexWriter, keep it open and flush periodically (not commit at each add operation), and read the Lucene wiki pages about the IndexWriter settings like

Re: Lucene memory consumption

Hello Frederic, I'm CCing java-dev@lucene.apache.org as Michael McCandless has been very helpful on IRC in discussing the ThreadLocal implication, and it would be nice you could provide first-hand information. There's a good reading to start from at

Having a default constructor in Analyzers

Hello, I've seen that some core Analyzers are now missing a default constructor; this is preventing many applications to configure/load Analyzers by reflection, which is a common use case to have Analyzers chosen in configuration files. Would it be possible to add, for example, a constructor like

Re: Having a default constructor in Analyzers

newInstance() on it, not directly on the Class. It's just one line of code more. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: Sanne Grinovero [mailto:sanne.grinov...@gmail.com] Sent: Sunday

Re: Having a default constructor in Analyzers

be done step by step. Yet, if we deprecate LUCENE_CURRENT people will use it for at least the next 3 to 5 years (until 4.0) anyway :) simon On Sun, Feb 7, 2010 at 8:17 PM, Sanne Grinovero sanne.grinov...@gmail.com wrote: Thanks for all the quick answers; finding the ctor having only

Re: Having a default constructor in Analyzers

2010/2/8 Robert Muir rcm...@gmail.com: 8 snip 8 how would this work when the Query analyzer differs from the Index analyzer? For example, using commongrams in solr means you use a different Query analyzer from Index analyzer, and there are some other use cases even in solr (synonyms

Re: Having a default constructor in Analyzers

Hi Uwe, yes Hibernate is definitely recommending the Solr way for normal and power users, but we're also taking care of beginners trying it out for the first time it should just work out of the box for a simple POC, in those cases an Analyzer is defined as global analyzer (used for all cases

Re: Proposal about Version API relaxation

Hello, I think some compatibility breaks should really be accepted, otherwise these requirements are going to kill the technological advancement: the effort in backwards compatibility will grow and be more timeconsuming and harder every day. A mayor release won't happen every day, likely not even

Re: Proposal about Version API relaxation

+1 on the Analyzers split, But would like to point out that it's not very different than having a non final static version field. Just a much better solution as you keep your code manageable. 2010/4/15 Grant Ingersoll gsing...@apache.org: On Apr 15, 2010, at 4:21 PM, Shai Erera wrote: +1 on

Re: Solr 1.5 - The Cloud Edition!

Hello Yonik, that's very interesting, I'm working since some time on the Infinispan based Lucene Directory, have you seen my announcement on dev-lucene? I didn't dare to cross-post. Again the link: http://www.jboss.org/community/wiki/InfinispanasaDirectoryforLucene It's an implementation to

Re: Upgrading Lucene jars

Why is Solr not depending directly on Lucene but repackaging the same classes? Sorry I've probably missed some important discussion. Whatever the reason for this decision, is it still a good reason? This gets new users in a hell of trouble sometimes, as some applications introduce Solr after

Re: Upgrading Lucene jars

should take care of this but it's actually giving a false feeling of confidence in this case. Regards, Sanne 2009/12/9 Shalin Shekhar Mangar shalinman...@gmail.com: On Wed, Dec 9, 2009 at 3:33 PM, Sanne Grinovero sanne.grinov...@gmail.comwrote: Why is Solr not depending directly on Lucene

Re: svn commit: r899979 - /lucene/solr/trunk/example/solr/conf/solrconfig.xml

thanks for the heads-up, this is good to know. I've updated http://wiki.apache.org/lucene-java/AvailableLockFactories which I recently created as a guide to help in choosing between different LockFactories. I believe the Native LockFactory is very useful, I wouldn't consider this a bug nor

[jira] Created: (LUCENE-2585) DirectoryReader.isCurrent might fail to see the segments file during concurrent index changes

Project: Lucene - Java Issue Type: Bug Components: Index Affects Versions: 3.0.2, 3.0.1, 3.0, 2.9.3 Reporter: Sanne Grinovero Fix For: 2.9.4, 3.0.3, 3.1 I could reproduce the issue several times but only by running long and stressfull

[jira] Commented: (LUCENE-2585) DirectoryReader.isCurrent might fail to see the segments file during concurrent index changes

[ https://issues.apache.org/jira/browse/LUCENE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895027#action_12895027 ] Sanne Grinovero commented on LUCENE-2585: - I'm going to see if I can contribute

[jira] Commented: (LUCENE-2585) DirectoryReader.isCurrent might fail to see the segments file during concurrent index changes

[ https://issues.apache.org/jira/browse/LUCENE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895059#action_12895059 ] Sanne Grinovero commented on LUCENE-2585: - sure, the test is totally open source

[jira] Updated: (LUCENE-2585) DirectoryReader.isCurrent might fail to see the segments file during concurrent index changes

[ https://issues.apache.org/jira/browse/LUCENE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanne Grinovero updated LUCENE-2585: Description: I could reproduce the issue several times but only by running long

[jira] Issue Comment Edited: (LUCENE-2585) DirectoryReader.isCurrent might fail to see the segments file during concurrent index changes

[ https://issues.apache.org/jira/browse/LUCENE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12895059#action_12895059 ] Sanne Grinovero edited comment on LUCENE-2585 at 8/3/10 6:26 PM

[jira] [Commented] (LUCENE-5541) FileExistsCachingDirectory, to work around unreliable File.exists

[ https://issues.apache.org/jira/browse/LUCENE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14130172#comment-14130172 ] Sanne Grinovero commented on LUCENE-5541: - Hi [~mikemccand], I think I'm hitting

[jira] [Commented] (LUCENE-5541) FileExistsCachingDirectory, to work around unreliable File.exists

[ https://issues.apache.org/jira/browse/LUCENE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14133804#comment-14133804 ] Sanne Grinovero commented on LUCENE-5541: - Thanks Michael, [~gustavonalle] from

[jira] [Commented] (LUCENE-5569) Rename AtomicReader to LeafReader

[ https://issues.apache.org/jira/browse/LUCENE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14291720#comment-14291720 ] Sanne Grinovero commented on LUCENE-5569: - As a heavy Lucene consumer I probably

[jira] [Commented] (LUCENE-6212) Remove IndexWriter's per-document analyzer add/updateDocument APIs

[ https://issues.apache.org/jira/browse/LUCENE-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608407#comment-14608407 ] Sanne Grinovero commented on LUCENE-6212: - Hi Adrien, thanks for replying! Yes I

[jira] [Commented] (LUCENE-6212) Remove IndexWriter's per-document analyzer add/updateDocument APIs

[ https://issues.apache.org/jira/browse/LUCENE-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608156#comment-14608156 ] Sanne Grinovero commented on LUCENE-6212: - Hello, I understand there are good

[jira] [Created] (LUCENE-6909) Improve concurrency for FacetsConfig

Sanne Grinovero created LUCENE-6909: --- Summary: Improve concurrency for FacetsConfig Key: LUCENE-6909 URL: https://issues.apache.org/jira/browse/LUCENE-6909 Project: Lucene - Core Issue

[jira] [Updated] (LUCENE-6909) Improve concurrency for FacetsConfig

[ https://issues.apache.org/jira/browse/LUCENE-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanne Grinovero updated LUCENE-6909: Attachment: 0001-LUCENE-6909-Allow-efficient-concurrent-usage-of-a-Fa.patch Trivial patch

[jira] [Commented] (LUCENE-6909) Improve concurrency for FacetsConfig

[ https://issues.apache.org/jira/browse/LUCENE-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026929#comment-15026929 ] Sanne Grinovero commented on LUCENE-6909: - Hi [~mikemccand]! Thanks for checking. Yes, of course

[jira] [Commented] (LUCENE-6909) Improve concurrency for FacetsConfig

[ https://issues.apache.org/jira/browse/LUCENE-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15027261#comment-15027261 ] Sanne Grinovero commented on LUCENE-6909: - Thanks! > Improve concurrency for FacetsCon

[jira] [Commented] (LUCENE-7058) Add getters for the properties of several Query implementations

[ https://issues.apache.org/jira/browse/LUCENE-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15177928#comment-15177928 ] Sanne Grinovero commented on LUCENE-7058: - Great, that's very handy! Thanks all for the speedy

[jira] [Commented] (LUCENE-6989) Implement MMapDirectory unmapping for coming Java 9 changes

[ https://issues.apache.org/jira/browse/LUCENE-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15659554#comment-15659554 ] Sanne Grinovero commented on LUCENE-6989: - Hi all, is there an update on this? I see several

[jira] [Commented] (LUCENE-6989) Implement MMapDirectory unmapping for coming Java 9 changes

[ https://issues.apache.org/jira/browse/LUCENE-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15752649#comment-15752649 ] Sanne Grinovero commented on LUCENE-6989: - We have more recent releases of Hibernate Search using

[jira] Commented: (LUCENE-1329) Remove synchronization in SegmentReader.isDeleted

[ https://issues.apache.org/jira/browse/LUCENE-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611572#action_12611572 ] Sanne Grinovero commented on LUCENE-1329: - Adding a readonly IndexReader would

[jira] Created: (LUCENE-2095) Document not guaranteed to be found after write and commit

Components: Index Affects Versions: 2.9.1, 2.4.1 Environment: Linux 64bit Reporter: Sanne Grinovero after same email on developer list: I developed a stress test to assert that a new document containing a specific term X is always found after a commit on the IndexWriter

[jira] Updated: (LUCENE-2095) Document not guaranteed to be found after write and commit

[ https://issues.apache.org/jira/browse/LUCENE-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanne Grinovero updated LUCENE-2095: Attachment: lucene-stresstest.patch attaching the testcase, apply to version 2.9.1. It's

[jira] Commented: (LUCENE-2095) Document not guaranteed to be found after write and commit

[ https://issues.apache.org/jira/browse/LUCENE-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12785943#action_12785943 ] Sanne Grinovero commented on LUCENE-2095: - Thanks a lot Michael, this makes my