Re: Announcing Splainer -- Open Source Solr Sandbox
Jacques, Does this documentation help? Am I missing anything? http://splainer.io/help.html Cheers -Doug On Wed, Aug 27, 2014 at 9:23 AM, Jacques du Rand jacq...@pricecheck.co.za wrote: ANY documentation as to how to setup this thing ? From: Doug Turnbull [dturnb...@opensourceconnections.com] Sent: Wednesday, August 27, 2014 1:46 PM To: solr-user@lucene.apache.org Subject: Re: Announcing Splainer -- Open Source Solr Sandbox Thanks! About the id field, in displayed fields you can specify an alternate Id field by prefixing a field name with id:. IE: id:uuid. You'll need to adjust this after pasting in a URL Doug On Wednesday, August 27, 2014, Markus Jelsma markus.jel...@openindex.io wrote: Yeah, very cool. Since this is all just client side, how about integrating it in Solr's UI? Also, it seems to assume `id` is the ID field, which is not always true. -Original message- From:david.w.smi...@gmail.com javascript:; david.w.smi...@gmail.com javascript:; Sent: Friday 22nd August 2014 19:42 To: solr-user@lucene.apache.org javascript:; Subject: Re: Announcing quot;Splainerquot; -- Open Source Solr Sandbox Cool Doug! I look forward to digging into this. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Fri, Aug 22, 2014 at 10:34 AM, Doug Turnbull dturnb...@opensourceconnections.com javascript:; wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io ). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com This email and its contents are subject to an email legal notice that can be viewed at http://www.naspers.com/disclaimer.php Should you be unable to access the link provided, please email us for a copy at c...@optinet.net Hierdie e-pos en sy inhoud is onderhewig aan 'n regskennisgewing oor elektroniese pos wat gelees kan word by http://www.naspers.com/afrikaans/voorbehoud.php 'n Afskrif kan aangevra word by c...@optinet.net -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com
Re: Announcing Splainer -- Open Source Solr Sandbox
Thanks to everyone that has sent me feedback on Splainer. I've resolved a couple of immediate issues surrounding pulling fl from the query: - not specifying an fl defaulted to just showing the id field's value for title/content -- we now assume to show more content (fl=*) not less - Splainer now accepts fl=* and *,score Other issues that folks identified : - NullPointerException presumably related to highlighting -- still investigating, but have had trouble recreating. If anyone else sees a similar issue, please let me know. - the unique id field is assumed to be id until you manually adjust it. We should prompt the user if this assumption appears false. The current work-around is to specify id:id_field_name in the displayed fields call out to tell Splainer what the id field is - Some documentation to help folks understand what they're seeing https://github.com/o19s/splainer/issues Thanks again, and please don't hesitate to engage me about the tool Cheers -Doug On Wed, Aug 27, 2014 at 10:09 AM, Doug Turnbull dturnb...@opensourceconnections.com wrote: As per documentation, it should be paste in your Solr URL and go. Generally we try to follow the maxim of Bad UI is like a bad joke if I have to explain it... its not good. So if something is not obvious (like having to prefix id: to an id field that's not id) that's a bug too me, not just a UI shortcoming. We'll fix it. Regardless, no tool is perfect, so we will come up with some documentation to walk people through the tool and capture edge cases that don't just work by pasting in your Solr URL. Did you encounter a specific problem? We shared this tool in part because our view of the world's Solr population is miniscule and biased around how we configure things. There's so much diversity in how people use Solr. So I humbly beseech the mailing list to tell me where Splainer doesn't work well with your Solr :) Cheers -Doug On Wed, Aug 27, 2014 at 9:23 AM, Jacques du Rand jacq...@pricecheck.co.za wrote: ANY documentation as to how to setup this thing ? From: Doug Turnbull [dturnb...@opensourceconnections.com] Sent: Wednesday, August 27, 2014 1:46 PM To: solr-user@lucene.apache.org Subject: Re: Announcing Splainer -- Open Source Solr Sandbox Thanks! About the id field, in displayed fields you can specify an alternate Id field by prefixing a field name with id:. IE: id:uuid. You'll need to adjust this after pasting in a URL Doug On Wednesday, August 27, 2014, Markus Jelsma markus.jel...@openindex.io wrote: Yeah, very cool. Since this is all just client side, how about integrating it in Solr's UI? Also, it seems to assume `id` is the ID field, which is not always true. -Original message- From:david.w.smi...@gmail.com javascript:; david.w.smi...@gmail.com javascript:; Sent: Friday 22nd August 2014 19:42 To: solr-user@lucene.apache.org javascript:; Subject: Re: Announcing quot;Splainerquot; -- Open Source Solr Sandbox Cool Doug! I look forward to digging into this. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Fri, Aug 22, 2014 at 10:34 AM, Doug Turnbull dturnb...@opensourceconnections.com javascript:; wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer ( http://splainer.io). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect
RE: Announcing Splainer -- Open Source Solr Sandbox
Yeah, very cool. Since this is all just client side, how about integrating it in Solr's UI? Also, it seems to assume `id` is the ID field, which is not always true. -Original message- From:david.w.smi...@gmail.com david.w.smi...@gmail.com Sent: Friday 22nd August 2014 19:42 To: solr-user@lucene.apache.org Subject: Re: Announcing quot;Splainerquot; -- Open Source Solr Sandbox Cool Doug! I look forward to digging into this. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Fri, Aug 22, 2014 at 10:34 AM, Doug Turnbull dturnb...@opensourceconnections.com wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com
Re: Announcing Splainer -- Open Source Solr Sandbox
Thanks! About the id field, in displayed fields you can specify an alternate Id field by prefixing a field name with id:. IE: id:uuid. You'll need to adjust this after pasting in a URL Doug On Wednesday, August 27, 2014, Markus Jelsma markus.jel...@openindex.io wrote: Yeah, very cool. Since this is all just client side, how about integrating it in Solr's UI? Also, it seems to assume `id` is the ID field, which is not always true. -Original message- From:david.w.smi...@gmail.com javascript:; david.w.smi...@gmail.com javascript:; Sent: Friday 22nd August 2014 19:42 To: solr-user@lucene.apache.org javascript:; Subject: Re: Announcing quot;Splainerquot; -- Open Source Solr Sandbox Cool Doug! I look forward to digging into this. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Fri, Aug 22, 2014 at 10:34 AM, Doug Turnbull dturnb...@opensourceconnections.com javascript:; wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com
RE: Announcing Splainer -- Open Source Solr Sandbox
ANY documentation as to how to setup this thing ? From: Doug Turnbull [dturnb...@opensourceconnections.com] Sent: Wednesday, August 27, 2014 1:46 PM To: solr-user@lucene.apache.org Subject: Re: Announcing Splainer -- Open Source Solr Sandbox Thanks! About the id field, in displayed fields you can specify an alternate Id field by prefixing a field name with id:. IE: id:uuid. You'll need to adjust this after pasting in a URL Doug On Wednesday, August 27, 2014, Markus Jelsma markus.jel...@openindex.io wrote: Yeah, very cool. Since this is all just client side, how about integrating it in Solr's UI? Also, it seems to assume `id` is the ID field, which is not always true. -Original message- From:david.w.smi...@gmail.com javascript:; david.w.smi...@gmail.com javascript:; Sent: Friday 22nd August 2014 19:42 To: solr-user@lucene.apache.org javascript:; Subject: Re: Announcing quot;Splainerquot; -- Open Source Solr Sandbox Cool Doug! I look forward to digging into this. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Fri, Aug 22, 2014 at 10:34 AM, Doug Turnbull dturnb...@opensourceconnections.com javascript:; wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com This email and its contents are subject to an email legal notice that can be viewed at http://www.naspers.com/disclaimer.php Should you be unable to access the link provided, please email us for a copy at c...@optinet.net Hierdie e-pos en sy inhoud is onderhewig aan 'n regskennisgewing oor elektroniese pos wat gelees kan word by http://www.naspers.com/afrikaans/voorbehoud.php 'n Afskrif kan aangevra word by c...@optinet.net
Re: Announcing Splainer -- Open Source Solr Sandbox
As per documentation, it should be paste in your Solr URL and go. Generally we try to follow the maxim of Bad UI is like a bad joke if I have to explain it... its not good. So if something is not obvious (like having to prefix id: to an id field that's not id) that's a bug too me, not just a UI shortcoming. We'll fix it. Regardless, no tool is perfect, so we will come up with some documentation to walk people through the tool and capture edge cases that don't just work by pasting in your Solr URL. Did you encounter a specific problem? We shared this tool in part because our view of the world's Solr population is miniscule and biased around how we configure things. There's so much diversity in how people use Solr. So I humbly beseech the mailing list to tell me where Splainer doesn't work well with your Solr :) Cheers -Doug On Wed, Aug 27, 2014 at 9:23 AM, Jacques du Rand jacq...@pricecheck.co.za wrote: ANY documentation as to how to setup this thing ? From: Doug Turnbull [dturnb...@opensourceconnections.com] Sent: Wednesday, August 27, 2014 1:46 PM To: solr-user@lucene.apache.org Subject: Re: Announcing Splainer -- Open Source Solr Sandbox Thanks! About the id field, in displayed fields you can specify an alternate Id field by prefixing a field name with id:. IE: id:uuid. You'll need to adjust this after pasting in a URL Doug On Wednesday, August 27, 2014, Markus Jelsma markus.jel...@openindex.io wrote: Yeah, very cool. Since this is all just client side, how about integrating it in Solr's UI? Also, it seems to assume `id` is the ID field, which is not always true. -Original message- From:david.w.smi...@gmail.com javascript:; david.w.smi...@gmail.com javascript:; Sent: Friday 22nd August 2014 19:42 To: solr-user@lucene.apache.org javascript:; Subject: Re: Announcing quot;Splainerquot; -- Open Source Solr Sandbox Cool Doug! I look forward to digging into this. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Fri, Aug 22, 2014 at 10:34 AM, Doug Turnbull dturnb...@opensourceconnections.com javascript:; wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io ). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com This email and its contents are subject to an email legal notice that can be viewed at http://www.naspers.com/disclaimer.php Should you be unable to access the link provided, please email us for a copy at c...@optinet.net Hierdie e-pos en sy inhoud is onderhewig aan 'n regskennisgewing oor elektroniese pos wat gelees kan word by http://www.naspers.com/afrikaans/voorbehoud.php 'n Afskrif kan aangevra word by c...@optinet.net -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com
Re: Announcing Splainer -- Open Source Solr Sandbox
Cool Doug! I look forward to digging into this. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Fri, Aug 22, 2014 at 10:34 AM, Doug Turnbull dturnb...@opensourceconnections.com wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com
Re: Announcing Splainer -- Open Source Solr Sandbox
What are the dependencies here in terms of solr config? Looks like it's dependent on highlighting at a minimum? I tried the example url and got a 500 with this stack trace once I inspected the response of the generated URI: java.lang.NullPointerException at org.apache.solr.handler.component.HighlightComponent.finishStage(HighlightComponent.java:194) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:331) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1963) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:777) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:418) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:368) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:942) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1004) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:744) On Fri, Aug 22, 2014 at 9:34 AM, Doug Turnbull dturnb...@opensourceconnections.com wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull Search Big Data Architect OpenSource Connections http://o19s.com
RE: Announcing Splainer -- Open Source Solr Sandbox
Ralph good catch. Thanks for the feedback! We should try without highlighting when a query with highlighting fails. In general we want to keep the requirements to a minimum. Right now it looks like highlighting is a requirement, but that shouldn't be the case. Highlighting should only be a value-add. (so yes that is a bug) -Doug From: ralph tice Sent: 8/22/2014 1:59 PM To: solr-user@lucene.apache.org Subject: Re: Announcing Splainer -- Open Source Solr Sandbox What are the dependencies here in terms of solr config? Looks like it's dependent on highlighting at a minimum? I tried the example url and got a 500 with this stack trace once I inspected the response of the generated URI: java.lang.NullPointerException at org.apache.solr.handler.component.HighlightComponent.finishStage(HighlightComponent.java:194) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:331) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1963) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:777) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:418) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:368) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:942) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1004) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:744) On Fri, Aug 22, 2014 at 9:34 AM, Doug Turnbull dturnb...@opensourceconnections.com wrote: Greetings from the OpenSource Connections Team! We're happy to announce we've taken core sandbox of our search relevancy product Quepid and open sourced it as Splainer (http://splainer.io). Splainer is a search sandbox that explains search results in a human readable form as you work. By being a *sandbox* it differs from parsing tools such as explain.solr.pl by letting you tweak and tweak and tweak without leaving the tool itself. In short, it helps you work faster to solve relevancy problems. Simply paste in a Solr URL and Splainer goes to work. Splainer is entirely driven by your browser (there's no backend -- its all static js/html/css and uses HTML local storage to store a few settings for you). So if your browser can see it, Splainer can work with it. Anyway, we've started getting great use out of the tool, and would also like to gather feedback from the community by sharing it. We're open to ideas, bug reports, pull requests, etc. Relevant links: Blog Post announcing Splainer: http://opensourceconnections.com/blog/2014/08/18/introducing-splainer-the-open-source-search-sandbox-that-tells-you-why/ Splainer: http://splainer.io Splainer on Github (open sourced as Apache 2) http://github.com/o19s/splainer These features (and a ton more) are also in our relevancy testing product Quepid: http://quepid.com Bugs/feedback/complaints/ideas/questions/contributions/etc welcome. Thank you for your time! -- Doug Turnbull
