> For someone familiar with Solr, will it be an issue to run those examples
> in a Solr instance instead ?
>
You can't run ES code on Solr, and the syntax is quite different, so you do
have to figure out how to convert it yourself and it's not always very
obvious. There is an appendix that covers
> OK - Slapping forehead now... D'oh!
>
> 1.2
> Float, not int!
>
LOL, we've all been there. I'm surprised I didn't notice that myself.
MJ
On Fri, Jun 17, 2016 at 2:15 PM, John Bickerstaff
wrote:
> If I do NOT add the last line and only have the line that sets
> synonyms=true, it appears to work fine.
>
> I see the dot notation all over the sample entries in solrconfig.xml... Am
> I missing something
et's hope we see some traction on it soon, as many people suffer from
> this issue.
>
> Upayavira
>
> On Thu, 9 Jun 2016, at 09:10 PM, MaryJo Sminkey wrote:
> > On Thu, Jun 9, 2016 at 1:50 PM, Joe Lawson <
> > jlaw...@opensourceconnections.com> wrote:
> >
> >
On Thu, Jun 9, 2016 at 1:50 PM, Joe Lawson <
jlaw...@opensourceconnections.com> wrote:
> The auth-phrasing-token (APT) filter is a two pronged solution that
> requires index and query time processes versus hon-lucene-synonyms (HLS)
> which is strictly a query time implementation. The primary take
On Thu, Jun 9, 2016 at 11:06 AM, Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> Honestly half the time I run into this problem, I end up creating a
> QParserPlugin because I need to do something specific. With a QParserPlugin
> I can run whatever analysis, slicing and dicing of the
> MaryJo you might want to start a new thread, I think we kinda hijacked this
> one. Also if you are interested in tuning queries check out
> http://splainer.io/ and https://www.quepid.com which are interactive tools
> (both of which my company makes) to tune for search relevancy.
>
Okay I
, MaryJo Sminkey <mjsmin...@gmail.com> wrote:
> Here's the issue I am still having with getting the right search relevancy
> with the synonym plugin in place. We typically have users searching on
> multiple terms, and we want matches across multiple terms, particularly
> those that
=mjsmin...@gmail.com=22>
On Mon, Jun 6, 2016 at 9:39 PM, MaryJo Sminkey <mjsmin...@gmail.com> wrote:
>
> On Mon, Jun 6, 2016 at 7:36 PM, Joe Lawson <
> jlaw...@opensourceconnections.com> wrote:
>
>>
>> We were thinking, as you experimented with, that the 0.5 an
On Mon, Jun 6, 2016 at 7:36 PM, Joe Lawson <
jlaw...@opensourceconnections.com> wrote:
>
> We were thinking, as you experimented with, that the 0.5 and 2.0 boosts
> were no match for the product name and keyword field boosts so that would
> influence your search as well.
Yeah I definitely will
complex query operations, especially make sure they
> aren't doing additional synonym resolution against the same file.
>
> I think you are getting hit by the MM bug. Try tuning it way down to
> something like 0.01% and see how the matches go.
>
>
>
> On Fri, Jun 3, 20
On Sat, Jun 4, 2016 at 11:47 PM, John Bickerstaff
wrote:
> MaryJo - I'm on vacation but can't resist... iirc there are some very
> useful query modifications suggested in the readme on the github for the
> plugin... can't access right now.
>
I'm assuming you mean the
Just a followup on this, I found that the method below using URL params
doesn't work when using the Rest API, if you try to set the field in your
facet object to something like "{!ex=dt}doctype" it throws an error. Here's
the documentation on the correct method to use with the API.
.io/install?source=signature=en=mjsmin...@gmail.com=22>
On Fri, Jun 3, 2016 at 2:21 PM, MaryJo Sminkey <mjsmin...@gmail.com> wrote:
> Okay so big thanks for the help with getting the hon_lucene_synonyms
> plugin working. That is a big load off to finally have a solution in place
> f
Okay so big thanks for the help with getting the hon_lucene_synonyms plugin
working. That is a big load off to finally have a solution in place for all
our multi-term synonyms. We did find that the information in Step 8 about
the plugin showing "SynonymExpandingExtendedDismaxQParser" for QParser
On Fri, Jun 3, 2016 at 1:25 AM, Erick Erickson
wrote:
> We can always use more documentation. One of the
> valuable things about people getting started is that it's an
> opportunity to clarify documents. Sometimes the people who
> develop/write the docs jump into the
d things I never knew about Solr/Lucene!
>
> I think one of the most valuable lessons was "Somebody's
> probably run into this before, I wonder what _they_ did?"
> ;)
>
> Best,
> Erick
>
> On Thu, Jun 2, 2016 at 9:46 PM, MaryJo Sminkey <mjsmin...@gmail.com>
t values.
>
> Personally I don't think it's possible, but will be interested to hear
> others input, since it's a very common situation for me - I cache the first
> result in memcached and tag future queries as related to the first.
>
> Or could you always make 2 calls ba
iginal (again), and
> one with the filters), the caches should help massively.
>
>
>
> On 02/06/16 19:07, MaryJo Sminkey wrote:
>
>> And you're saying the count for the second query is different than what
>> was
>> returned in the facet? You may need to che
q=video=true=*=20=true=team
>
> Then when I specify which team
> http://
> **select?q=video=true=*=20=true=team=team:rollback
>
> The counts are obviously different now, as the result set is limited to
> one team.
>
> Sas
>
> -Original Message-
> From: MaryJ
In other words... to diagnose such a problem it would really help to see
the exact parameters and filters you are using on each of the searches.
Mary Jo
On Thu, Jun 2, 2016 at 1:47 PM, Jamal, Sarfaraz <
sarfaraz.ja...@verizonwireless.com.invalid> wrote:
> Hello Everyone,
>
> I am working on
Jamai - what is your q= set to? And do you have a fq for the original
query? I have found that if you do a wildcard search (*.*) you have to be
careful about other parameters you set as that can often result in the
numbers returned being off. In my case, my defaults had things like edismax
Yup that was the issue for us as well. It doesn't seem to be throwing the
class error now, although I have not been able to successfully get back
results that seem to be using it, it's showing up as the deftype in my
params but the QParser in my debug is the normal edismax one. I will have
to play
t; out the tests for working examples. I'll try to update it soon. I've run
> the plugin on Solr 5 and 6, solrcloud and standalone. For running in
> SolrCloud make sure you follow
>
> https://cwiki.apache.org/confluence/display/solr/Adding+Custom+Plugins+in+SolrCloud+Mode
>
> On
So we still can't get this to work, here's the latest update my server guy
gave me: It seems to not matter where the file is located, it does not
load. Yet, the the Solr Java class path shows the file has loaded. Only
this path (./server/lib/hon-lucene-synonyms-2.0.0.jar) will work in that it
auto phrasing one.. If I'm
> successful, I'll post back.
>
> On Mon, May 30, 2016 at 3:45 PM, MaryJo Sminkey <mjsmin...@gmail.com>
> wrote:
>
> > This is a very timely discussion for me as well as we're trying to tackle
> > the multi term synonym issue as well and
This is a very timely discussion for me as well as we're trying to tackle
the multi term synonym issue as well and have not been able to hon-lucene
plugin to work, the jar shows up as installed but when we set up the sample
request handler it throws this error:
27 matches
Mail list logo