SOLR 3.3.0 multivalued field sort problem
Hi, I am currently using SOLR 1.4.1, With this version sorting working fine even in multivalued field. Now I am planning to upgrade my SOLR version from 1.4.1 -- 3.3.0, In this latest version sorting is not working on multivauled field. So I am in unable to upgrade my SOLR due to this drawback. Is there a work around available to fix this problem? Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/SOLR-3-3-0-multivalued-field-sort-problem-tp3248778p3248778.html Sent from the Solr - User mailing list archive at Nabble.com.
Fuzzy search with sort combination - drawback
Hi, I am having one problem while using the fuzzy search from query. I have two fields in my SOLR output, one field is endNgramed and other one is a normal Integer field which will have my customized score for that document. I have a handler[myhandler] which by default will sort the documents based on my customized score field and return the response. Here I am trying fuzzy search sample query. http://localhost:8080/solr/core0/select/?qt=myhandlerq=apple~0.7 I am getting the following result for the above query { Term:tool academy application, MyScore:1152}, { Term:fiona apple, MyScore:928}, { Term:apple bottom jeans, MyScore:637}, { Term:apply for reality show, MyScore:606}, { Term:tool academy 3 application, MyScore:203}] Here less relevant content has been coming on top [due to my customized sort]. If I remove that sorting criteria and do the same search, I am getting the following result. { Term:fiona apple, MyScore:928}, { Term:apple bottom jeans, MyScore:637}, { Term:apply for reality show, MyScore:606}, { Term:tool academy application, MyScore:1152}, { Term:tool academy 3 application, MyScore:203}] }, Is there a way to achieve the customized sort as well as the relevant content on top in this scenario. Can anyone advice? Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/Fuzzy-search-with-sort-combination-drawback-tp3248774p3248774.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query performance very slow even after autowarming
No Wease, We got the performance improvement after doing the following stuff -- Reduced the merge factor from 10 to 3. -- Auto-warming queries as I mentioned in my initial thread. Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/Query-performance-very-slow-even-after-autowarming-tp2010384p2545451.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: EdgeNgram Auto suggest - doubles ignore
Hi Erick, If you have time, Can you please take a look and provide your comments (or) suggestions for this problem? Please let me know if you need any more information. Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/EdgeNgram-Auto-suggest-doubles-ignore-tp2321919p2451828.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: EdgeNgram Auto suggest - doubles ignore
Hi Erick, I tried to use terms component, I got ended up with the following problems. Problem: 1 Custom Sort not working in terms component: http://lucene.472066.n3.nabble.com/Term-component-sort-is-not-working-td1905059.html#a1909386 I want to sort using one of my custom field[value_score], I gave it aleady in my configuration, but it is not sorting properly. The following are the configuration in solrconfig.xml searchComponent name=termsComponent class=org.apache.solr.handler.component.TermsComponent/ requestHandler name=/terms class=org.apache.solr.handler.component.SearchHandler lst name=defaults bool name=termstrue/bool str name=wtjson/str str name=flname/str str name=sortvalue_score desc/str str name=indenttrue/str /lst arr name=components strtermsComponent/str /arr /requestHandler The SOLR response tag is not returned based on sorted parameter. Problem: 2 Cap sensitive problem: [I am searching for Apple] http://localhost/solr/core1/terms?terms.fl=nameterms.prefix=apple -- not working http://localhost/solr/core1/terms?terms.fl=nameterms.prefix=Apple -- working Tried regex to overcome cap-sensitive problem: http://localhost/solr/core1/terms?terms.fl=nameterms.regex=Appleterms.regex.flag=case_insensitive Is this regex based search will help me for my requirement? It is returning irrelevant results. I am using the same syntax it is mentioned in WIKI. http://wiki.apache.org/solr/TermsComponent Am I going wrong anywhere? Please let me know if you need any more info. Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/EdgeNgram-Auto-suggest-doubles-ignore-tp2321919p2399330.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: EdgeNgram Auto suggest - doubles ignore
Hi Eric, You are right, there is a copy field to EdgeNgram, I tried the configuration but it not working as expected. Configuration I tried: fieldType name=”query” class=”solr.TextField” positionIncrementGap=”100″ termVectors=”true” analyzer type=”index” tokenizer class=”solr.StandardTokenizerFactory”/ filter class=”solr.LowerCaseFilterFactory”/ /analyzer analyzer type=”query” tokenizer class=”solr.StandardTokenizerFactory”/ filter class=”solr.LowerCaseFilterFactory”/ /analyzer /fieldType fieldType name=”edgytext” class=”solr.TextField” positionIncrementGap=”100″ analyzer type=”index” tokenizer class=”solr.WhitespaceTokenizerFactory”/ filter class=”solr.LowerCaseFilterFactory”/ filter class=”solr.EdgeNGramFilterFactory” minGramSize=”3″ maxGramSize=”25″/ /analyzer analyzer type=”query” tokenizer class=”solr.KeywordTokenizerFactory”/ filter class=”solr.LowerCaseFilterFactory”/ /analyzer /fieldType field name=”user_query” type=”query” indexed=”true” stored=”true” omitNorms=”true” omitTermFreqAndPositions=”true” / field name=”edgy_user_query” type=”edgytext” indexed=”true” stored=”true” omitNorms=”true” omitTermFreqAndPositions=”true” / defaultSearchFieldedgy_user_query/defaultSearchField copyField source=”user_query” dest=”edgy_user_query”/ == When I search for the term apple. It is returning results for pineapple vers apple, milk with apple, apple milk shake ... Is there any other way to overcome this problem? Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/EdgeNgram-Auto-suggest-doubles-ignore-tp2321919p2329370.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: EdgeNgram Auto suggest - doubles ignore
Hi Eric, What I want here is, lets say I have 3 documents like [pineapple vers apple, milk with apple, apple milk shake ] and If i search for apple, it should return only apple milk shake because that term alone starts with the letter apple which I typed in. It should not bring others and if I type milk it should return only milk with apple I want an output Similar like a Google auto suggest. Is there a way to achieve this without encapsulating with double quotes. Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/EdgeNgram-Auto-suggest-doubles-ignore-tp2321919p2333602.html Sent from the Solr - User mailing list archive at Nabble.com.
RE: Problem while creating Polish supported SOLR artifact creation
Hi Steven, Thanks for your reply, I tried with the latest trunk and try tried the command ant dist, Still it is throwing the same 6 errors. https://svn.apache.org/repos/asf/lucene/dev/trunk/ Please advice. Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/Problem-while-creating-Polish-supported-SOLR-artifact-tp2183507p2184063.html Sent from the Solr - User mailing list archive at Nabble.com.
Problem while creating Polish supported SOLR artifact creation
Hi, I am new to do SOLR patching, Can anyone help me to do this? I am trying to apply this patch [SOLR-2237.patch] to include polish character support in SOLR. https://issues.apache.org/jira/browse/SOLR-2237 I did the following steps: 1) svn co -r {2010-11-15} http://svn.apache.org/repos/asf/lucene/dev/trunk lucene-dev-trunk 2) cd lucene-dev-trunk 3) wget https://issues.apache.org/jira/secure/attachment/12459598/SOLR-2237.patch 4) patch -p0 -i SOLR-2237.patch --dry-run (Stripping trailing CRs from patch.) patching file solr/contrib/analysis-extras/src/test/org/apache/solr/analysis/TestStempelPolishStemFilterFactory.java (Stripping trailing CRs from patch.) patching file solr/contrib/analysis-extras/src/java/org/apache/solr/analysis/StempelPolishStemFilterFactory.java (Stripping trailing CRs from patch.) patching file modules/analysis/stempel/src/java/org/apache/lucene/analysis/stempel/StempelStemmer.java (Stripping trailing CRs from patch.) patching file modules/analysis/stempel/src/java/org/apache/lucene/analysis/pl/PolishAnalyzer.java I believe patch was successfully completed. 5) ant I got the following compilation errors. common.compile-core: [javac] Compiling 123 source files to /home/test/lucene-dev-trunk-Nov-2010-exported_test/lucene/build/classes/java [javac] /home/test/lucene-dev-trunk-Nov-2010-exported_test/lucene/src/java/org/apache/lucene/search/SortField.java:472: inconvertible types [javac] found : org.apache.lucene.search.cache.CachedArrayCreatorcapture of ? [javac] required: org.apache.lucene.search.cache.IntValuesCreator [javac] return new FieldComparator.IntComparator(numHits, (IntValuesCreator)creator, (Integer)missingValue ); [javac] ^ [javac] /home/test/lucene-dev-trunk-Nov-2010-exported_test/lucene/src/java/org/apache/lucene/search/SortField.java:475: inconvertible types [javac] found : org.apache.lucene.search.cache.CachedArrayCreatorcapture of ? [javac] required: org.apache.lucene.search.cache.FloatValuesCreator [javac] return new FieldComparator.FloatComparator(numHits, (FloatValuesCreator)creator, (Float)missingValue ); [javac] ^ [javac] /home/test/lucene-dev-trunk-Nov-2010-exported_test/lucene/src/java/org/apache/lucene/search/SortField.java:478: inconvertible types [javac] found : org.apache.lucene.search.cache.CachedArrayCreatorcapture of ? [javac] required: org.apache.lucene.search.cache.LongValuesCreator [javac] return new FieldComparator.LongComparator(numHits, (LongValuesCreator)creator, (Long)missingValue ); [javac] ^ [javac] /home/test/lucene-dev-trunk-Nov-2010-exported_test/lucene/src/java/org/apache/lucene/search/SortField.java:481: inconvertible types [javac] found : org.apache.lucene.search.cache.CachedArrayCreatorcapture of ? [javac] required: org.apache.lucene.search.cache.DoubleValuesCreator [javac] return new FieldComparator.DoubleComparator(numHits, (DoubleValuesCreator)creator, (Double)missingValue ); [javac] ^ [javac] /home/test/lucene-dev-trunk-Nov-2010-exported_test/lucene/src/java/org/apache/lucene/search/SortField.java:484: inconvertible types [javac] found : org.apache.lucene.search.cache.CachedArrayCreatorcapture of ? [javac] required: org.apache.lucene.search.cache.ByteValuesCreator [javac] return new FieldComparator.ByteComparator(numHits, (ByteValuesCreator)creator, (Byte)missingValue ); [javac] ^ [javac] /home/test/lucene-dev-trunk-Nov-2010-exported_test/lucene/src/java/org/apache/lucene/search/SortField.java:487: inconvertible types [javac] found : org.apache.lucene.search.cache.CachedArrayCreatorcapture of ? [javac] required: org.apache.lucene.search.cache.ShortValuesCreator [javac] return new FieldComparator.ShortComparator(numHits, (ShortValuesCreator)creator, (Short)missingValue ); [javac] ^ [javac] 6 errors Again I tried the following 5) cd solr 6) ant dist Again I got the same above six error messages. I also tried the checkout the latest code from lucene trunk, Still I could not able to make it up. Can anyone provide a solution for this? It would be really helpful if I get latest polish supported solr war file readily available. Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/Problem-while-creating-Polish-supported-SOLR-artifact-creation-tp2183507p2183507.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query performance very slow even after autowarming
Hi Chris, Thanks for looking into it. Here is the sample query. http://localhost:8080/solr/core0/select/?qt=autosuggestq=a I am using a request handler with a name autosuggest with the following configuration. requestHandler name=autosuggest class=solr.SearchHandler lst name=defaults str name=wtjson/str str name=flname,score/str str name=sortscore desc/str str name=indenttrue/str /lst /requestHandler The debug timing for the above query is as follows. timing:{ time:.0, prepare:{ time:0.0, org.apache.solr.handler.component.QueryComponent:{ time:0.0}, org.apache.solr.handler.component.FacetComponent:{ time:0.0}, org.apache.solr.handler.component.MoreLikeThisComponent:{ time:0.0}, org.apache.solr.handler.component.HighlightComponent:{ time:0.0}, org.apache.solr.handler.component.StatsComponent:{ time:0.0}, org.apache.solr.handler.component.DebugComponent:{ time:0.0}}, process:{ time:.0, org.apache.solr.handler.component.QueryComponent:{ time:3332.0}, org.apache.solr.handler.component.FacetComponent:{ time:0.0}, org.apache.solr.handler.component.MoreLikeThisComponent:{ time:0.0}, org.apache.solr.handler.component.HighlightComponent:{ time:0.0}, org.apache.solr.handler.component.StatsComponent:{ time:0.0}, org.apache.solr.handler.component.DebugComponent:{ time:1.0} This is not at all consistent, sometimes it is happening and sometimes not. Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/Query-performance-very-slow-even-after-autowarming-tp2010384p2084263.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query performance very slow even after autowarming
Alexey, 1) I am using EdgeNGramFilter only in index analyzer alone. 2) Sometimes even multiple characters also creating problems, What i told was an example for a performance problem, And moreover I am trying out the autowarming and sometime it is not working ideally [100% guaranteed performance improvement], Let say If I am warming all the first letters, ideally all the first letter queries should perform good, I am not seeing that guaranteed performance improvement. Even after query warming still some queries are taking more than 3 seconds to respond. Is this the ideal behavior? Or my autowarming configuration is wrong can you please clarify it? Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/Query-performance-very-slow-even-after-autowarming-tp2010384p2039335.html Sent from the Solr - User mailing list archive at Nabble.com.
Query performance very slow even after autowarming
Hi, I am using edgeNgramFilterfactory on SOLR 1.4.1 [filter class=solr.EdgeNGramFilterFactory maxGramSize=100 minGramSize=1 /] for my indexing. Each document will have about 5 fields in it and only one field is indexed with EdgeNGramFilterFactory. I have about 1.4 million documents in my index now and my index size is approx 296MB. I made the field that is indexed with EdgeNGramFilterFactory as default search field. All my query responses are very slow, some of them taking more than 10seconds to respond. All my query responses are very slow, Queries with single letters are still very slow. /select/?q=m So I tried query warming as follows. listener event=newSearcher class=solr.QuerySenderListener arr name=queries lststr name=qa/str/lst lststr name=qb/str/lst lststr name=qc/str/lst lststr name=qd/str/lst lststr name=qe/str/lst lststr name=qf/str/lst lststr name=qg/str/lst lststr name=qh/str/lst lststr name=qi/str/lst lststr name=qj/str/lst lststr name=qk/str/lst lststr name=ql/str/lst lststr name=qm/str/lst lststr name=qn/str/lst lststr name=qo/str/lst lststr name=qp/str/lst lststr name=qq/str/lst lststr name=qr/str/lst lststr name=qs/str/lst lststr name=qt/str/lst lststr name=qu/str/lst lststr name=qv/str/lst lststr name=qw/str/lst lststr name=qx/str/lst lststr name=qy/str/lst lststr name=qz/str/lst /arr /listener The same above is done for firstSearcher as well. My cache settings are as follows. filterCache class=solr.LRUCache size=16384 initialSize=4096 autowarmCount=4096/ queryResultCache class=solr.LRUCache size=16384 initialSize=4096 autowarmCount=1024/ documentCache class=solr.LRUCache size=16384 initialSize=16384 / Still after query warming, few single character search is taking up to 3 seconds to respond. Am i doing anything wrong in my cache setting or autowarm setting or am i missing anything here? Thanks, Johnny -- View this message in context: http://lucene.472066.n3.nabble.com/Query-performance-very-slow-even-after-autowarming-tp2010384p2010384.html Sent from the Solr - User mailing list archive at Nabble.com.