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 <sar...@gmail.com> wrote: > Please vote for release candidate 2 for Lucene/Solr 5.5.5 > > The artifacts can be downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/luc

[GitHub] lucene-solr pull request #263: Backporting of SOLR-11477 on branch_5_5

Github user Sanne closed the pull request at: https://github.com/apache/lucene-solr/pull/263 --- - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

[GitHub] lucene-solr issue #263: Backporting of SOLR-11477 on branch_5_5

Github user Sanne commented on the issue: https://github.com/apache/lucene-solr/pull/263 Thanks @sarowe ! closing --- - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev

[GitHub] lucene-solr pull request #263: Backporting of SOLR-11477 on branch_5_5

GitHub user Sanne opened a pull request: https://github.com/apache/lucene-solr/pull/263 Backporting of SOLR-11477 on branch_5_5 This is an adaptation of last weeks' security fix SOLR-11477 by (Michael Stepankin, Olga Barinova, Uwe Schindler, Christine Poerschke) (aka

[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-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

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!

[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

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: Moving Lucene / Solr from SVN to Git

when reading the tutorials and references, don't be afraid to type commands and check the results. Thanks, Sanne On 11 January 2016 at 09:33, Jan Høydahl <jan@cominvent.com> wrote: > All discussion in the Github PR is captured in JIRA if the two are linked, > see https://issues.apa

[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] [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

Re: Optimisations proposal for FacetsConfig

Thanks Erick! It's done, it was as trivial as deleting a single word: https://issues.apache.org/jira/browse/LUCENE-6909 Sanne On 24 November 2015 at 18:10, Erick Erickson <erickerick...@gmail.com> wrote: > Sanne: > > Sure, please open a JIRA and add a patch. You'll need to cre

[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

Optimisations proposal for FacetsConfig

t? As a second step, I'd also like to see if the build method could be short-circuited for a quick return: in case there are no faceted fields would be great to just return with the input document right away. Thanks, Sanne - To

[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

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

[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

Re: [VOTE] Move trunk to Java 8

JVMs, often supported JVM builds by other vendors, and I don't expect this to change. HTH -- Sanne On 12 September 2014 20:31, Chris Hostetter hossman_luc...@fucit.org wrote: : That is bogus for an open source project. I won't have such updates, : how can i support such a java version, users

[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-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

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 sar

Re: The Old Git Discussion

patch files to JIRA. - Sanne On 8 January 2014 00:45, David Smiley (@MITRE.org) dsmi...@mitre.org wrote: +1, Mark. Git isn't perfect; I sympathize with the annoyances pointed out by Rob et. all. But I think we would be better off for it -- a net win considering the upsides. In the end

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: Indexing file with security problem

interesting! Sanne - Hibernate Search team On 27 June 2013 03:14, Otis Gospodnetic otis.gospodne...@gmail.com wrote: Hi, I would start from ManifoldCF - it may save you some work. Otis Solr ElasticSearch Support http://sematext.com/ On Jun 26, 2013 5:01 PM, lukasw lukas...@gmail.com

Infinispan JGroups migrating to Apache License

stores the byte[] chunks of the segments. This is not a replacement for Solr or ElasticSearch: it provides just a storage component; it does not solve - among others - the problem of distributed writers. It is used by Hibernate Search. Regards, Sanne

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: Source Control

, but that's never been a blocker in our case as each user is free to use what he prefers on his personal repository. Highly recommended! Sanne On 28 October 2012 16:58, Dawid Weiss dawid.we...@cs.put.poznan.pl wrote: Different toys for different boys. Everyone will have his or her favorite

Re: ideas for alphas/betas?

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

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: [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 (https

Re: [VOTE] release 3.3 (take two)

-in compatible replacements) Regards, Sanne 2011/6/26 Steven A Rowe sar...@syr.edu: +1 I looked at the differences, and then just ran tests on the Solr and Lucene source tarballs. Steve -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Sunday, June 26, 2011 11:12 AM

Re: Code Freeze on realtime_search branch

will spend my time testing this carefully instead, or if some kind of locking is still required I'd appreciate some pointers so that I'll be able to remove them. Regards, Sanne 2011/4/29 Simon Willnauer simon.willna...@googlemail.com: Hey folks, LUCENE-3023 aims to land the considerably large

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: 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

is not handling it. I'm looking into Lucene 3.0.3 and the IOException it *is* actually needed, not sure what was changed in the version this is referring to, but as it used to throw it (and needing it), I think it's quite possible this need is not so remote. Regards, Sanne Shai On Mon, Mar 21

Re: Index File

://lucene.apache.org/java/3_0_3/fileformats.html and i know what Index should has. is there any way to see created index? yes, use the force :) http://code.google.com/p/luke/ Regards, Sanne thanks in advance . Peace. -Soheila D

Re: [VOTE] Lucene and Solr 3.1 release candidate

polluting your local caches with this: make sure you delete all copies when the real one is released. -- Sanne -- View this message in context: http://lucene.472066.n3.nabble.com/VOTE-Lucene-and-Solr-3-1-release-candidate-tp2645100p2675660.html Sent from the Solr - Dev mailing list archive

Re: [VOTE] Lucene and Solr 3.1 release candidate

as is but instructions and warnings in the release notes would be very welcome. (I couldn't find a Chances.html for Solr?) Regards, Sanne [1] http://people.apache.org/~rmuir/staging_area/lucene-solr-3.1RC0-rev1078688/lucene-3.1RC0/maven/org/apache/lucene/lucene-solr-grandparent/3.1.0/lucene-solr

Re: [VOTE] Lucene and Solr 3.1 release candidate

2011/3/8 Steven A Rowe sar...@syr.edu: Hi Sanne, Solr (and some Lucene modules) have several non-Mavenized dependencies. To work around this, the Maven build has a profile called bootstrap.  If you check out the source (or use the source distribution) you can place all non-Mavenized

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

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

[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

Re: Proposal about Version API relaxation

would think twice before trying; honestly the current requirements are scary. +1 Sanne 2010/4/15 Earwin Burrfoot ear...@gmail.com: I'd like to remind that Mike's proposal has stable branches. We can branch off preflex trunk right now and wrap it up as 3.1. Current trunk is declared as future 4.0

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: Having a default constructor in Analyzers

expansion and things like that) 8 snip 8 They are two different Analyzer types, but I assume they want to use the same value for Version, right? The same version which was used to build the rest of the index. Regards, Sanne

Re: Having a default constructor in Analyzers

here to check we could keep it simple :-) Thanks all, Sanne 2010/2/8 Uwe Schindler u...@thetaphi.de: Simon: Sanne, I would recommend you building a Factory pattern around you Analyzers / TokenStreams similar to what solr does. That way you can load you own default ctor interface via reflection

Having a default constructor in Analyzers

public StandardAnalyzer() { this(Version.LUCENE_CURRENT); } ? Of course more advanced use cases would need to pass parameters but please make the advanced usage optional; I have now seen more than a single project break because of this (and revert to older Lucene). Regards, Sanne

Re: Having a default constructor in Analyzers

for all help, Sanne 2010/2/7 Robert Muir rcm...@gmail.com: I propose we remove LUCENE_CURRENT completely, as soon as TEST_VERSION is done. On Sun, Feb 7, 2010 at 12:53 PM, Uwe Schindler u...@thetaphi.de wrote: Hi Sanne, Exactly that usage we want to prevent. Using Version.LUCENE_CURRENT

Re: Having a default constructor in Analyzers

of QueryParser I should use...) just some ideas, forgive me if I misunderstood this usage (should avoid writing late in the night..) Regards, Sanne 2010/2/7 Simon Willnauer simon.willna...@googlemail.com: On Sun, Feb 7, 2010 at 8:38 PM, Robert Muir rcm...@gmail.com wrote: Simon, can you explain

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

consider discouraging it's use, people just need to be informed of the behavior and know that no LockFactory impl is good for all cases. Adding some lines to it's javadoc seems appropriate. Regards, Sanne 2010/1/20 Chris Hostetter hossman_luc...@fucit.org: : At a minimu, shouldn't

Re: Lucene memory consumption

this to lucene-dev directly? Regards, Sanne 2010/1/6 Frederic Simon fr...@jfrog.org: Thanks Emmanuel, Yes the main issue is that the hardRef map in this class was forcing all the objects to go to the Old generation space in the JVM GC, instead of staying at a ThreadLocal level. So, all objects

Re: Lucene 2.9.0 Near Real Time Indexing and lock timeouts

from an Hibernate mapped database. While I recommend reading for newcomers, I'd also appreciate feedback and comments from Lucene experts and developers :-) Regards, Sanne 2010/1/14 Michael McCandless luc...@mikemccandless.com: Calling commit after every addition will drastically slow down your

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: 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 2010

Re: update doc by query

-committed: exact moment would be out of my control, but even so the view on index wouldn't have a chance to miss some documents. Regards, Sanne On Sun, Jan 10, 2010 at 10:04 PM, Michael McCandless luc...@mikemccandless.com wrote: I think there no particular demand... But: why not just separately

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: 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: 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: Upgrading Lucene jars

having Lucene already on the classpath and it's not immediately obvious that differently named jars contain same named classes. Could this be a good timeframe to change this? Regards, Sanne 2009/12/8 Koji Sekiguchi k...@r.email.ne.jp: Shalin Shekhar Mangar wrote: I need to upgrade contrib

[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

nightly build deploy to Maven repositories

it be a good idea to have him also verify the 2.9 branch until it's actively updated? Regards, Sanne - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org

Re: Solr 1.5 - The Cloud Edition!

to zero-nodes, persisting the in memory distributed state to something else (some plugins provided, like JDBC or S3 stores). Regards, Sanne 2009/12/4 Yonik Seeley yo...@lucidimagination.com: I hereby dub Solr 1.5 The Cloud Edition! (of course anyone else may also dub it anything else they so

Re: Socket and file locks

words to highlight the differences as a quick overview of what is available. hope you like it, I'm open to suggestions. Regards, Sanne 2009/11/29 Michael McCandless luc...@mikemccandless.com: This looks great! Maybe it makes most sense to create a wiki page (http://wiki.apache.org/lucene-java

Re: Socket and file locks

communication). While this is a technology preview and performance regarding the Directory code is still unknown, I believe the LockFactory was the most tested component. free to download and inspect (LGPL): http://anonsvn.jboss.org/repos/infinispan/trunk/lucene-directory/ Regards, Sanne 2009/11/27

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

[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

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

am thinking about a statistical assert, like considering it's fine if (ratio error some threshold), but that's my last resort. Regards, Sanne 2009/11/25 Michael McCandless luc...@mikemccandless.com: Indeed I see this test failing too!  On first look the test seems correct. Can you open

Re: A new Lucene Directory available

release. Regards, Sanne On Sun, Nov 15, 2009 at 8:50 AM, Lukáš Vlček lukas.vl...@gmail.com wrote: Hi, this sounds very interesting. Do you know which versions of Lucene are supported? Do you know if it would work with upcoming Lucene 3.0.x? https://jira.jboss.org/jira/browse/ISPN-275 Regards

Re: A new Lucene Directory available

configuration at all levels: os, jgroups and infrastructure. Thank you very much for you considerations, it's very appreciated. Regards, Sanne On Sun, Nov 15, 2009 at 12:39 PM, Earwin Burrfoot ear...@gmail.com wrote: Terracotta guys easy-clustered Lucene a few years ago. I'm yet to see at least one person

Re: A new Lucene Directory available

switch over to infinispan-...@lists.jboss.org so you can get better answers and I don't have to spam the Lucene developers. Regards, Sanne On Sun, Nov 15, 2009 at 3:43 PM, Earwin Burrfoot ear...@gmail.com wrote: About the RAMDirectory comparison, as you said yourself the bytes aren't read

Re: A new Lucene Directory available

this peeks your interest, sorry if I couldn't provide numbers. Regards, Sanne On Sat, Nov 14, 2009 at 11:15 PM, John Wang john.w...@gmail.com wrote: HI Sanne:     Very interesting!     What kinda performance should we expect with this, comparing to regular FSDIrectory on local HD. Thanks

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

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

[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