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? > >> > > >
