Re: Reverse range query
This post helped me solve my problem which I had posted on StackOverflow. See my answer here: http://stackoverflow.com/questions/8070742/solr-multivalued-field-how-can-i-return-documents-where-all-values-in-the-fiel http://stackoverflow.com/questions/8070742/solr-multivalued-field-how-can-i-return-documents-where-all-values-in-the-fiel Would be great to see a feature in Solr for a reverse query. Ie, the value in your solr document is queried against your query input, which would make problems like this a breeze. -- View this message in context: http://lucene.472066.n3.nabble.com/Reverse-range-query-tp1789135p3497482.html Sent from the Solr - User mailing list archive at Nabble.com.
SEVERE: java.io.IOException: The specified network name is no longer available
Hi all, Using Solr 1.4 hosted with Tomcat 6 on Windows 2003 (sometimes Windows 2008) Occasionally, we can't search anymore and this error shows up in the log file: SEVERE: java.io.IOException: The specified network name is no longer available at java.io.RandomAccessFile.readBytes(Native Method) at java.io.RandomAccessFile.read(Unknown Source) at org.apache.lucene.store.SimpleFSDirectory$SimpleFSIndexInput.readInternal(SimpleFSDirectory.java:132) at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:157) at org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:38) at org.apache.lucene.store.IndexInput.readVInt(IndexInput.java:80) at org.apache.lucene.index.TermBuffer.read(TermBuffer.java:64) at org.apache.lucene.index.SegmentTermEnum.next(SegmentTermEnum.java:129) at org.apache.lucene.index.SegmentTermEnum.scanTo(SegmentTermEnum.java:160) at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:232) at org.apache.lucene.index.TermInfosReader.terms(TermInfosReader.java:299) at org.apache.lucene.index.SegmentReader.terms(SegmentReader.java:939) at org.apache.lucene.index.DirectoryReader$MultiTermEnum.init(DirectoryReader.java:973) at org.apache.lucene.index.DirectoryReader.terms(DirectoryReader.java:620) at org.apache.solr.search.SolrIndexReader.terms(SolrIndexReader.java:302) at org.apache.solr.handler.component.TermsComponent.process(TermsComponent.java:82) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:195) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1316) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:338) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:241) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454) at java.lang.Thread.run(Unknown Source) Once we see the error, it is persistent. Restarting Tomcat makes the error stop. This is happening across a variety of deployments and networks, so I don't think there is an actual network problem. Many other apps operate fine on the same server(s)/network(s). We are using a file server (again with many different configurations) to store the actual index files, which are not on the same machine as Solr/Tomcat. On a few deployments we're moving the index local to Solr to see if that corrects the problem. My questions are: 1. Has anyone seen something like this before? 1. Is putting the index files on a file server a supported configuration? Thanks for any help Brian. -- View this message in context: http://lucene.472066.n3.nabble.com/SEVERE-java-io-IOException-The-specified-network-name-is-no-longer-available-tp1454016p1454016.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: SEVERE: java.io.IOException: The specified network name is no longer available
Yonik Seeley-2-2 wrote: Hmmm, that's interesting. I wonder if it's a Java bug or something? There's nothing in lucene/solr that I know of that would lead to The specified network name is no longer available. What JVM are you using? -Yonik http://lucenerevolution.org Lucene/Solr Conference, Boston Oct 7-8 java -version gives me this: java version 1.6.0_18 Java(TM) SE Runtime Environment (build 1.6.0_18-b07) Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode) Is that what you're looking for? Can you confirm that putting the Index files on a network share is OK? We used to use Lucene and I know that this was bad news .. but since getting these errors we're wondering whether Solr might have a similar issue. I found this Java bug, but it's really old and I'm not sure if it's relevant: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6176034 Thanks Yonik -- View this message in context: http://lucene.472066.n3.nabble.com/SEVERE-java-io-IOException-The-specified-network-name-is-no-longer-available-tp1454016p1454271.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: SEVERE: java.io.IOException: The specified network name is no longer available
Erick Erickson wrote: SOLR uses Lucene, so I'd expect that putting your index files on a share isn't any more robust under SOLR than Lucene Sounds to me like your network's glitchy. Except that with Lucene we had separate processes searching and indexing directly against the files over the network, so it wouldn't be possible to have any centralized locking logic beyond NTFS. Solr is different in that indexing and searching requests go through Solr and are passed to Lucene through the same process. This is why it sounds plausible to me that Solr could handle storing the index files on a network share. Originally I blamed the network too. But given that other apps that are using the same file server are working fine, and that we have this problem across completely separate networks (ie, different clients of ours that have completely different infrastructures), I don't think that it is the network. Does anyone else store their Solr index on a file share, or NAS or SAN or anything other than a local disk? -- View this message in context: http://lucene.472066.n3.nabble.com/SEVERE-java-io-IOException-The-specified-network-name-is-no-longer-available-tp1454016p1454468.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query Filter fq with OR operator
This feature is very important to me .. should I post something on the dev forum? Not sure what the proper protocol is for adding a feature to the roadmap Thanks, Brian. -- View this message in context: http://www.nabble.com/Query-Filter-fq-with-OR-operator-tp23895837p24059181.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query Filter fq with OR operator
Otis Gospodnetic wrote: Brian, Opening a JIRA issue if it doesn't already exist is the best way. If you can provide a patch, even better! Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch Thanks Otis! I've created a JIRA https://issues.apache.org/jira/browse/SOLR-1223 issue here - Original Message From: brian519 bpear...@desire2learn.com To: solr-user@lucene.apache.org Sent: Tuesday, June 16, 2009 1:32:41 PM Subject: Re: Query Filter fq with OR operator This feature is very important to me .. should I post something on the dev forum? Not sure what the proper protocol is for adding a feature to the roadmap Thanks, Brian. -- View this message in context: http://www.nabble.com/Query-Filter-fq-with-OR-operator-tp23895837p24059181.html Sent from the Solr - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/Query-Filter-fq-with-OR-operator-tp23895837p24060300.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query Filter fq with OR operator
Adding my vote for this feature. Another possible way to do this would be to introduce the ofq parameter .. so all of the fq's and AND'ed and the ofq's would be OR'd I've got some really complicated fq's that aren't going to cache well, introducing OR'd filters would allow me to use simpler filters and I expect performance would be a lot better Thanks -- View this message in context: http://www.nabble.com/Query-Filter-fq-with-OR-operator-tp23895837p23986336.html Sent from the Solr - User mailing list archive at Nabble.com.
