Which is what I believe you had as a working example in your Dropbox images.

So, does it work now?

Regards,
   Alex.
----
http://www.solr-start.com/ - Resources for Solr users, new and experienced


On 16 March 2017 at 22:22, Aman Deep Singh <amandeep.coo...@gmail.com> wrote:
> If I give query in quotes it converted query in to graph query as
>
> Graph(cust_sh6:"one plus one" hasBoolean=false hasPhrase=false)
>
>
> On 17-Mar-2017 1:38 AM, "Alexandre Rafalovitch" <arafa...@gmail.com> wrote:
>
>> Oh. Try your query with quotes around the phone phrase:
>> q="one plus one"
>>
>> My hypothesis is:
>> Query parser splits things on whitespace before passing it down into
>> analyzer chain as individual match attempts. The Analysis UI does not
>> take that into account and treats the whole string as phrase sent. You
>> say
>> outputUnigrams="false" outputUnigramsIfNoShingles="false"
>> So, every single token during the query gets ignored because there is
>> nothing for it to shingle with.
>>
>> I am not sure why it would have worked in Solr 4.
>>
>> Regards,
>>    Alex.
>> ----
>> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>>
>>
>> On 16 March 2017 at 13:06, Aman Deep Singh <amandeep.coo...@gmail.com>
>> wrote:
>> > For images dropbox url is
>> > https://www.dropbox.com/sh/6dy6a8ajabjtxrt/
>> AAAoxhZQe2vp3sTl3Av71_eHa?dl=0
>> >
>> >
>> > On Thu, Mar 16, 2017 at 10:29 PM Aman Deep Singh <
>> amandeep.coo...@gmail.com>
>> > wrote:
>> >
>> >> Yes I have reloaded the core after config changes
>> >>
>> >>
>> >> On 16-Mar-2017 10:28 PM, "Alexandre Rafalovitch" <arafa...@gmail.com>
>> >> wrote:
>> >>
>> >> Images do not come through.
>> >>
>> >> But I was wrong too. You use eDismax and pass "cust_shingle" in, so
>> >> the "df" value is irrelevant.
>> >>
>> >> You definitely reloaded the core after changing definitions?
>> >> ----
>> >> http://www.solr-start.com/ - Resources for Solr users, new and
>> experienced
>> >>
>> >>
>> >> On 16 March 2017 at 12:37, Aman Deep Singh <amandeep.coo...@gmail.com>
>> >> wrote:
>> >> > Already check that i am sending sceenshots of various senarios
>> >> >
>> >> >
>> >> > On Thu, Mar 16, 2017 at 7:46 PM Alexandre Rafalovitch <
>> >> arafa...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Sanity check. Is your 'df' pointing at the field you think it is
>> >> >> pointing at? It really does look like all tokens were eaten and
>> >> >> nothing was left. But you should have seen that in the Analysis
>> screen
>> >> >> too, if you have the right field.
>> >> >>
>> >> >> Try adding echoParams=all to your request to see the full final
>> >> >> parameter list. Maybe some parameters in initParams sections override
>> >> >> your assumed config.
>> >> >>
>> >> >> Regards,
>> >> >>    Alex.
>> >> >> ----
>> >> >> http://www.solr-start.com/ - Resources for Solr users, new and
>> >> experienced
>> >> >>
>> >> >>
>> >> >> On 16 March 2017 at 08:30, Aman Deep Singh <
>> amandeep.coo...@gmail.com>
>> >> >> wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > Recently I migrated from solr 4 to 6
>> >> >> > IN solr 4 shinglefilterfactory is working correctly
>> >> >> > my configration  i
>> >> >> >
>> >> >> >     <fieldType name="text_shingle" class="solr.TextField"
>> >> >> > positionIncrementGap="100">
>> >> >> >         <analyzer type="index">
>> >> >> >          <tokenizer class="solr.WhitespaceTokenizerFactory"/>
>> >> >> >          <filter class="solr.ShingleFilterFactory"
>> minShingleSize="2"
>> >> >> > maxShingleSize="5"
>> >> >> >                  outputUnigrams="false"
>> >> >> > outputUnigramsIfNoShingles="false" />
>> >> >> >           <filter class="solr.LowerCaseFilterFactory"/>
>> >> >> >         </analyzer>
>> >> >> >         <analyzer type="query">
>> >> >> >           <tokenizer class="solr.WhitespaceTokenizerFactory"/>
>> >> >> >          <filter class="solr.ShingleFilterFactory"
>> minShingleSize="2"
>> >> >> > maxShingleSize="5"
>> >> >> >                  outputUnigrams="false"
>> >> >> > outputUnigramsIfNoShingles="false" />
>> >> >> >           <filter class="solr.LowerCaseFilterFactory"/>
>> >> >> >           <filter class="solr.PositionFilterFactory"/>
>> >> >> >         </analyzer>
>> >> >> >       </fieldType>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > But after updating to solr 6 shingles is not working ,schema is as
>> >> >> > below,
>> >> >> >
>> >> >> >         <fieldType name="text_shingle" class="solr.TextField"
>> >> >> > positionIncrementGap="100">
>> >> >> >         <analyzer type="index">
>> >> >> >          <tokenizer class="solr.WhitespaceTokenizerFactory"/>
>> >> >> >          <filter class="solr.ShingleFilterFactory"
>> minShingleSize="2"
>> >> >> > maxShingleSize="5"
>> >> >> >                  outputUnigrams="false"
>> >> >> > outputUnigramsIfNoShingles="false" />
>> >> >> >           <filter class="solr.LowerCaseFilterFactory"/>
>> >> >> >         </analyzer>
>> >> >> >         <analyzer type="query">
>> >> >> >           <tokenizer class="solr.WhitespaceTokenizerFactory"/>
>> >> >> >          <filter class="solr.ShingleFilterFactory"
>> minShingleSize="2"
>> >> >> > maxShingleSize="5"
>> >> >> >                  outputUnigrams="false"
>> >> >> > outputUnigramsIfNoShingles="false" />
>> >> >> >           <filter class="solr.LowerCaseFilterFactory"/>
>> >> >> >         </analyzer>
>> >> >> >       </fieldType>
>> >> >> >
>> >> >> > Although in the Analysis tab is was showing proper shingle result
>> but
>> >> >> > when
>> >> >> > using in the queryParser it was not giving proper results
>> >> >> >
>> >> >> > my sample hit is
>> >> >> >
>> >> >> >
>> >> >> >
>> >> http://localhost:8983/solr/shingel_test/select?q=one%
>> 20plus%20one&wt=xml&debugQuery=true&defType=edismax&qf=cust_shingle
>> >> >> >
>> >> >> > it create the parsed query as
>> >> >> >
>> >> >> > <str name="rawquerystring">one plus one</str>
>> >> >> > <str name="querystring">one plus one</str>
>> >> >> > <str name="parsedquery">(+())/no_coord</str>
>> >> >> > <str name="parsedquery_toString">+()</str>
>> >> >> > <lst name="explain"/>
>> >> >> > <str name="QParser">ExtendedDismaxQParser</str>
>> >>
>> >>
>> >>
>>

Reply via email to