Re: DIH error when nested db datasource and file data source
hi gora,
Query works and if i remove xml data load indexing works fine too
Problem seem to be with this
entity name=f processor=FileListEntityProcessor
baseDir=${solr.solr.home} fileName=.xml
recursive=false rootEntity=true
dataSource=video_datasource
entity name=x processor=XPathEntityProcessor
forEach=/gvpVideoMetaData/mediaItem[@media_id='${topic_tree.topic_id}']
url=${f.fileAbsolutePath}
Basically how would i get details abt a id fetched from db using xpath from
a xml file.
--
View this message in context:
http://lucene.472066.n3.nabble.com/DIH-error-when-nested-db-datasource-and-file-data-source-tp3345664p3345735.html
Sent from the Solr - User mailing list archive at Nabble.com.
Numeric Facets query results
Hello,
I am new to SOLR and using the Numeric Facets feature in v3.3 to display a
facet list of lengths. I have successfully added the query parameters to
display a facet list using:
facet.range = length
f.length.facet.range.start = 0
f.length.facet.range.end = 100
f.length.facet.range.gap = 10
f.length.facet.range.include = lower
Which gives me a list like
0 10
10 20
20 30
Etc to 100
Now I want to create a query to return the pertinent results when a user
clicks on a facet item like 10 20.
Since I am using f.length.facet.range.include = lower I cannot simply use
length:[10 TO 20] since this includes results where length is 20. My
current work around is to add an exclude -length:20
I also tried {!frange l=10 u=20 incu=false incl=true}length which returns
the pertinent results but does not use the same single parameter for
include so this is not ideal either.
Is there a better way of doing this? Perhaps pulling data from a facet list
cache? Or another method that respects the same parameters, specifically
include, that facet.range uses?
Thanks for any help.
Greg
Re: Numeric Facets query results
Of course you can hack something like
length:[10 TO 19.99], but that's clumsy too.
It doesn't help the 3.x code line, but trunk allows
mixing inclusive and exclusive end points in
ranges, e.g. length:[10 TO 20}
(note curly brace at end). See:
https://issues.apache.org/jira/browse/LUCENE-996
Best
Erick
On Sun, Sep 18, 2011 at 1:39 AM, Coda Moda pub...@codamoda.com wrote:
Hello,
I am new to SOLR and using the Numeric Facets feature in v3.3 to display a
facet list of lengths. I have successfully added the query parameters to
display a facet list using:
facet.range = length
f.length.facet.range.start = 0
f.length.facet.range.end = 100
f.length.facet.range.gap = 10
f.length.facet.range.include = lower
Which gives me a list like
0 10
10 20
20 30
Etc to 100
Now I want to create a query to return the pertinent results when a user
clicks on a facet item like 10 20.
Since I am using f.length.facet.range.include = lower I cannot simply use
length:[10 TO 20] since this includes results where length is 20. My
current work around is to add an exclude -length:20
I also tried {!frange l=10 u=20 incu=false incl=true}length which returns
the pertinent results but does not use the same single parameter for
include so this is not ideal either.
Is there a better way of doing this? Perhaps pulling data from a facet list
cache? Or another method that respects the same parameters, specifically
include, that facet.range uses?
Thanks for any help.
Greg
Re: Miscellaneous DIH related questions
No cron job, I'm just clicking on the full import button in dataimport.jsp page. 1) Can you point me to the code in Solr where such a retry functionality should be added? I might be able to contribute. 2) What is a good place to add the java based scheduling? Again I'll test and share if I succeed. - Pulkit Sent from my iPhone On Sep 18, 2011, at 12:37 AM, Gora Mohanty g...@mimirtech.com wrote: On Sun, Sep 18, 2011 at 4:50 AM, Pulkit Singhal pulkitsing...@gmail.com wrote: [...] 3) Is there some way to configure the datasource to retry 3 time or something like that? I have increased the values for connectionTimeout and readTimeout but it doesn't help when sometimes the server simply denies the request due to heavy load. I need to be able to retry at those times. The onError has only the abort,skip,continue options, non of which really let me retry anything. [...] Don't think that there is a built-in feature for this, though it sounds like it would be useful. I presume that you are scheduling your imports through cron, or something like that. One possibility then would be to have the script check the status of the import, and retry if needed. Regards, Gora
Tomcat unicode problems with IE 9, Firefox 6 and solrj client
Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client
The first returned link for Firefox 6 is the same as the returned link for IE 9. I was misread. So the encode is this one. Anyone knows what it is. From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:48:31 PM Subject: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client
maybe set on tomcat connector ? Connector ... URIEncoding=UTF-8/ kiwi On Mon, Sep 19, 2011 at 12:56 AM, Xue-Feng Yang just4l...@yahoo.com wrote: The first returned link for Firefox 6 is the same as the returned link for IE 9. I was misread. So the encode is this one. Anyone knows what it is. From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:48:31 PM Subject: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client
I had found the encode from java.net.URLEncoder. However, I still couldn't get any result for solrj client. Is there any different usage for solrj between English and other languages? From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:56:44 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client The first returned link for Firefox 6 is the same as the returned link for IE 9. I was misread. So the encode is this one. Anyone knows what it is. From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:48:31 PM Subject: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client
I saw this in the doc and set it before I started up tomcat first time. All results I posted is with this configuration. Thanks anyway. From: Kiwi de coder kiwio...@gmail.com To: solr-user@lucene.apache.org; Xue-Feng Yang just4l...@yahoo.com Sent: Sunday, September 18, 2011 1:14:58 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client maybe set on tomcat connector ? Connector ... URIEncoding=UTF-8/ kiwi On Mon, Sep 19, 2011 at 12:56 AM, Xue-Feng Yang just4l...@yahoo.com wrote: The first returned link for Firefox 6 is the same as the returned link for IE 9. I was misread. So the encode is this one. Anyone knows what it is. From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:48:31 PM Subject: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client
Actually, it works in some cases in my post. So it's not a problem in server. It's a problem in client. I may have some mistakes in solrj client, but it works in English makes the thing confused. From: Kiwi de coder kiwio...@gmail.com To: solr-user@lucene.apache.org; Xue-Feng Yang just4l...@yahoo.com Sent: Sunday, September 18, 2011 1:14:58 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client maybe set on tomcat connector ? Connector ... URIEncoding=UTF-8/ kiwi On Mon, Sep 19, 2011 at 12:56 AM, Xue-Feng Yang just4l...@yahoo.com wrote: The first returned link for Firefox 6 is the same as the returned link for IE 9. I was misread. So the encode is this one. Anyone knows what it is. From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:48:31 PM Subject: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Stability of NRT searching in trunk
Hey everyone, I know this question has probably been asked before but I cannot seem to find it. Basically I noticed that in the latest trunk of Solr there is now a soft commit (http://wiki.apache.org/solr/UpdateXmlMessages#A.22commit.22_and_.22optimize.22) that ofc allows for the hard index to look like it has been updated in realtime (with a mechanism that sounds very much like a fsync to disk on a hard commit). I am wondering: a. Is this stable enough to be used to reproduce this kind of behaviour in production: https://issues.apache.org/jira/browse/SOLR-2566 ? b. Does it work for the full CRUD of a record? I am wondering whether it is time I can switch from the Lucene project to the Solr project which better supports a lot of my needs. I ofc cannot do this until I have some kind of NRT ability in Solr (not previous NRT behaviour with indexing 10k records every second, I mean real NRT). Thanks in advance, -- View this message in context: http://lucene.472066.n3.nabble.com/Stability-of-NRT-searching-in-trunk-tp3346714p3346714.html Sent from the Solr - User mailing list archive at Nabble.com.
How to sort results based on matching term position
We have a requirement to sort/boost documents returned for phrase matches depending on where the match was within the field, the nearer the beginning the better i.e. a search term of The w would return results in this order The War of the Worlds The Ward The Whistleblower Gone with the Wind Tomorrow, When the War Began Spy Kids: All the Time in the World Tomorrow, When the War Began I am hoping TermVectors, TermPositions or TermOffsets may help here and have enabled them but not sure how to utilise them to boost scores or sort. Am I going to need to create our own Solr components (we have tried to avoid this to date) and if so which ones? Any help appreciated Thanks Dan Ledgard | Lead Developer KIT digital | York, UK | www.kitd.comhttp://www.kitd.com/ | NASDAQ: KITD | Vision of the Future
Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client
Finally, it's a known bug: https://issues.apache.org/jira/browse/SOLR-1959 From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 1:25:08 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Actually, it works in some cases in my post. So it's not a problem in server. It's a problem in client. I may have some mistakes in solrj client, but it works in English makes the thing confused. From: Kiwi de coder kiwio...@gmail.com To: solr-user@lucene.apache.org; Xue-Feng Yang just4l...@yahoo.com Sent: Sunday, September 18, 2011 1:14:58 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client maybe set on tomcat connector ? Connector ... URIEncoding=UTF-8/ kiwi On Mon, Sep 19, 2011 at 12:56 AM, Xue-Feng Yang just4l...@yahoo.com wrote: The first returned link for Firefox 6 is the same as the returned link for IE 9. I was misread. So the encode is this one. Anyone knows what it is. From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:48:31 PM Subject: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Re: JSON and DataImportHandler
Any updates on this topic? On Fri, Jul 16, 2010 at 5:36 PM, P Williams williams.tricia.l...@gmail.com wrote: Hi All, Has anyone gotten the DataImportHandler to work with json as input? Is there an even easier alternative to DIH? Could you show me an example? Many thanks, Tricia
Re: JSON and DataImportHandler
Ah I see now: http://wiki.apache.org/solr/UpdateJSON#Example Not part of DIH that's all. On Sun, Sep 18, 2011 at 5:42 PM, Pulkit Singhal pulkitsing...@gmail.com wrote: Any updates on this topic? On Fri, Jul 16, 2010 at 5:36 PM, P Williams williams.tricia.l...@gmail.com wrote: Hi All, Has anyone gotten the DataImportHandler to work with json as input? Is there an even easier alternative to DIH? Could you show me an example? Many thanks, Tricia
Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client
conclusion: both Tomcat 6 and Glassfish 3 work with solrj client by POST. ^=^ From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 4:53:25 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Finally, it's a known bug: https://issues.apache.org/jira/browse/SOLR-1959 From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 1:25:08 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Actually, it works in some cases in my post. So it's not a problem in server. It's a problem in client. I may have some mistakes in solrj client, but it works in English makes the thing confused. From: Kiwi de coder kiwio...@gmail.com To: solr-user@lucene.apache.org; Xue-Feng Yang just4l...@yahoo.com Sent: Sunday, September 18, 2011 1:14:58 PM Subject: Re: Tomcat unicode problems with IE 9, Firefox 6 and solrj client maybe set on tomcat connector ? Connector ... URIEncoding=UTF-8/ kiwi On Mon, Sep 19, 2011 at 12:56 AM, Xue-Feng Yang just4l...@yahoo.com wrote: The first returned link for Firefox 6 is the same as the returned link for IE 9. I was misread. So the encode is this one. Anyone knows what it is. From: Xue-Feng Yang just4l...@yahoo.com To: solr-user@lucene.apache.org solr-user@lucene.apache.org Sent: Sunday, September 18, 2011 12:48:31 PM Subject: Tomcat unicode problems with IE 9, Firefox 6 and solrj client Now I moved to Tomcat 6 for another round testing. All English cores are OK for IE 9, Firefox 6 and solrj client. When I tested with Chinese cores, IE 9 is OK whatever I played on it. Firefox 6 is a little different: 1) If I set Query String to content:耶和华 without qotations in page http://localhost:18080/solr/cuv/admin/, I had return responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:耶和华/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=5908 start=0docstr name=id申命记 2:2/str/docdocstr name=id出埃及记 13:1/str/docdocstr name=id出埃及记 14:1/str/docdocstr name=id出埃及记 16:11/str/docdocstr name=id出埃及记 25:1/str/docdocstr name=id出埃及记 30:11/str/docdocstr name=id出埃及记 30:17/str/docdocstr name=id出埃及记 30:22/str/docdocstr name=id出埃及记 31:1/str/docdocstr name=id出埃及记 31:12/str/doc/result/response the link went to http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on and %E8%80%B6%E5%92%8C%E5%8D%8E is visible as 耶和华。 2) If I refreshed, it kept the same. 3) If I highlighted the link and placed Enter key, then the returned link was http://localhost:18080/solr/cuv/select/?q=content%3A%D2%AE%BA%CD%BB%AAversion=2.2start=0rows=10indent=on which was different from the above link. The returned page was responselst name=responseHeaderint name=status0/intint name=QTime1/intlst name=paramsstr name=indenton/strstr name=start0/strstr name=qcontent:Ү�ͻ�/strstr name=rows10/strstr name=version2.2/str/lst/lstresult name=response numFound=0 start=0//response Actually, in IE 9, the returned link is always http://localhost:18080/solr/cuv/select/?q=content%3A%E8%80%B6%E5%92%8C%E5%8D%8Eversion=2.2start=0rows=10indent=on which is different from both of Firefox 6. For solrj client, I tested many ways to encode, but all return no results. What is the right encode way? Any help is welcome.
Re: Lucene-SOLR transition
On 9/15/2011 8:30 PM, Scott Smith wrote: 2. Assuming that the answer to 1 is correct, then is there an easy way to take a lucene query (with nested Boolean queries, filter queries, etc.) and generate a SOLR query string with q and fq components? I believe that Query.toString() will probably get you back something that can be parsed in turn by the traditional lucene QueryParser, thus completing the circle and returning your original Query. But why would you want to do that? -Mike
what is the default value of omitNorms and termVectors in solr schema
Hi As per this document, http://wiki.apache.org/solr/FieldOptionsByUseCase, omitNorms and termVectors have to be explicitly specified in some cases. I am wondering what is the default value of these settings if solr schema definition does not state them. *Example:* field name=ql_path type=string indexed=false stored=true/ In above case, will Solr create norms for this field and term vector as well? Any ideas? Thanks Saroj
Re: what is the default value of omitNorms and termVectors in solr schema
From Solr's example schema.xml: omitTermFreqAndPositions attribute introduced, true by default except for text fields (meaning TextField's) And term vectors most definitely are false by default. Also from the example schema.xml: termVectors: [false] set to true to store the term vector for a given field. Erik On Sep 18, 2011, at 19:58 , roz dev wrote: Hi As per this document, http://wiki.apache.org/solr/FieldOptionsByUseCase, omitNorms and termVectors have to be explicitly specified in some cases. I am wondering what is the default value of these settings if solr schema definition does not state them. *Example:* field name=ql_path type=string indexed=false stored=true/ In above case, will Solr create norms for this field and term vector as well? Any ideas? Thanks Saroj
Upgrading solr from 3.3 to 3.4
Hi all, Does upgrading solr from 3.3 to 3.4 requires reindexing of all the cores or we can directly copy the data folders to the new solr ? -- Thanks Regards, Isan Fulia.
Re: indexing data from rich documents - Tika with solr3.1
Hi Erik Hatcher-4 I tried index from your url. But i have a problem. In your case, you knew a files absolute path (Dir.new(/Users/erikhatcher/apache-solr-3.3.0/docs). So you can indexed it. In my case, i don't know a files absolute path. I only know http's address where have files (ex: you can see this link as reference: http://www.lc.unsw.edu.au/onlib/pdf/). Another ways? Thanks -- View this message in context: http://lucene.472066.n3.nabble.com/indexing-data-from-rich-documents-Tika-with-solr3-1-tp3322555p3347706.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Upgrading solr from 3.3 to 3.4
If you are already using Apache Lucene 3.1, 3.2 or 3.3, we strongly recommend you upgrade to 3.4.0 because of the index corruption bug on OS or computer crash or power loss (LUCENE-3418), now fixed in 3.4.0. 2011/9/19 Isan Fulia isan.fu...@germinait.com Hi all, Does upgrading solr from 3.3 to 3.4 requires reindexing of all the cores or we can directly copy the data folders to the new solr ? -- Thanks Regards, Isan Fulia.
OutOfMemoryError coming from TermVectorsReader
Hi,
I am new to solr. I an trying to index text documents of large size. On
searching from indexed documents I am getting following OutOfMemoryError.
Please help me in resolving this issue.
The field which stores file content is configured in schema.xml as below:
field name=Content type=text_token indexed=true stored=true
omitNorms=true termVectors=true termPositions=true termOffsets=true /
and Highlighting is configured as below:
str name=hlon/str
str name=hl.fl${all.fields.list}/str
str name=f.Content.hl.fragsize500/str
str name=f.Content.hl.useFastVectorHighlightertrue/str
2011-09-16 09:38:45.763 [http-thread-pool-9091(5)] ERROR -
java.lang.OutOfMemoryError: Java heap space
at
org.apache.lucene.index.TermVectorsReader.readTermVector(TermVectorsReader.java:503)
at
org.apache.lucene.index.TermVectorsReader.get(TermVectorsReader.java:263)
at
org.apache.lucene.index.TermVectorsReader.get(TermVectorsReader.java:284)
at
org.apache.lucene.index.SegmentReader.getTermFreqVector(SegmentReader.java:759)
at
org.apache.lucene.index.DirectoryReader.getTermFreqVector(DirectoryReader.java:510)
at
org.apache.solr.search.SolrIndexReader.getTermFreqVector(SolrIndexReader.java:234)
at
org.apache.lucene.search.vectorhighlight.FieldTermStack.init(FieldTermStack.java:83)
at
org.apache.lucene.search.vectorhighlight.FastVectorHighlighter.getFieldFragList(FastVectorHighlighter.java:175)
at
org.apache.lucene.search.vectorhighlight.FastVectorHighlighter.getBestFragments(FastVectorHighlighter.java:166)
at
org.apache.solr.highlight.DefaultSolrHighlighter.doHighlightingByFastVectorHighlighter(DefaultSolrHighlighter.java:509)
at
org.apache.solr.highlight.DefaultSolrHighlighter.doHighlighting(DefaultSolrHighlighter.java:376)
at
org.apache.solr.handler.component.HighlightComponent.process(HighlightComponent.java:116)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:194)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1368)
at
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:356)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:215)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162)
at
org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227)
at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170)
at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013)
Thanks Regards
Anand Nigam
Developer
***
The Royal Bank of Scotland plc. Registered in Scotland No 90312.
Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB.
Authorised and regulated by the Financial Services Authority. The
Royal Bank of Scotland N.V. is authorised and regulated by the
De Nederlandsche Bank and has its seat at Amsterdam, the
Netherlands, and is registered in the Commercial Register under
number 33002587. Registered Office: Gustav Mahlerlaan 350,
Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and
The Royal Bank of Scotland plc are authorised to act as agent for each
other in certain jurisdictions.
This e-mail message is confidential and for use by the addressee only.
If the message is received by anyone other than the addressee, please
return the message to the sender by replying to it and then delete the
message from your computer. Internet e-mails are not necessarily
secure. The Royal Bank of Scotland plc and The Royal Bank of Scotland
N.V. including its affiliates (RBS group) does not accept responsibility
for changes made to this message after it was sent.
