Sorry. Let me add more info. (I assumed that anyone who tried it would see the problem right away but that might not be the case.)
> You haven't shown the SOLR field type definitions. Values of all non-String types in my index are not being shown. In my case, this includes long, tint and date types. > You haven't provided, say, the output from SOLR if you add &debugQuery=on. Solr side of things seem to work fine. Is this still needed? > You haven't shown the terms from either SOLR admin or Luke that they > actually see in the index. I'm not sure if I understand this question. Basically, if I do a query "id:694" in /solr/admin, I get the result. But the same query doesn't return anything in Luke. > You haven't identified the version of SOLR that the index was created with Solr 1.4 > You haven't identified the version of Luke you're using. Luke 1.0.1 (2010-04-01) > Both SOLR and Luke use Lucene under the covers, so the problem is almost > certainly your expectations... This may well be the case. Not knowing the details, I was still surprised since I expected the same search behavior for simple queries between solr and luke. > Imagine a co-worker from another department has provided you the information > you've provided us. What could you say? I might give it a try and see the same thing :-D Thanks > On Sun, May 30, 2010 at 2:19 PM, jlist9 <jli...@gmail.com> wrote: > >> Oh, here's a modified/improved version of what I described in my first >> email: >> >> 1. Queries like "id:123" which work fine in /solr/admin web interface but >> returns nothing in Luke. Query "*:*" returns all records fine in Luke. I >> expect Luke returns the same result as /solr/admin since it's essentially >> a Lucene query? >> >> 2. When Luke displays records with query "*:*", it shows the string >> values fine but the numeric fields and date fields show blank. It shows >> DocID OK, though. I expect Luke to be able to show non-string values, too. >> >> On Sun, May 30, 2010 at 10:57 AM, Erick Erickson >> <erickerick...@gmail.com> wrote: >> > Then you have to provide a lot more detail about what you did >> > and what you're seeing and what you think you should see. You >> > might review this page: >> > http://wiki.apache.org/solr/UsingMailingLists >> > >> > Best >> > Erick >> > >> > On Sun, May 30, 2010 at 1:41 PM, jlist9 <jli...@gmail.com> wrote: >> > >> >> I find in the Plugins tab that the default is PersianAnalyzer. I >> switched >> >> to StandardAnalyzer and tried a few different Lucene Compatibility >> values >> >> but it didn't help :-( >> >> >> >> On Sun, May 30, 2010 at 4:40 AM, Erick Erickson < >> erickerick...@gmail.com> >> >> wrote: >> >> > The Solr admin page as access to (and uses) the field >> >> > definitions you've put in the config file. Luke has no >> >> > knowledge of this configuration, you have to choose >> >> > your analyzer from the drop down and select the one >> >> > closest to what's in your config file for SOLR. Are you >> >> > perhaps using an analyzer in Luke that doesn't >> >> > play nice with the definitions in SOLR? >> >> > >> >> > HTH >> >> > Erick >> >> > >> >> > >> >> > On Sat, May 29, 2010 at 10:55 PM, jlist9 <jli...@gmail.com> wrote: >> >> > >> >> >> I tried the stand-alone Luke tool (not Luke request handler) to >> browse >> >> >> a solr index and find a few strange things: >> >> >> >> >> >> 1. Queries like "id:123" which work fine in /solr/admin web interface >> >> >> returns nothing in Luke. "*:*" returns everything fine in Luke. >> >> >> >> >> >> 2. When Luke displays records with query "*:*", it shows the string >> >> >> values fine but the numeric fields and date fields shows blank. It >> shows >> >> >> DocID OK, though. >> >> >> >> >> >> Anyone else has tried Luke on a solr index? >> >> >> >> >> > >> >> >> > >> >
