ISORC 2015 - Deadline Extension: 28/12/2014

Extended submission deadline: 28 December 2014 Submission at: https://www.easychair.org/conferences/?conf=isorc2015 == CALL FOR PAPERS The 18th IEEE International Symposium On Real-Time Computing

Facet Result Order

Hi All, I am working on Lucene Facet now a day and facet seems working fine. Just one thing that come to my attention is, order of facet results get changed if there is same total count.  For example, for country facet following results have been noticed. First time: - USA(10)- India(9)- UK(9)

ISORC 2015 - Deadline extension: Dec. 28, 2014

[ We apologize to those who receive multiple copies of this message. ] Extended submission deadline: 28 December 2014 Submission at: https://www.easychair.org/conferences/?conf=isorc2015 === CALL FOR

Getting new token stream from analyzer for legacy projects!

Hi, I have a legacy problem with the token stream. In my application I create a batch of documents from a unique analyzer (this due to configuration). I add the field using the tokenStream from the analyzer(for internal reasons). In a pseudo code this translates in : Analyzer analyzer =

unsafe memory access operation

we are running into this issue for the first time while searching a lucene index hosted on NFS. Once, this error occurs, all subsequent requests fails. help appreciated. Our Config: 64-bit Java 1.7 (we are making use of MMapDirectory) Lucene 4.2.1 Index size: 8GB Let me know if you need any

RE: unsafe memory access operation

Hi, Which Java 7 build number / update level are you using? Those errors occur easily if you use an outdated JDK version. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: Vijay B

Re: unsafe memory access operation

Here is the info you requested: java version 1.7.0_25 Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) On Fri, Dec 12, 2014 at 12:05 PM, Uwe Schindler u...@thetaphi.de wrote: Hi, Which Java 7 build number / update level

Re: unsafe memory access operation

Uwe, We never seen these errors before with the same version of java. Would you think updating to latest version of 1.7 would get rid of this? Here is the info you requested: java version 1.7.0_25 Java(TM) SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot(TM) 64-Bit Server VM (build

RE: unsafe memory access operation

Hi, I noticed, you mentioned NFS as filesystem. Lucene does not work correctly on NFS as file systems, especially when writing to an index (commits don’t work safely, NRT reopening breaks without correct DeletionPolicy, FileLocking is broken). Purely reading indexes is fine, but here NFS is a

Re: unsafe memory access operation

Ume, Thank you for your inputs. We update (write) index nightly once a day and use it majorly for reads. I am wondering how does the latest version of java that you recommend help in my case. Please clarify. -- on a side note,not related to this, could you please reply to my comments on your

RE: unsafe memory access operation

Hi, Ume, Thank you for your inputs. We update (write) index nightly once a day and use it majorly for reads. I am wondering how does the latest version of java that you recommend help in my case. Please clarify. This is unrelated to this issue. It is just a recommendation. -- on a side