FYI everyone, I've updated the README.md to be fully up to date for Solr
6.0 and the latest plugin release.
https://github.com/healthonnet/hon-lucene-synonyms/blob/master/README.md
On Fri, Jun 17, 2016 at 2:34 PM, MaryJo Sminkey wrote:
> > OK - Slapping forehead now...
> 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
OK - Slapping forehead now... D'oh!
1.2 wrote:
> Hi all -
>
> I've successfully run the hon-lucene-synonyms plugin from the Admin
> console by adding the following to the Raw Query Parameters field...
>
>
> =text=synonym_edismax=true=1.2=1.1
>
> I got those from the Read Me on the github
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
Hi all -
I've successfully run the hon-lucene-synonyms plugin from the Admin console
by adding the following to the Raw Query Parameters field...
=text=synonym_edismax=true=1.2=1.1
I got those from the Read Me on the github account.
Now I'm trying to make this work via a requestHandler in
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.
On Tue, Jun 7, 2016 at
I'm really thinking this just might not be the right tool for us, what we
really need is a solution that works like the normal synonym filter does,
just with proper multi-term support, so I can apply the synonyms only on
certain fields (copied fields) that have their own, lower boost settings.
The
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 appears as phrases, to appear higher than matches for the same
term
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
Yeah I thought the scale of the boosts were off as well but got caught up
verifying that the plugin was working. My colleague suggested that it could
be that because small block is a phrase that it would get a higher score in
matching because you basically get a phrase match each time which causes
Oh thanks, yeah I did miss that one field which had a parent type with the
normal synonym filter. However, that's our product SKU field so really
doesn't even come into play. I verified that none of the other fields have
a synonym filter set and even removed the productumbertext just to make
sure
>
> Advice: make sure on the schema that none of the fields your are running
> queries against do any complex query operations, especially make sure they
> aren't doing additional synonym resolution against the same file.
>
BTW. I'd do this first before messing with MM
Mary Jo.
It appears to be working correctly but you have a very complex query going
on so it can be confusing. Assuming you are using the queryParser as
provided in examples your query would look like "+sbc" when it enters the
queryParser and would look like "+((sbc)^2.0 (sb)^0.5 (small
Yes, query parameters/modifications mentioned in the readme. Beyond those
I don't have useful advice at this point
On Jun 4, 2016 10:56 PM, "MaryJo Sminkey" wrote:
> On Sat, Jun 4, 2016 at 11:47 PM, John Bickerstaff <
> j...@johnbickerstaff.com>
> wrote:
>
> > MaryJo - I'm
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
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.
You may know about them already, but if it's been a while since you looked,
those may help...
On Jun 3, 2016 12:28 PM,
On some additional tests, it looks like it's the phrase matching in
particular that is the issue, if I take that out I do seem to be getting
better results. I definitely don't want to get rid of those so need to find
a way to make them work together.
Sent with MailTrack
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
Yes, I get that, thanks.
On Jun 1, 2016 6:38 PM, "Joe Lawson"
wrote:
> 2.0 is compiled with Solr 5 and Java 7. It uses the namespace
> solr.SynonymExpandingExtendedDismaxQParserPlugin
>
> 5.0.4 is compiled with Solr 6 and Java 8 and is the first release that
2.0 is compiled with Solr 5 and Java 7. It uses the namespace
solr.SynonymExpandingExtendedDismaxQParserPlugin
5.0.4 is compiled with Solr 6 and Java 8 and is the first release that made
it to maven central. It uses the namespace
Just to be clear, I got version 2.0 of the jar from github... should I be
look for something in a maven repository? A bit confused at this point
given all the version numbers...
I want the latest and greatest unless there's any special considerations..
Thanks for the assistance!
On Jun 1, 2016
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
Nothing up until 5.0.4 was distributed on maven central. 5.0 -> 5.0.4 was
just a bunch of clean up to get it ready for maven (including the namespace
change).
Being that nearly all docs and articles talking about the plugin reference
the old 2.0 one could reasonably get confused as to what config
On 6/1/2016 1:10 PM, John Bickerstaff wrote:
> @Joe:
>
> Is it possible that the jar's package name does not match the entry in the
> sample solrconfig.xml file?
>
> The solrconfig.xml example file in the test directory contains the
> following package name:
>
I mean the 5.0 namespace is different from the 2.0 not 3.0.
On Jun 1, 2016 5:43 PM, "Joe Lawson"
wrote:
2.0 is different from 3.0 so check the test config that is associated with
the 2.0 release. Ie
2.0 is different from 3.0 so check the test config that is associated with
the 2.0 release. Ie
https://github.com/healthonnet/hon-lucene-synonyms/blob/8f736da053510911517fcb8a712b1d8ca5c920d2/src/test/resources/solr/collection1/conf/example_solrconfig.xml
On Jun 1, 2016 3:10 PM, "John
@Joe:
Is it possible that the jar's package name does not match the entry in the
sample solrconfig.xml file?
The solrconfig.xml example file in the test directory contains the
following package name:
However, the jar file (when unzipped) has the following directory structure
down to the same
I tried this - it didn't fail. I don't know if it really started in
Denable.runtime.lib=true mode or not:
service solr start -Denable.runtime.lib=true
Of course, I'd still really rather be able to just drop jars into
/var/solr/data/lib and have them work...
Thanks all.
On Wed, Jun 1, 2016 at
ter-synonym-handling-in-solr/>
> >> >> > > > >>
> >> >> > > > >> In addition to the already-mentioned projects, there is
> also:
> >> >> > > > >>
> >> >> > > > >> <https:
ways to work around the
>> fact
>> >> > that
>> >> > > > >> Lucene’s QueryParser splits on whitespace before sending text
>> to
>> >> > > > analysis,
>> >> > > > >> one token at a time, so in a synonym filter, multi-word
>> synonyms
>> >> can
>> >> > > > never
>> >> &
So - the instructions on using the Blob Store API say to use the
Denable.runtime.lib=true option when starting Solr.
Thing is, I've installed per the "for production" instructions which gives
me an entry in /etc/init.d called solr.
Two questions.
To test this can I still use the start.jar in
Ahhh - gotcha.
Well, not sure why it's not picked up - seems lots of other jars are...
Maybe Joe will comment...
On Wed, Jun 1, 2016 at 10:22 AM, MaryJo Sminkey wrote:
> That refers to running Solr in cloud mode. We aren't there yet.
>
> MJ
>
>
>
> On Wed, Jun 1, 2016 at
That refers to running Solr in cloud mode. We aren't there yet.
MJ
On Wed, Jun 1, 2016 at 12:20 PM, John Bickerstaff
wrote:
> Hi Mary Jo,
>
> I'll point you to Joe's earlier comment about needing to use the Blob Store
> API... He put a link in his response.
>
> I'm
Hi Mary Jo,
I'll point you to Joe's earlier comment about needing to use the Blob Store
API... He put a link in his response.
I'm about to try that today... Given that Joe is a contributor to
hon_lucene there's a good chance his experience is correct here -
especially given the evidence
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
Thanks Shawn
Yup - I created a /lib inside my $SOLR_HOME directory (which by default was
/var/solr/data)
I put the hon_lucene. jar file in there and rebooted - same errors
about class not found.
Tried again in what looked like the next most obvious spot
server/solr-webapp/webapp/WEB-INF/lib
On 5/31/2016 3:13 PM, John Bickerstaff wrote:
> The suggestion on the readme is that I can drop the
> hon_lucene_synonyms jar file into the $SOLR_HOME directory, but this
> does not seem to be working - I'm getting class not found exceptions.
What I typically do with *all* extra jars
t;> >> > > > >> one token at a time, so in a synonym filter, multi-word
>> synonyms
>> >> can
>> >> > > > never
>> >> > > > >> match and add alternatives. See <
>> >> > > > >> https://issues.a
ixed, there is still work to do
> getting
> >> > > > >> (e)dismax to work with the modified Lucene QueryParser, and
> >> > addressing
> >> > > > >> problems with how queries are constructed from Lucene’s
> >>
gt; > j...@johnbickerstaff.com>
>> > > > >> wrote:
>> > > > >> >
>> > > > >> > Thanks Chris --
>> > > > >> >
>> > > > >> > The two projects I'm aware of are:
>> > > >
ene QueryParser, and
> > > > addressing
> > > > > > >> problems with how queries are constructed from Lucene’s
> > > “sausagized”
> > > > > > token
> > > > > > >> stream.
> > > > > > >>
> > &
t; wrote:
> > > > > >> >
> > > > > >> > Thanks Chris --
> > > > > >> >
> > > > > >> > The two projects I'm aware of are:
> > > > > >> >
> > > > > >> > ht
; > > > >> >
> > > > >>
> > > >
> > >
> >
> https://lucidworks.com/blog/2014/07/12/solution-for-multi-term-synonyms-in-lucenesolr-using-the-auto-phrasing-tokenfilter/
> > > > >> >
> > > > >
hu, May 26, 2016 at 12:01 PM, Chris Morley <
> ch...@depahelix.com
> > >
> > > >> wrote:
> > > >> >
> > > >> >> Chris Morley here, from Wayfair. (Depahelix = my domain)
> > > >> >>
> > > >> >
;> We worked mostly off of Ted Sullivan's work and also off of some
> > >> >> suggestions from Koorosh Vakhshoori. We have gotten to a point
> where
> > >> we
> > >> >> have a more sophisticated internal implementation, however, we've
> &g
(now at Lucidworks) and Simon Hughes of Dice.com have
> >> also
> >> >> done work in this area.
> >> >>
> >> >> It should be very possible to get this kind of thing working on
> >> >> SolrCloud. I haven't tried it yet
done work in this area.
>> >>
>> >> It should be very possible to get this kind of thing working on
>> >> SolrCloud. I haven't tried it yet but I think theoretically, it should
>> >> just work. The synonyms stuff is mostly about doing things at index
>> time
>> >> and query time. The index time stuf
;> directly, while the query time stuff might pose some issues, but
> probably
> >> not too bad, if there are any issues at all.
> >>
> >> I've had decent luck porting our various plugins from 4.10.x to 5.5.0
> >> because a lot of stuff is just Java, and it still works
too bad, if there are any issues at all.
>>
>> I've had decent luck porting our various plugins from 4.10.x to 5.5.0
>> because a lot of stuff is just Java, and it still works within the Jetty
>> context.
>>
>> -Chris.
>>
>>
>>
>>
;
> -Chris.
>
>
>
>
>
> From: "John Bickerstaff" <j...@johnbickerstaff.com>
> Sent: Thursday, May 26, 2016 1:51 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr Cloud and Multi-word Synonyms :: synonym_edism
.
From: "John Bickerstaff" <j...@johnbickerstaff.com>
Sent: Thursday, May 26, 2016 1:51 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Cloud and Multi-word Synonyms :: synonym_edismax parser
Hey Jeff (or anyone interested in multi-wor
fixing typo:
http://wiki.apache.org/solr/QueryParser (search the page for
synonym_edismax)
On Thu, May 26, 2016 at 11:50 AM, John Bickerstaff wrote:
> Hey Jeff (or anyone interested in multi-word synonyms) here are some
> potentially interesting links...
>
>
Hey Jeff (or anyone interested in multi-word synonyms) here are some
potentially interesting links...
http://wiki.apache.org/solr/QueryParser (search the page for
synonum_edismax)
https://nolanlawson.com/2012/10/31/better-synonym-handling-in-solr/ (blog
post about what became the
Oh, interesting. I’ve certainty encountered issues with multi-word synonyms,
but I hadn’t come across this. If you end up using it with a recent solr
verison, I’d be glad to hear your experience.
I haven’t used it, but I am aware of one other project in this vein that you
might be interested
Ahh - for question #3 I may have spoken too soon. This line from the
github repository readme suggests a way.
Update: We have tested to run with the jar in $SOLR_HOME/lib as well, and
it works (Jetty).
I'll try that and only respond back if that doesn't work.
Questions 1 and 2 still stand of
Hi all,
I'm creating a Solr Cloud that will index and search medical text.
Multi-word synonyms are a pretty important factor.
I find that there are some challenges around multi-word synonyms and I also
found on the wiki that there is a recommended 3rd-party parser
(synonym_edismax parser)
56 matches
Mail list logo