Hi Jan,

Well, I have very likely confused some old documentation to be up to date, but 
all I did was to google for "ExtendedDisMax" and clicked on the first result:

https://wiki.apache.org/solr/ExtendedDisMax

I could only assume that this was a valid page since it belongs to 
wiki.apache.org/solr/ and nowhere on the page it says anything about the 
documentation being deprecated or having moved somewhere else. I now can see 
that the last modification date of that page is August 2013, but that is 
written in a small font at the very bottom of the page, so not something I 
noticed before.

So, should I assume that the "Confluence wiki" is the correct place for all 
documentation, even for solr 4.6?

I hope you can understand my confusion, since there seem to be 3 official 
documentation sites (wiki.apache.org/solr/, 
cwiki.apache.org/confluence/display/solr/ and lucene.apache.org/solr/), with no 
clear indication anywhere (that I could find) which site should be used or how 
they complement each other.

Also I would like to thank you for explaining that the query parses, response 
writers etc are built in in Solr now, so they don't need to be configured at 
all. I just am a bit confused about the fact that nobody thought that the 
documentation should be just as clear about this as you have been here. :)

Regards
/Jimi

-----Original Message-----
From: Jan Høydahl [mailto:jan....@cominvent.com] 
Sent: Monday, February 29, 2016 12:52 PM
To: solr-user@lucene.apache.org
Subject: Re: ExtendedDisMax configuration nowhere to be found

Hi Jimi,

I believe you may be confusing some old config and thus was lead to believe 
that you need to pre-configure anything in order to start using dismax / 
edismax.

In ealier versions of Solr, there was both a <queryParser> named “dismax” as 
well as a <requestHandler> named “dismax”, setting the defType parameter to 
“dismax”. This caused some confusion and was removed in 3.1 (see 
https://issues.apache.org/jira/browse/SOLR-2363).

All the built-in Solr Query parsers mentioned in the Reference Guide, such as 
“lucene”, “dismax”, “edismax” etc are pre-registered with these keywords, so no 
need for explicit <queryParser> tags. And you can test them out through the 
normal /select end point without configuring a new <requestHandler> section in 
solrconfig.xml. You may of course choose to create your own <requestHandler> 
section with predefined defaults for the defType, qf, pf, pf2, pf3, tie, mm… 
parameters once you got all those defined, but in the simplest case, all you 
need to do is as described in the RefGuide:

   
http://localhost:8983/solr/techproducts/select?q=foo&defType=edismax&qf=title^10,body^2

Feel free to ask further questions if you don’t get it right.

PS: Solr has a rich library of built-in components ready to use out of the box. 
There are many query parsers, response writers, function queries, field types 
etc that you can start using directly. Then you have some “contrib” features 
which need to be explicitly added to class path and registered in 
solrconfig.xml before using, and the same with 3rd party components you 
download elsewhere. But most of the bundled stuff you read about in the 
RefGuide is already integrated, ready to use.

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

> 29. feb. 2016 kl. 09.20 skrev jimi.hulleg...@svensktnaringsliv.se:
> 
> There is no need to deliberately misinterpret what I wrote. What I was trying 
> to say was that "automagical" things don't belong in a professional 
> environment, because it is hiding important information from people. And this 
> is bad as it is, but if it on top of that is the *intended* meaning for 
> things in solr to be "automagical", ie *deliberately* hiding information from 
> the solr users, well that attitude is just baffling in my eyes. I can only 
> hope that I misunderstood you.
> 
> /Jimi
> 
> -----Original Message-----
> From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
> Sent: Sunday, February 28, 2016 11:44 PM
> To: solr-user@lucene.apache.org
> Subject: Re: ExtendedDisMax configuration nowhere to be found
> 
> So, all this hard work that people have put into Solr to make it more like a 
> Disney theme park is just... wasted... on you? Sigh. Okay, I guess we can't 
> please everyone.
> 
> -- Jack Krupansky
> 
> On Sun, Feb 28, 2016 at 5:40 PM, <jimi.hulleg...@svensktnaringsliv.se>
> wrote:
> 
>> I have no problem with automatic. It is "automagicall" stuff that I 
>> find a bit hard to like. Ie things that are automatic, but doesn't 
>> explain how and why they are automatic. But Disney Land and Disney 
>> World are actually really good examples of places where the magic 
>> stuff is suitable, ie in themeparks, designed mostly for kids. In the 
>> grown up world of IT, most people prefer logical and documented stuff, not 
>> things that "just works"
>> without explaining why. No offence :)
>> 
>> /Jimi
>> 
>> -----Original Message-----
>> From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
>> Sent: Sunday, February 28, 2016 11:31 PM
>> To: solr-user@lucene.apache.org
>> Subject: Re: ExtendedDisMax configuration nowhere to be found
>> 
>> Yes, it absolutely is automagic - just look at those examples in the 
>> Confluence ref guide. No special request handler is needed - just the 
>> normal default handler. Just the defType and qf parameters are needed
>> - as shown in the wiki examples.
>> 
>> It really is that simple! All you have to supply is the list of 
>> fields to query (qf) and your actual query text (q).
>> 
>> I know, I know... some people just can't handle automatic. (Some 
>> people hate DisneyLand/World!)
>> 
>> -- Jack Krupansky
>> 
>> On Sun, Feb 28, 2016 at 5:16 PM, 
>> <jimi.hulleg...@svensktnaringsliv.se>
>> wrote:
>> 
>>> I'm sorry, but I am still confused. I'm expecting to see some 
>>> <requestHandler> tag somewhere. Why doesn't the documentation nor 
>>> the example solrconfig.xml contain such a tag?
>>> 
>>> If the edismax requestHandler is defined automatically, the 
>>> documentation should explain that. Also, there should still exist 
>>> some xml code that corresponds exactly to that default setup, right?
>>> That is what I'm looking for.
>>> 
>>> For now, this edismax thing seems to work "automagically", and I 
>>> prefer to understand why and how something works.
>>> 
>>> /Jimi
>>> 
>>> -----Original Message-----
>>> From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
>>> Sent: Sunday, February 28, 2016 10:58 PM
>>> To: solr-user@lucene.apache.org
>>> Subject: Re: ExtendedDisMax configuration nowhere to be found
>>> 
>>> Consult the Confluence wiki for more recent doc:
>>> 
>>> https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax
>>> +Q
>>> uery+Parser
>>> 
>>> You can specify all the parameters on your query request as in the 
>>> examples, or by placing the parameters in the "defaults" section for 
>>> your request handler in solrconfig.xml.
>>> 
>>> 
>>> -- Jack Krupansky
>>> 
>>> On Sun, Feb 28, 2016 at 2:42 PM,
>>> <jimi.hulleg...@svensktnaringsliv.se>
>>> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> I want to setup ExtendedDisMax in our solr 4.6 server, but I can't 
>>>> seem to find any example configuration for this. Ie the 
>>>> configuration needed in solrconfig.xml. In the wiki page 
>>>> http://wiki.apache.org/solr/ExtendedDisMax it simply says:
>>>> 
>>>> "Extended DisMax is already configured in the example 
>>>> configuration, with the name edismax."
>>>> 
>>>> But this is not true for the solrconfig.xml in our setup (it only 
>>>> contains an example for dismax, not edismax), and I downloaded the 
>>>> latest solr zip file (solr 5.5.0), and it didn't have either dismax 
>>>> or edismax in any of its solrconfig.xml files.
>>>> 
>>>> Why is it so hard to find this configuration? Am I missing 
>>>> something obvious?
>>>> 
>>>> Regards
>>>> /Jimi
>>>> 
>>> 
>> 

Reply via email to