Re: Search opening hours
I can't answer it, but I wonder if searches related to the international date line might help - that's where the equivalent issue is in spatial terms. Upayavira On Sun, Sep 6, 2015, at 06:32 PM, O. Klein wrote: > OK. I got most of it working. > > I created a worldBounds="0 -1 762 1" > > 15 minute intervals for a week. > > And use "linestring(1 0, 2 0)" to index data for Monday 00:15 to 00:30 > > How do I get to index Sunday 24:00 to Monday 01:00 ? > > I have a feeling the linestring just goes back and doesn't wrap around > the > plane. > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Search-opening-hours-tp4225250p4227374.html > Sent from the Solr - User mailing list archive at Nabble.com.
Re: Search opening hours
Saw that, but not a lot of info about it. >From my understanding, the way it supposed to work is that a value bigger then boundary get's normalized. I just get an exception "bad x not in boundary rect" Any pointers? -- View this message in context: http://lucene.472066.n3.nabble.com/Search-opening-hours-tp4225250p4227384.html Sent from the Solr - User mailing list archive at Nabble.com.
Problems upgrading to Solr 5.3.0
Hi, I'm trying to upgrade from Solr 5.2.1 to 5.3.0. My Solr is running on SolrCloud and also on external zookeeper 3.4.6. When I tried to migrate the index over from Solr 5.2.1 to Solr 5.3.0, the Solr is not able to startup, and it just give the error saying Solr did not come online within 30 seconds! I've put the indexed under solrMain\node1\solr and solrMain\node2\solr as I'm running my Solr with 2 notes, and I used the following command to start. bin\solr.cmd start -cloud -p 8983 -s solrMain\node1\solr -m 12g -z "localhost:2181,localhost:2182,localhost:2183" I've also tried not to migrate the index, but to start Solr 5.3.0 without any cores and indexes, and tried to create a new core from there from my Solr 5.2.1 configurations. However, when I tried to create, I got the following error: org.apache.solr.common.SolrException: Could not load conf for core collection1_shard1_replica2: Plugin init failure for [schema.xml] fieldType "text_ar": Plugin init failure for [schema.xml] analyzer/tokenizer: Error loading class 'solr.ICUTokenizerFactory'. Schema file is /configs/collection1/schema.xml at org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:80) at org.apache.solr.core.CoreContainer.create(CoreContainer.java:725) at org.apache.solr.core.CoreContainer.create(CoreContainer.java:701) at org.apache.solr.handler.admin.CoreAdminHandler.handleCreateAction(CoreAdminHandler.java:629) at org.apache.solr.handler.admin.CoreAdminHandler.handleRequestInternal(CoreAdminHandler.java:214) at org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(CoreAdminHandler.java:194) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:143) at org.apache.solr.servlet.HttpSolrCall.handleAdminRequest(HttpSolrCall.java:675) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:443) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:210) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:179) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.solr.common.SolrException: Plugin init failure for [schema.xml] fieldType "text_ar": Plugin init failure for [schema.xml] analyzer/tokenizer: Error loading class 'solr.ICUTokenizerFactory'. Schema file is /configs/collection1/schema.xml at org.apache.solr.schema.IndexSchema.readSchema(IndexSchema.java:596) at org.apache.solr.schema.IndexSchema.(IndexSchema.java:175) at org.apache.solr.schema.IndexSchemaFactory.create(IndexSchemaFactory.java:55) at org.apache.solr.schema.IndexSchemaFactory.buildIndexSchema(IndexSchemaFactory.java:69) at org.apache.solr.core.ConfigSetService.createIndexSchema(ConfigSetService.java:104) at org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:75) ... 30 more Caused by: org.apache.solr.common.SolrException: Plugin init failure for [schema.xml] fieldType "text_ar": Plugin init failure for [schema.xml] analyzer/tokenizer: Error loading class 'solr.ICUTokenizerFactory' at org.apache.solr.util.plugin.AbstractPluginLoader.load(AbstractPluginLoader.java:178)
Re: Strange interpretation of invalid ISO date strings
Just a word of warning: iso-8601, the date format standard, is quite big, to say the least, and I thus expect very few implementations to be complete. I survived one such interoperability issue with Safari on iOS6. While they (and JS I think) claim iso-8601, it was not complete and fine grained hunting lead us to the discovery of that. Opening an issue at Apple was done but changing on our side was much faster. Overall, this has cost us several months of development... I wish there would be a tinyer standard. Paul -- fat fingered on my z10 -- Message d'origine De: Shawn Heisey Envoyé: Montag, 7. September 2015 02:05 À: solr-user@lucene.apache.org Répondre à: solr-user@lucene.apache.org Objet: Strange interpretation of invalid ISO date strings Here's some debug info from a query our code was generating: "querystring": "post_date:[2015-09-0124T00:00:00Z TO 2015-09-0224T00:00:00Z]", "parsedquery": "post_date:[145169280 TO 146033280]", The "24" is from part of our code that interprets the hour, it was being incorrectly added. We have since fixed the problem, but are somewhat confused that we did not get an error. When I decode the millisecond timestamps in the parsed query, I get these dates: Sat, 02 Jan 2016 00:00:00 GMT Mon, 11 Apr 2016 00:00:00 GMT Should this be considered a bug? I would have expected Solr to throw an exception related to an invalidly formatted date, not assume that we meant the 124th and 224th day of the month and calculate it accordingly. Would I be right in thinking that this problem is not actually in Solr code, that we are using code from either Java itself or a third party for ISO date parsing? The index where this problem was noticed is Solr 4.9.1 running with Oracle JDK8u45 on Linux. I confirmed that the same thing happens if I use Solr 5.2.1 running with Oracle JDK 8u60 on Windows. Thanks, Shawn
Re: ghostly config issues
On 9/6/2015 11:27 AM, Mark Fenbers wrote: > This issue still persists. :-(( > > I have moved all the jars to /lib. I have commented out > all references in solrconfig.xml. I have moved all jars to > /lib and removed them from /lib. But nothing has > changed with any of these steps. > > I only heard of Solr/Lucene about a week ago, and so I downloaded the > package since then. If I have multiple versions of things, then it > would have had to come packaged that way because I only > downloaded/installed it once. > > In my solrconfig.xml, I reference a file for my particular database > details in a tag. In it, I deliberately misspelled the > class name because I wanted to see if I got a different error. I did, > so I know that my issue isn't because it can't find the class. (I since > changed it back.) The contents of my db-data-config.xml file are > attached (below). Do you see anything obviously incorrect about my > config? Could this be where the source of the DataImportHandler error > originates? If we assume that it cannot be a problem with multiple jar versions, which sounds pretty reasonable, then I think SOLR-6188 is probably to blame. https://issues.apache.org/jira/browse/SOLR-6188 I think you should try this as a troubleshooting step: Rename that lib directory where you have the jars to something like libtest and add/change the sharedLib setting in your solr.xml to libtest. The following line should do it: libtest See this wiki page for more information about solr.xml: https://wiki.apache.org/solr/Solr.xml%204.4%20and%20beyond If this troubleshooting step fixes the problem, then I think it's definitely SOLR-6188, and you have a viable workaround that should continue to work even after SOLR-6188 is fixed. Thanks, Shawn
Re: Search opening hours
I think the client code has to normalize the input. There are methods in the spatial libraries that will do this - or maybe I wrote them my code, can't remember. How are you handling parsing the hours? - Darren > On Sep 6, 2015, at 4:56 PM, O. Kleinwrote: > > Saw that, but not a lot of info about it. > > From my understanding, the way it supposed to work is that a value bigger > then boundary get's normalized. > > I just get an exception "bad x not in boundary rect" > > Any pointers? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Search-opening-hours-tp4225250p4227384.html > Sent from the Solr - User mailing list archive at Nabble.com.
Re: frequently update field
tnx for comparison of external file and atomic update On Sat, Sep 5, 2015 at 6:53 AM, Jack Krupanskywrote: > The standard recommendation is to create a proof of concept implementation > and see how well it performs. > > The external file approach is intended for bulk update, such as when the > pricing for many products will be updated all at once. > > Atomic update is recommended for incremental updates. > > Atomic update does depend of setting all source fields to stored since the > entire document must be first read from the stored values before updating > the selected fields. > > If storing all source fields is prohibitive, then they must be stored in an > external database so that the full documents can be reindexed when updating > is required. > > As with any database question, the first thing you must do is identify your > access patterns - how much data will you be updating and with what > frequency. > > Generally, atomic update is recommended when only a small fraction of the > data will be updated in some relatively small interval of time, such as > hundreds of documents per hour or dozens of documents per minute, or a > handful per second. > > > -- Jack Krupansky > > On Sat, Sep 5, 2015 at 1:16 AM, sara hajili wrote: > > > hi > > i am new in solr, i face to a problem and need any solution to solve > that. > > i have a field that this field need to update frequently. > > "image i need to index all post of member of a social app" > > in this case i need to store and index all posts field like caption , > > image, title,comments ,etc > > but question is about some field like > > "like_count,repost_count,comment_count" this field frequenly changed and > i > > need to update that but other like caption ,title are not as the same of > > like count field. > > so what is the best solution to handle this frequntly update.. > > i found that in solr 4 people used external file. > > but now in solr 5.x i see that atomic update appear. > > atomic update is substitute of extenal file?and what is best approach in > > this case? > > "i really worry about cost of re indexing docs when update like count" > > >
solr now relational between tags?!!
hi i have a social app and i wanna to index all people posts. in this case i index post data like : title,images,tags,caption,comment,like counts,etc and i need to search on tag"people tags on their post ,this tags are related to their post" i am willing to undrestand that solr know any relational bettwen tags?!! "i know we can set filter to set synonym of a search clause ,and for example if people search football ,(if in synonym file i set "football"="soccer") solr search on football and soccer. i need to know solr can underestand other relational between tags?? i mean solr now about companion relation betwwen tags?!! see this: if i have tags in solr "football,sport,cr7" and in many tags in solr doc football and sport come to gether. if user search sport, solr underestand that search about sport and football together("because football and sport come together more and more in docs,so solr must conclude that sport and football have comparison relational,so search on both of them ")?? so solr know that?if no how implement this? or if yes.how i use this feature? tnx.
Re: ghostly config issues
On 9/5/2015 10:40 PM, Shawn Heisey wrote: Your solr home is /localapps/dev/EventLog ... Solr automatically loads any jar found in the lib directory in the solr home, so it is attempting to use /localapps/dev/EventLog/lib for the classloader. For the other things you noticed, I believe I know why that is happening too. This SHOULD be the structure of a core instanceDir, if "collection1" is the name of that directory. This is highly simplified and missing things you would likely find in the directory structure: collection1/ |-core.properties |-conf/ |--solrconfig.xml |--schema.xml |--stopwords.txt |-data/ |--index/ |---[Lucene index files go here] The directory with the core.properties file is the instanceDir. The instanceDir is supposed to contain a conf directory and a data directory. It appears that you have this of structure in your solr home (leaving a lot of things out on this one): solr/ |-conf/ |--core.properties |--solrconfig.xml |--schema.xml This is why it is looking in a path that has "conf" twice -- it is going to the instanceDir (where it found core.properties) and assuming that it will find a conf directory there. The conf directory is not supposed to be the instanceDir. Thanks, Shawn Yes, indeed. Moving core.properties up to the parent directory did the trick. I also created a lib subdir and copied the postgres jar file and the Solr import handlers into it -- according to the advice from Kevin Lee responding to my "Config error mystery" post. This brought me back to my original problem, which is shown in the log data below (java stack trace). Perhaps is it an issue with multiple versions of the same jar as you suggested in your response to "Config error mystery", but the log (below) does not seem to indicate that it has found a duplicate jar. Though Solr is running, I am not able to create an index from my database data. What do you make of the information in the log file? Mark 2015-09-06 11:02:30.674 INFO (main) [ ] o.e.j.u.log Logging initialized @853ms 2015-09-06 11:02:31.075 INFO (main) [ ] o.e.j.s.Server jetty-9.2.11.v20150529 2015-09-06 11:02:31.110 WARN (main) [ ] o.e.j.s.h.RequestLogHandler !RequestLog 2015-09-06 11:02:31.115 INFO (main) [ ] o.e.j.d.p.ScanningAppProvider Deployment monitor [file:/localapps/dev/solr-5.3.0/server/contexts/] at interval 0 2015-09-06 11:02:32.261 INFO (main) [ ] o.e.j.w.StandardDescriptorProcessor NO JSP Support for /solr, did not find org.apache.jasper.servlet.JspServlet 2015-09-06 11:02:32.290 WARN (main) [ ] o.e.j.s.SecurityHandler ServletContext@o.e.j.w.WebAppContext@27cd61b{/solr,file:/localapps/dev/solr-5.3.0/server/solr-webapp/webapp/,STARTING}{/localapps/dev/solr-5.3.0/server/solr-webapp/webapp} has uncovered http methods for path: / 2015-09-06 11:02:32.308 INFO (main) [ ] o.a.s.s.SolrDispatchFilter SolrDispatchFilter.init(): WebAppClassLoader=365733477@15cca665 2015-09-06 11:02:32.343 INFO (main) [ ] o.a.s.c.SolrResourceLoader JNDI not configured for solr (NoInitialContextEx) 2015-09-06 11:02:32.344 INFO (main) [ ] o.a.s.c.SolrResourceLoader using system property solr.solr.home: /localapps/dev/EventLog/ 2015-09-06 11:02:32.349 INFO (main) [ ] o.a.s.c.SolrResourceLoader new SolrResourceLoader for directory: '/localapps/dev/EventLog/' 2015-09-06 11:02:32.355 INFO (main) [ ] o.a.s.c.SolrResourceLoader Adding 'file:/localapps/dev/EventLog/lib/pg.jar' to classloader 2015-09-06 11:02:32.355 INFO (main) [ ] o.a.s.c.SolrResourceLoader Adding 'file:/localapps/dev/EventLog/lib/solr-dataimporthandler-5.3.0.jar' to classloader 2015-09-06 11:02:32.356 INFO (main) [ ] o.a.s.c.SolrResourceLoader Adding 'file:/localapps/dev/EventLog/lib/solr-dataimporthandler-extras-5.3.0.jar' to classloader 2015-09-06 11:02:32.700 INFO (main) [ ] o.a.s.c.SolrXmlConfig Loading container configuration from /localapps/dev/EventLog/solr.xml 2015-09-06 11:02:32.871 INFO (main) [ ] o.a.s.c.CoresLocator Config-defined core root directory: /localapps/dev/EventLog 2015-09-06 11:02:32.928 INFO (main) [ ] o.a.s.c.CoreContainer New CoreContainer 574322827 2015-09-06 11:02:32.928 INFO (main) [ ] o.a.s.c.CoreContainer Loading cores into CoreContainer [instanceDir=/localapps/dev/EventLog/] 2015-09-06 11:02:32.929 INFO (main) [ ] o.a.s.c.CoreContainer loading shared library: /localapps/dev/EventLog/lib 2015-09-06 11:02:32.931 INFO (main) [ ] o.a.s.c.SolrResourceLoader Adding 'file:/localapps/dev/EventLog/lib/pg.jar' to classloader 2015-09-06 11:02:32.931 INFO (main) [ ] o.a.s.c.SolrResourceLoader Adding 'file:/localapps/dev/EventLog/lib/solr-dataimporthandler-5.3.0.jar' to classloader 2015-09-06 11:02:32.931 INFO (main) [ ] o.a.s.c.SolrResourceLoader Adding 'file:/localapps/dev/EventLog/lib/solr-dataimporthandler-extras-5.3.0.jar' to classloader 2015-09-06 11:02:32.983 INFO (main) [ ] o.a.s.h.c.HttpShardHandlerFactory created with socketTimeout :
Strange interpretation of invalid ISO date strings
Here's some debug info from a query our code was generating: "querystring": "post_date:[2015-09-0124T00:00:00Z TO 2015-09-0224T00:00:00Z]", "parsedquery": "post_date:[145169280 TO 146033280]", The "24" is from part of our code that interprets the hour, it was being incorrectly added. We have since fixed the problem, but are somewhat confused that we did not get an error. When I decode the millisecond timestamps in the parsed query, I get these dates: Sat, 02 Jan 2016 00:00:00 GMT Mon, 11 Apr 2016 00:00:00 GMT Should this be considered a bug? I would have expected Solr to throw an exception related to an invalidly formatted date, not assume that we meant the 124th and 224th day of the month and calculate it accordingly. Would I be right in thinking that this problem is not actually in Solr code, that we are using code from either Java itself or a third party for ISO date parsing? The index where this problem was noticed is Solr 4.9.1 running with Oracle JDK8u45 on Linux. I confirmed that the same thing happens if I use Solr 5.2.1 running with Oracle JDK 8u60 on Windows. Thanks, Shawn
Re: ghostly config issues
On 9/6/2015 12:00 PM, Shawn Heisey wrote: It looks like you have jars in the solrhome/lib directory, which is good. You probably don't need the dataimporthandler jar for -extras if you just want to load from a database. It does appear that you also have directives in your solrconfig.xml, which are loading after the dataimport jars load. Loading jars from multiple locations complicates the classloader, and has been known to cause a huge number of problems. I don't know if it is why you are having a class cast exception, but it would be my first guess. Since you are using the solrhome/lib directory, you should put ALL jars that you need there, remove all jars from any instanceDir/lib directory, and also remove all configuration elements from your solrconfig.xml. It looks like the jars that are loading are for Solr 5.3.0. Do you have any jars from another Solr or Lucene version in a directory that might somehow be on the classpath -- loaded into the system java directories via operating system packages or something? There *might* be a problem with jars loading twice. That appears to be causing other problems, described in this issue: https://issues.apache.org/jira/browse/SOLR-6188 If loading the dataimport jar twice IS causing this problem, then you could probably fix it by removing the jars from the solrhome/lib directory and loading them with elements in solrconfig.xml instead -- this is the opposite of the advice I gave you earlier in this message. I do not like to load jars that way, because each core ends up loading the jars into its own classloader, so for me they would get loaded multiple times ... but it might be a viable workaround, especially if you are not going to have a large number of cores. Thanks, Shawn This issue still persists. :-(( I have moved all the jars to /lib. I have commented out all references in solrconfig.xml. I have moved all jars to /lib and removed them from /lib. But nothing has changed with any of these steps. I only heard of Solr/Lucene about a week ago, and so I downloaded the package since then. If I have multiple versions of things, then it would have had to come packaged that way because I only downloaded/installed it once. In my solrconfig.xml, I reference a file for my particular database details in a tag. In it, I deliberately misspelled the class name because I wanted to see if I got a different error. I did, so I know that my issue isn't because it can't find the class. (I since changed it back.) The contents of my db-data-config.xml file are attached (below). Do you see anything obviously incorrect about my config? Could this be where the source of the DataImportHandler error originates? Thanks! Mark url="jdbc:postgresql://dx1f/OHRFC" user="awips" /> deltaQuery="SELECT posttime FROM eventlogtext WHERE lastmodtime > '${dataimporter.last_index_time}'">
Re: Search opening hours
OK. I got most of it working. I created a worldBounds="0 -1 762 1" 15 minute intervals for a week. And use "linestring(1 0, 2 0)" to index data for Monday 00:15 to 00:30 How do I get to index Sunday 24:00 to Monday 01:00 ? I have a feeling the linestring just goes back and doesn't wrap around the plane. -- View this message in context: http://lucene.472066.n3.nabble.com/Search-opening-hours-tp4225250p4227374.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: ghostly config issues
On 9/6/2015 5:28 AM, Mark Fenbers wrote: > Yes, indeed. Moving core.properties up to the parent directory did the > trick. I also created a lib subdir and copied the postgres jar file and > the Solr import handlers into it -- according to the advice from Kevin > Lee responding to my "Config error mystery" post. This brought me back > to my original problem, which is shown in the log data below (java stack > trace). Perhaps is it an issue with multiple versions of the same jar > as you suggested in your response to "Config error mystery", but the log > (below) does not seem to indicate that it has found a duplicate jar. > Though Solr is running, I am not able to create an index from my > database data. > > What do you make of the information in the log file? It looks like you have jars in the solrhome/lib directory, which is good. You probably don't need the dataimporthandler jar for -extras if you just want to load from a database. It does appear that you also have directives in your solrconfig.xml, which are loading after the dataimport jars load. Loading jars from multiple locations complicates the classloader, and has been known to cause a huge number of problems. I don't know if it is why you are having a class cast exception, but it would be my first guess. Since you are using the solrhome/lib directory, you should put ALL jars that you need there, remove all jars from any instanceDir/lib directory, and also remove all configuration elements from your solrconfig.xml. It looks like the jars that are loading are for Solr 5.3.0. Do you have any jars from another Solr or Lucene version in a directory that might somehow be on the classpath -- loaded into the system java directories via operating system packages or something? There *might* be a problem with jars loading twice. That appears to be causing other problems, described in this issue: https://issues.apache.org/jira/browse/SOLR-6188 If loading the dataimport jar twice IS causing this problem, then you could probably fix it by removing the jars from the solrhome/lib directory and loading them with elements in solrconfig.xml instead -- this is the opposite of the advice I gave you earlier in this message. I do not like to load jars that way, because each core ends up loading the jars into its own classloader, so for me they would get loaded multiple times ... but it might be a viable workaround, especially if you are not going to have a large number of cores. Thanks, Shawn
Re: solr now relational between tags?!!
The closest thing to this I know of would be "more like this", you might want to take a look at that capability: https://cwiki.apache.org/confluence/display/solr/MoreLikeThis Best, Erick On Sat, Sep 5, 2015 at 11:29 PM, sara hajiliwrote: > hi > i have a social app and i wanna to index all people posts. > in this case i index post data like : > title,images,tags,caption,comment,like counts,etc > and i need to search on tag"people tags on their post ,this tags are > related to their post" > i am willing to undrestand that solr know any relational bettwen tags?!! > "i know we can set filter to set synonym of a search clause ,and for > example if people search football ,(if in synonym file i set > "football"="soccer") solr search on football and soccer. > i need to know solr can underestand other relational between tags?? > i mean solr now about companion relation betwwen tags?!! > see this: > if i have tags in solr "football,sport,cr7" > and in many tags in solr doc football and sport come to gether. > if user search sport, > solr underestand that search about sport and football together("because > football and sport come together more and more in docs,so solr must > conclude that sport and football have comparison relational,so search on > both of them ")?? > so solr know that?if no how implement this? > or if yes.how i use this feature? > tnx.