Query regarding Path Hierarchy tokenizer
Hello Community I am using Path Hierarchy Tokenizer in which i am storing a path as a field value. Tokenizer splits that path in different tokens and they can be used as synonyms. But while querying those tokens, solr is not able to parse the query. Can somebody please tell me how to query these kinds of tokens ? these are the tokens indexed "c:", "c:/usr", "c:/usr/local", "c:/usr/local/apache -- Kind Regards, Shubham Goswami Enterprise Software Engineer mobile: +91 7803886288 email: *shubham.gosw...@hotwax.co* *www.hotwax.co <http://www.hotwax.co/>*
Re: Query on stemming
Hi Paras/Jorn Thanks for your support. I am using Solr version 7.5. I tried with SnowballPorterFilterFactory class and its working fine. Thanks for your help. On Fri, Nov 1, 2019 at 5:52 PM Paras Lehana wrote: > Hi Shubham, > > I am getting the ClassNotFoundException while indexing after making the > > changes. > > > >- Please describe the error properly with full details. We need to see >what is exactly causing ClassNotFoundException in the trace. >- This seems to be a Java syntax error due to >*EnglishPorterFilterFactory**.java* being not available. Please confirm >if it's available in analysis directory. >- Also, what Solr version are you using? *EnglishPorterFilterFactory* is >already *deprecated* and I suggest you to use >*SnowballPorterFilterFactory* with *language="English" *instead. You >need to add the stemming in query time analysis chain too, otherwise, > query >as "bags" will not match with "bag" (indexed). > > > Hope this helps. > > On Fri, 1 Nov 2019 at 15:42, Shubham Goswami > wrote: > > > Hi Jorn > > > > Thanks for your response. > > Following is my field type definition and i am getting the > > ClassNotFoundException while indexing after making the changes. > > > >> positionIncrementGap="100" multiValued="true"> > > > > > >> ignoreCase="true"/> > > > > > > > > > > > >> ignoreCase="true"/> > >> ignoreCase="true" synonyms="synonyms.txt"/> > > > > > > > > > > On Fri, Nov 1, 2019 at 2:10 PM Jörn Franke wrote: > > > > > How did you define the field type? Probably you have syntax errors > there. > > > I recommend to use the schema rest api instead of schema xml as it will > > > give you better feedback on what is wrong and it allows you also better > > > versioning of the schema in a source code repository. > > > > > > https://lucene.apache.org/solr/guide/8_2/schema-api.html > > > > > > > > > > Am 01.11.2019 um 06:41 schrieb Shubham Goswami < > > > shubham.gosw...@hotwax.co>: > > > > > > > > Hello Community > > > > > > > > I am using a filter class EnglishPorterFilterFactory for stemming > > filter > > > > but because of usage of this class, my solr is not able reload the > > > schema. > > > > > > > > Can somebody please let me know what exactly this class does and how > > can > > > i > > > > implement stemming ? > > > > Any help will be appreciated. Thanks in advance. > > > > > > > > -- > > > > Kind Regards, > > > > Shubham Goswami > > > > Enterprise Software Engineer > > > > mobile: +91 7803886288 > > > > email: *shubham.gosw...@hotwax.co* > > > > *www.hotwax.co <http://www.hotwax.co/>* > > > > > > > > > -- > > Kind Regards, > > Shubham Goswami > > Enterprise Software Engineer > > mobile: +91 7803886288 > > email: *shubham.gosw...@hotwax.co* > > *www.hotwax.co <http://www.hotwax.co/>* > > > > > -- > -- > Regards, > > *Paras Lehana* [65871] > Development Engineer, Auto-Suggest, > IndiaMART Intermesh Ltd. > > 8th Floor, Tower A, Advant-Navis Business Park, Sector 142, > Noida, UP, IN - 201303 > > Mob.: +91-9560911996 > Work: 01203916600 | Extn: *8173* > > -- > IMPORTANT: > NEVER share your IndiaMART OTP/ Password with anyone. > -- Kind Regards, Shubham Goswami Enterprise Software Engineer mobile: +91 7803886288 email: *shubham.gosw...@hotwax.co* *www.hotwax.co <http://www.hotwax.co/>*
Re: Query on stemming
Hi Jorn Thanks for your response. Following is my field type definition and i am getting the ClassNotFoundException while indexing after making the changes. On Fri, Nov 1, 2019 at 2:10 PM Jörn Franke wrote: > How did you define the field type? Probably you have syntax errors there. > I recommend to use the schema rest api instead of schema xml as it will > give you better feedback on what is wrong and it allows you also better > versioning of the schema in a source code repository. > > https://lucene.apache.org/solr/guide/8_2/schema-api.html > > > > Am 01.11.2019 um 06:41 schrieb Shubham Goswami < > shubham.gosw...@hotwax.co>: > > > > Hello Community > > > > I am using a filter class EnglishPorterFilterFactory for stemming filter > > but because of usage of this class, my solr is not able reload the > schema. > > > > Can somebody please let me know what exactly this class does and how can > i > > implement stemming ? > > Any help will be appreciated. Thanks in advance. > > > > -- > > Kind Regards, > > Shubham Goswami > > Enterprise Software Engineer > > mobile: +91 7803886288 > > email: *shubham.gosw...@hotwax.co* > > *www.hotwax.co <http://www.hotwax.co/>* > -- Kind Regards, Shubham Goswami Enterprise Software Engineer mobile: +91 7803886288 email: *shubham.gosw...@hotwax.co* *www.hotwax.co <http://www.hotwax.co/>*
Query on stemming
Hello Community I am using a filter class EnglishPorterFilterFactory for stemming filter but because of usage of this class, my solr is not able reload the schema. Can somebody please let me know what exactly this class does and how can i implement stemming ? Any help will be appreciated. Thanks in advance. -- Kind Regards, Shubham Goswami Enterprise Software Engineer mobile: +91 7803886288 email: *shubham.gosw...@hotwax.co* *www.hotwax.co <http://www.hotwax.co/>*
Re: Query on changing FieldType
Hello Erick/Emir Thanks for your valuable suggestions. I will it keep in mind while doing such operations. Best, Shubham On Wed, Oct 23, 2019 at 5:56 PM Erick Erickson wrote: > Really, just don’t do this. Please. As others have pointed out, it may > look like it works, but it won’t. I’ve spent many hours tracking down why > clients got weird errors after making changes like this, sometimes weeks > later. Or more accurately, if you choose to change field types without > reindexing, please don’t ask for others to troubleshoot it when something > blows up. > > As far as creating a new core, if that takes a significant amount of time > relative to re-indexing, then you must be working with a very small index. > Those operations should take a couple of minutes, tops. > > Best, > Erick > > > On Oct 23, 2019, at 5:13 AM, Emir Arnautović < > emir.arnauto...@sematext.com> wrote: > > > > Hi Shubham, > > My guess that it might be working for text because it uses o.toString() > so there are no runtime errors while in case of others, it has to assume > some class so it does class casting. You can check in logs what sort of > error happens. But in any case, like Jason pointed out, that is a problem > that is just waiting to happen somewhere and the only way to make sure it > does not happen is to do full reindexing or to create a new field (with a > new name) and stop using the one that is wrong. Different field types are > indexed in different structures and with different defaults (e.g. for > docValues) and I would not rely on some features working after field type > changed. > > > > Thanks, > > Emir > > -- > > Monitoring - Log Management - Alerting - Anomaly Detection > > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > > > > > > >> On 23 Oct 2019, at 08:18, Shubham Goswami > wrote: > >> > >> Hi Jason > >> > >> Thanks for the response. > >> You are right that re-indexing is required after making any changes to > >> Schema even i am re-indexing the docs in which i have > >> changed the fieldtypes, but here Emir is talking about full re-indexing > >> i.e. deleting the existing/core and creating new one that is > >> time consuming i think. My doubt is that i am not able to change the > type > >> which has implementation classes like LongPointField/IntPointField to > the > >> type with implementation classes LongPointField/IntPointField.t > >> > >>But i am able to change into Text related fields like TextFields > >> and from TextFields to any other Int/Long type fields. > >> So i just want to know that what is exact dependency on these classes so > >> that iam able to change types of some fields ? > >> > >> Thanks > >> Shubham > >> > >> On Tue, Oct 22, 2019 at 6:29 PM Jason Gerlowski > >> wrote: > >> > >>> Hi Shubbham, > >>> > >>> Emir gave you accurate advice - you cannot (safely) change field types > >>> without reindexing. You may avoid errors for a time, and searches may > >>> even return the results you expect. But the type-change is still a > >>> ticking time bomb...Solr might try to merge segments down the road or > >>> do some other operation and blow up in unexpected ways. For more > >>> information on why this is, see the documentation here: > >>> https://lucene.apache.org/solr/guide/8_2/reindexing.html. > >>> > >>> Unfortunately there's no way around it. This, by the way, is why the > >>> community strongly recommends against using schema-guessing mode for > >>> anything other than experimentation. > >>> > >>> Best of luck, > >>> > >>> Jason > >>> > >>> On Tue, Oct 22, 2019 at 7:42 AM Shubham Goswami > >>> wrote: > >>>> > >>>> Hi Emir > >>>> > >>>> As you have mentioned above we cannot change field type after indexing > >>> once > >>>> and we have to do dull re-indexing again, I tried to change field type > >>> from > >>>> plong to pint which has implemented class solr.LongPointField and > >>>> solr.IntPointField respectively and it was showing error as expected. > >>>> But when i changed field types from pint/plong to any type which > >>>> has implemented class solr.TextField, in this case its working fine > and i > >>>> am able to index the document
Re: Query on changing FieldType
Hi Jason Thanks for the response. You are right that re-indexing is required after making any changes to Schema even i am re-indexing the docs in which i have changed the fieldtypes, but here Emir is talking about full re-indexing i.e. deleting the existing/core and creating new one that is time consuming i think. My doubt is that i am not able to change the type which has implementation classes like LongPointField/IntPointField to the type with implementation classes LongPointField/IntPointField.t But i am able to change into Text related fields like TextFields and from TextFields to any other Int/Long type fields. So i just want to know that what is exact dependency on these classes so that iam able to change types of some fields ? Thanks Shubham On Tue, Oct 22, 2019 at 6:29 PM Jason Gerlowski wrote: > Hi Shubbham, > > Emir gave you accurate advice - you cannot (safely) change field types > without reindexing. You may avoid errors for a time, and searches may > even return the results you expect. But the type-change is still a > ticking time bomb...Solr might try to merge segments down the road or > do some other operation and blow up in unexpected ways. For more > information on why this is, see the documentation here: > https://lucene.apache.org/solr/guide/8_2/reindexing.html. > > Unfortunately there's no way around it. This, by the way, is why the > community strongly recommends against using schema-guessing mode for > anything other than experimentation. > > Best of luck, > > Jason > > On Tue, Oct 22, 2019 at 7:42 AM Shubham Goswami > wrote: > > > > Hi Emir > > > > As you have mentioned above we cannot change field type after indexing > once > > and we have to do dull re-indexing again, I tried to change field type > from > > plong to pint which has implemented class solr.LongPointField and > > solr.IntPointField respectively and it was showing error as expected. > > But when i changed field types from pint/plong to any type which > > has implemented class solr.TextField, in this case its working fine and i > > am able to index the documents after changing its fieldtype with same and > > different id. > > > > So i want to know if is there any compatibility with implemented classes > ? > > > > Thanks > > Shubham > > > > On Tue, Oct 22, 2019 at 2:46 PM Emir Arnautović < > > emir.arnauto...@sematext.com> wrote: > > > > > Hi Shubham, > > > No you cannot. What you can do is to use copy field or update request > > > processor to store is as some other field and use that in your query > and > > > ignore the old one that will eventually disappear as the result of > segment > > > merges. > > > > > > HTH, > > > Emir > > > -- > > > Monitoring - Log Management - Alerting - Anomaly Detection > > > Solr & Elasticsearch Consulting Support Training - > http://sematext.com/ > > > > > > > > > > > > > On 22 Oct 2019, at 10:53, Shubham Goswami > > > > wrote: > > > > > > > > Hi Emir > > > > > > > > Thanks for the reply, i got your point. > > > > But is there any other way to do like one field could have two or > more > > > > different types defined ? > > > > or if i talk about my previous query, can we index some data for the > > > same > > > > field with different unique id after replacing the type ? > > > > > > > > Thanks again > > > > Shubham > > > > > > > > On Tue, Oct 22, 2019 at 1:23 PM Emir Arnautović < > > > > emir.arnauto...@sematext.com> wrote: > > > > > > > >> Hi Shubham, > > > >> Changing type is not allowed without full reindexing. If you do > > > something > > > >> like that, Solr will end up with segments with different types for > the > > > same > > > >> field. Remember that segments are immutable and that reindexing some > > > >> document will be in new segment, but old segment will still be there > > > and at > > > >> query type Solr will have mismatch between what is stated in schema > and > > > >> what is in segment. In order to change type you have to do full > > > reindexing > > > >> - create a new collection and reindex all documents. > > > >> > > > >> HTH, > > > >> Emir > > > >> -- > > > >> Monitoring - Log Management - Alerting - Anomaly Detection > > > >> Solr &am
Re: Query on changing FieldType
Hi Emir As you have mentioned above we cannot change field type after indexing once and we have to do dull re-indexing again, I tried to change field type from plong to pint which has implemented class solr.LongPointField and solr.IntPointField respectively and it was showing error as expected. But when i changed field types from pint/plong to any type which has implemented class solr.TextField, in this case its working fine and i am able to index the documents after changing its fieldtype with same and different id. So i want to know if is there any compatibility with implemented classes ? Thanks Shubham On Tue, Oct 22, 2019 at 2:46 PM Emir Arnautović < emir.arnauto...@sematext.com> wrote: > Hi Shubham, > No you cannot. What you can do is to use copy field or update request > processor to store is as some other field and use that in your query and > ignore the old one that will eventually disappear as the result of segment > merges. > > HTH, > Emir > -- > Monitoring - Log Management - Alerting - Anomaly Detection > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > > > > On 22 Oct 2019, at 10:53, Shubham Goswami > wrote: > > > > Hi Emir > > > > Thanks for the reply, i got your point. > > But is there any other way to do like one field could have two or more > > different types defined ? > > or if i talk about my previous query, can we index some data for the > same > > field with different unique id after replacing the type ? > > > > Thanks again > > Shubham > > > > On Tue, Oct 22, 2019 at 1:23 PM Emir Arnautović < > > emir.arnauto...@sematext.com> wrote: > > > >> Hi Shubham, > >> Changing type is not allowed without full reindexing. If you do > something > >> like that, Solr will end up with segments with different types for the > same > >> field. Remember that segments are immutable and that reindexing some > >> document will be in new segment, but old segment will still be there > and at > >> query type Solr will have mismatch between what is stated in schema and > >> what is in segment. In order to change type you have to do full > reindexing > >> - create a new collection and reindex all documents. > >> > >> HTH, > >> Emir > >> -- > >> Monitoring - Log Management - Alerting - Anomaly Detection > >> Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > >> > >> > >> > >>> On 22 Oct 2019, at 09:25, Shubham Goswami > >> wrote: > >>> > >>> Hello Community > >>> > >>> I have indexed some documents for which solr has taken its > type="plongs" > >> by > >>> auto guessing but i am trying to change its type="pint" and re-indexing > >> the > >>> same data with the same id and indexing the data with different id > where > >> id > >>> is unique key but it is showing error. > >>> > >>> Can somebody please let me know if it is possible or not, if not > possible > >>> then why it is not possible as i am using different id as well ? if > >>> possible then how we could achieve it ? > >>> Any help will be appreciated. Thanks in advance. > >>> > >>> -- > >>> *Thanks & Regards* > >>> Shubham Goswami > >>> Enterprise Software Engineer > >>> *HotWax Systems* > >>> *Enterprise open source experts* > >>> cell: +91-7803886288 > >>> office: 0731-409-3684 > >>> http://www.hotwaxsystems.com > >> > >> > > > > -- > > *Thanks & Regards* > > Shubham Goswami > > Enterprise Software Engineer > > *HotWax Systems* > > *Enterprise open source experts* > > cell: +91-7803886288 > > office: 0731-409-3684 > > http://www.hotwaxsystems.com > > -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Re: Query on changing FieldType
Hi Emir Thanks for the reply, i got your point. But is there any other way to do like one field could have two or more different types defined ? or if i talk about my previous query, can we index some data for the same field with different unique id after replacing the type ? Thanks again Shubham On Tue, Oct 22, 2019 at 1:23 PM Emir Arnautović < emir.arnauto...@sematext.com> wrote: > Hi Shubham, > Changing type is not allowed without full reindexing. If you do something > like that, Solr will end up with segments with different types for the same > field. Remember that segments are immutable and that reindexing some > document will be in new segment, but old segment will still be there and at > query type Solr will have mismatch between what is stated in schema and > what is in segment. In order to change type you have to do full reindexing > - create a new collection and reindex all documents. > > HTH, > Emir > -- > Monitoring - Log Management - Alerting - Anomaly Detection > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > > > > On 22 Oct 2019, at 09:25, Shubham Goswami > wrote: > > > > Hello Community > > > > I have indexed some documents for which solr has taken its type="plongs" > by > > auto guessing but i am trying to change its type="pint" and re-indexing > the > > same data with the same id and indexing the data with different id where > id > > is unique key but it is showing error. > > > > Can somebody please let me know if it is possible or not, if not possible > > then why it is not possible as i am using different id as well ? if > > possible then how we could achieve it ? > > Any help will be appreciated. Thanks in advance. > > > > -- > > *Thanks & Regards* > > Shubham Goswami > > Enterprise Software Engineer > > *HotWax Systems* > > *Enterprise open source experts* > > cell: +91-7803886288 > > office: 0731-409-3684 > > http://www.hotwaxsystems.com > > -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Query on changing FieldType
Hello Community I have indexed some documents for which solr has taken its type="plongs" by auto guessing but i am trying to change its type="pint" and re-indexing the same data with the same id and indexing the data with different id where id is unique key but it is showing error. Can somebody please let me know if it is possible or not, if not possible then why it is not possible as i am using different id as well ? if possible then how we could achieve it ? Any help will be appreciated. Thanks in advance. -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Help to learn synonymQueryStyle and FieldTypeSimilarity
Hi Community I am a beginner in solr and i am trying to understand the working of synonymQueryStyle and FieldTypeSimilarity but i am still not clear how it exactly works. Can somebody please help me to understand this with the help of an example ? Any help will be appreciated. Thanks in advance. -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Re: Query regarding positionIncrementGap
Hi Erick Thanks for reply and your example is very helpful. But i think we can only use this attribute if we are getting data from a single field which has the copy of all data from every field. Please correct me if i am wrong. Thanks for your great support. Shubham On Thu, Oct 17, 2019 at 5:56 PM Erick Erickson wrote: > First, it only counts if you add multiple entries for the field. Consider > the following > >a b c >def > > > where the field has a positionIncrementGap of 100. The term positions of > the entries are > a:1 > b:2 > c:3 > d:103 > e:104 > f:105 > > Now consider the doc where there’s only one field: > >a b c d e f > > > The term positions are > a:1 > b:2 > c:3 > d:4 > e:5 > f:6 > > The use-case is if you, say, index individual sentences and want to match > two or more words in the _same_ sentence. You can specify a phrase query > where the slop is < the positionIncrementGap. So in the first case, if I > search for “a b”~99 I’d get a match. But if I searched for “a d”~99 I > wouldn’t. > > Best, > Erick > > > On Oct 17, 2019, at 2:09 AM, Shubham Goswami > wrote: > > > > Hi Community > > > > I am a beginner in solr and i am trying to understand the working of > > positionIncrementGap but i am still not clear how it exactly works for > the > > phrase queries and general queires. > > Can somebody please help me to understand this with the help fo an > > example ? > > Any help will be appreciated. Thanks in advance. > > > > -- > > *Thanks & Regards* > > Shubham Goswami > > Enterprise Software Engineer > > *HotWax Systems* > > *Enterprise open source experts* > > cell: +91-7803886288 > > office: 0731-409-3684 > > http://www.hotwaxsystems.com > > -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Error in Initializing plugin
Hi Community I am working with currencies and exchange rates and getting this following error. error: Plugin Initializing failure for [schema.xml] fieldType Can somebody please help me out regarding this issue ? schema changes : Thanks in adavance. -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Query regarding positionIncrementGap
Hi Community I am a beginner in solr and i am trying to understand the working of positionIncrementGap but i am still not clear how it exactly works for the phrase queries and general queires. Can somebody please help me to understand this with the help fo an example ? Any help will be appreciated. Thanks in advance. -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Re: Query on autoGeneratePhraseQueries
Hi Michael/Shawn Thanks for the response. Michael you are right, autoGeneratePhraseQueries works for the query like Black-company with the setting of Sow=true. Thanks for your great support. Best Shubham On Wed, Oct 16, 2019 at 9:22 PM Michael Gibney wrote: > Going to back to the initial question, the wording is a little ambiguous > and it occurs to me that it's possible there's a misunderstanding of what > autoGeneratePhraseQueries does. It really only auto-generates phrase > *subqueries*. To use the example from the initial request, a query like > (black company) would always generate a non-phrase query (respecting mm, > q.op, etc. -- but in any case not a top-level phrase query), regardless of > the setting of autoGeneratePhraseQueries. > > autoGeneratePhraseQueries (when set to true) only kicks in (in different > ways depending on analysis chain, and setting of "sow") for a query like > (the black-company manufactures), which would be transformed to something > more like (the "black company" manufactures). The idea is that there's some > extra indication that the two words should be bundled together for purposes > of querying. > > If you want to auto-generate a top-level phrase query, some other approach > would be called for. > > Apologies if this is obvious and/or not helpful, Shubham! > > On Wed, Oct 16, 2019 at 10:10 AM Shawn Heisey wrote: > > > On 10/16/2019 7:14 AM, Shubham Goswami wrote: > > > I have implemented the sow=false property with eDismax Query parser but > > > still it does not has any effect > > > on the query as it is still parsing as separate terms instead of > phrased > > > one. > > > > We have seen reports that when sow=false, which is the default setting > > since Solr 7.0, autoGeneratePhraseQueries does not work. Try setting > > sow=true and see whether you get the results you expect. > > > > I do not know whether this behavior is a bug or if it is expected. > > > > Thanks, > > Shawn > > > -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
Re: Re: Query on autoGeneratePhraseQueries
Hi Rohan/Audrey
I have implemented the sow=false property with eDismax Query parser but
still it does not has any effect
on the query as it is still parsing as separate terms instead of phrased
one.
On Tue, Oct 15, 2019 at 8:25 PM Rohan Kasat wrote:
> Also check ,
> pf , pf2 , pf3
> ps , ps2, ps3 parameters for phrase searches.
>
> Regards,
> Rohan K
>
> On Tue, Oct 15, 2019 at 6:41 AM Audrey Lorberfeld -
> audrey.lorberf...@ibm.com wrote:
>
> > I'm not sure how your config file is setup, but I know that the way we do
> > multi-token synonyms is to have the sow (split on whitespace) parameter
> set
> > to False while using the edismax parser. I'm not sure if this would work
> > with PhraseQueries , but it might be worth a try!
> >
> > In our config file we do something like this:
> >
> >
> >
> > edismax
> > 1.0
> > explicit
> > 100
> > content_en
> > w3json_en
> > false
> >
> >
> >
> > You can read a bit about the parameter here:
> >
> https://opensourceconnections.com/blog/2018/02/20/edismax-and-multiterm-synonyms-oddities/
> >
> > Best,
> > Audrey
> >
> > --
> > Audrey Lorberfeld
> > Data Scientist, w3 Search
> > IBM
> > audrey.lorberf...@ibm.com
> >
> >
> > On 10/15/19, 5:50 AM, "Shubham Goswami"
> > wrote:
> >
> > Hi kshitij
> >
> > Thanks for the reply!
> > I tried to debug it and found that raw query(black company) has
> parsed
> > as
> > two separate queries
> > black and company and returning the results based on black query
> > instead of
> > this it should have
> > got parsed as a single phrase query like("black company") because i
> am
> > using
> > autoGeneratedPhraseQuery.
> > Do you have any idea about this please correct me if i am wrong.
> >
> > Thanks
> > Shubham
> >
> > On Tue, Oct 15, 2019 at 1:58 PM kshitij tyagi <
> > kshitij.shopcl...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Try debugging your solr query and understand how it gets parsed.
> Try
> > using
> > > "debug=true" for the same
> > >
> > > On Tue, Oct 15, 2019 at 12:58 PM Shubham Goswami <
> > > shubham.gosw...@hotwax.co>
> > > wrote:
> > >
> > > > *Hi all,*
> > > >
> > > > I am a beginner to solr framework and I am trying to implement
> > > > *autoGeneratePhraseQueries* property in a fieldtype of
> > > type=text_general, i
> > > > kept the property value as true and restarted the solr server but
> > still
> > > it
> > > > is not taking my two words query like(Black company) as a phrase
> > without
> > > > double quotes and returning the results only for Black.
> > > >
> > > > Can somebody please help me to understand what am i
> > missing ?
> > > > Following is my Schema.xml file code and i am using solr 7.5
> > version.
> > > > > > > positionIncrementGap="100" multiValued="true"
> > > > autoGeneratePhraseQueries="true">
> > > >
> > > > =
> > > >words="stopwords.txt"
> > > > ignoreCase="true"/>
> > > >
> > > >
> > > >
> > > >
> > > >words="stopwords.txt"
> > > > ignoreCase="true"/>
> > > >expand="true"
> > > > ignoreCase="true" synonyms="synonyms.txt"/>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > *Thanks & Regards*
> > > > Shubham Goswami
> > > > Enterprise Software Engineer
> > > > *HotWax Systems*
> > > > *Enterprise open source experts*
> > > > cell: +91-7803886288
> > > > office: 0731-409-3684
> > > >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hotwaxsystems.com=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=Zi9beGF58BzJUNUdCkeW0pwliKwq9vdTSh0V_lR0734=FhSkJBcmYw_bfHgq1enzuYQeOZwKHzlP9h4VwTZSL5E=
> > > >
> > >
> >
> >
> > --
> > *Thanks & Regards*
> > Shubham Goswami
> > Enterprise Software Engineer
> > *HotWax Systems*
> > *Enterprise open source experts*
> > cell: +91-7803886288
> > office: 0731-409-3684
> >
> >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hotwaxsystems.com=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=Zi9beGF58BzJUNUdCkeW0pwliKwq9vdTSh0V_lR0734=FhSkJBcmYw_bfHgq1enzuYQeOZwKHzlP9h4VwTZSL5E=
> >
> >
> > --
>
> *Regards,Rohan Kasat*
>
--
*Thanks & Regards*
Shubham Goswami
Enterprise Software Engineer
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7803886288
office: 0731-409-3684
http://www.hotwaxsystems.com
Re: Query on autoGeneratePhraseQueries
Hi kshitij
Thanks for the reply!
I tried to debug it and found that raw query(black company) has parsed as
two separate queries
black and company and returning the results based on black query instead of
this it should have
got parsed as a single phrase query like("black company") because i am using
autoGeneratedPhraseQuery.
Do you have any idea about this please correct me if i am wrong.
Thanks
Shubham
On Tue, Oct 15, 2019 at 1:58 PM kshitij tyagi
wrote:
> Hi,
>
> Try debugging your solr query and understand how it gets parsed. Try using
> "debug=true" for the same
>
> On Tue, Oct 15, 2019 at 12:58 PM Shubham Goswami <
> shubham.gosw...@hotwax.co>
> wrote:
>
> > *Hi all,*
> >
> > I am a beginner to solr framework and I am trying to implement
> > *autoGeneratePhraseQueries* property in a fieldtype of
> type=text_general, i
> > kept the property value as true and restarted the solr server but still
> it
> > is not taking my two words query like(Black company) as a phrase without
> > double quotes and returning the results only for Black.
> >
> > Can somebody please help me to understand what am i missing ?
> > Following is my Schema.xml file code and i am using solr 7.5 version.
> > > positionIncrementGap="100" multiValued="true"
> > autoGeneratePhraseQueries="true">
> >
> > =
> >> ignoreCase="true"/>
> >
> >
> >
> >
> >> ignoreCase="true"/>
> >> ignoreCase="true" synonyms="synonyms.txt"/>
> >
> >
> >
> >
> >
> > --
> > *Thanks & Regards*
> > Shubham Goswami
> > Enterprise Software Engineer
> > *HotWax Systems*
> > *Enterprise open source experts*
> > cell: +91-7803886288
> > office: 0731-409-3684
> > http://www.hotwaxsystems.com
> >
>
--
*Thanks & Regards*
Shubham Goswami
Enterprise Software Engineer
*HotWax Systems*
*Enterprise open source experts*
cell: +91-7803886288
office: 0731-409-3684
http://www.hotwaxsystems.com
Query on autoGeneratePhraseQueries
*Hi all,* I am a beginner to solr framework and I am trying to implement *autoGeneratePhraseQueries* property in a fieldtype of type=text_general, i kept the property value as true and restarted the solr server but still it is not taking my two words query like(Black company) as a phrase without double quotes and returning the results only for Black. Can somebody please help me to understand what am i missing ? Following is my Schema.xml file code and i am using solr 7.5 version. = -- *Thanks & Regards* Shubham Goswami Enterprise Software Engineer *HotWax Systems* *Enterprise open source experts* cell: +91-7803886288 office: 0731-409-3684 http://www.hotwaxsystems.com
