Solr 8.0 Error - For input string
All of a sudden getting the following error. Need help to understand rectify the same - 1/27/2020, 9:36:58 AM ERROR true x:livedata RequestHandlerBase org.apache.solr.common.SolrException: For input string: "1*1*1*0" org.apache.solr.common.SolrException: For input string: "1*1*1*0" at org.apache.solr.common.params.SolrParams.getInt(SolrParams.java:236) at org.apache.solr.search.QParser.getSortSpec(QParser.java:270) at org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:185) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:272) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:199) at org.apache.solr.core.SolrCore.execute(SolrCore.java:2559) at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:711) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:394) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:340) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1602) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:513) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1588) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1557) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:502) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NumberFormatException: For input string: "1*1*1*0" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:580) at java.lang.Integer.valueOf(Integer.java:766) at org.apache.solr.common.params.SolrParams.getInt(SolrParams.java:233) ... 43 more
Re: Re: Anyone have experience with Query Auto-Suggestor?
Oh, great! Thank you, this is helpful! On 1/24/20, 6:43 PM, "Walter Underwood" wrote: Click-based weights are vulnerable to spamming. Some of us fondly remember when Google was showing Microsoft as the first hit for “evil empire” thanks to a click attack. For our ecommerce search, we use the actual titles of books weighted by order volume. Decorated titles are reduced to a base title, so “Managerial Accounting: Student Value Edition” becomes just “Managerial Accounting”. Showing all the variations is the job of the real results page. wunder Walter Underwood wun...@wunderwood.org https://urldefense.proofpoint.com/v2/url?u=http-3A__observer.wunderwood.org_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=3oEhRJWEHDoz3HXt87Y_FXxPTUZg1zSA5r4P6urviug=87IOY_vKNONtR2r2IkW-NnZ4Rn3wI-OIO6RSdqdOMfU= (my blog) > On Jan 24, 2020, at 7:07 AM, Lucky Sharma wrote: > > Hi Audrey, > As suggested by Erik, you can index the data into a seperate collection and > You can instead of adding weights inthe document you can also use > LTR(Learning to Rank) with in Solr to rerank on the documents. > And also to increase more relevance with in the Autosuggestion and making > positional context of the user in case of Multi token keywords you can also > bigrams/trigrams to generate edge n-grams. > > > > Regards, > Lucky Sharma > > On Fri, 24 Jan, 2020, 8:28 pm Lucky Sharma, wrote: > >> Hi Audrey, >> As suggested by Erik, you can index the data into a seperate collection >> and You can instead of adding weights inthe document you can also use LTR >> with in Solr to rerank on the features. >> >> Regards, >> Lucky Sharma >> >> On Fri, 24 Jan, 2020, 8:01 pm Audrey Lorberfeld - >> audrey.lorberf...@ibm.com, wrote: >> >>> Erik, >>> >>> Thank you! Yes, that's exactly how we were thinking of architecting it. >>> And our ML engineer suggested something else for the suggestion weights, >>> actually -- to build a model that would programmatically update the weights >>> based on those suggestions' live clicks @ position k, etc. Pretty cool >>> idea... >>> >>> >>> >>> On 1/23/20, 2:26 PM, "Erik Hatcher" wrote: >>> >>>It's a great idea. And then index that file into a separate lean >>> collection of just the suggestions, along with the weight as another field >>> on those documents, to use for ranking them at query time with standard >>> /select queries. (this separate suggest collection would also have >>> appropriate tokenization to match the partial words as the user types, like >>> ngramming) >>> >>>Erik >>> >>> On Jan 20, 2020, at 11:54 AM, Audrey Lorberfeld - >>> audrey.lorberf...@ibm.com wrote: David, Thank you, that is useful. So, would you recommend using a (clean) >>> field over an external dictionary file? We have lots of "top queries" and >>> measure their nDCG. A thought was to programmatically generate an external >>> file where the weight per query term (or phrase) == its nDCG. Bad idea? Best, Audrey On 1/20/20, 11:51 AM, "David Hastings" < >>> hastings.recurs...@gmail.com> wrote: Ive used this quite a bit, my biggest piece of advice is to >>> choose a field that you know is clean, with well defined terms/words, you dont >>> want an autocomplete that has a massive dictionary, also it will make the start/reload times pretty slow On Mon, Jan 20, 2020 at 11:47 AM Audrey Lorberfeld - audrey.lorberf...@ibm.com wrote: > Hi All, > > We plan to incorporate a query autocomplete functionality into our >>> search > engine (like this: >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lucene.apache.org_solr_guide_8-5F1_suggester.html=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=L8V-izaMW_v4j-1zvfiXSqm6aAoaRtk-VJXA6okBs_U=vnE9KGyF3jky9fSi22XUJEEbKLM1CA7mWAKrl2qhKC0= > ). And I was wondering if anyone has personal experience with this > component and would like to share? Basically, we are just looking >>> for some > best practices from more experienced Solr admins so that we have a >>> starting > place to launch this in our beta. > > Thank you! > > Best, > Audrey > >>> >>> >>> >>>
