Re: admin query showing unstored fields

2012-11-18 Thread Reik Schatz
nsky > > -Original Message- From: Reik Schatz > Sent: Friday, November 16, 2012 8:35 AM > > To: solr-user@lucene.apache.org > Subject: Re: admin query showing unstored fields > > Hi Jack, > > I just did some testing again and can confirm it works! I am new to So

Re: admin query showing unstored fields

2012-11-16 Thread Jack Krupansky
ng that cause the unexpected behavior. -- Jack Krupansky -Original Message- From: Reik Schatz Sent: Friday, November 16, 2012 3:02 AM To: solr-user@lucene.apache.org Subject: Re: admin query showing unstored fields I did this test. Here is my schema.xml (setting sto

Re: admin query showing unstored fields

2012-11-16 Thread Reik Schatz
st be some other steps you are performing that cause the unexpected > behavior. > > > -- Jack Krupansky > > -Original Message- From: Reik Schatz > Sent: Friday, November 16, 2012 3:02 AM > To: solr-user@lucene.apache.org > Subject: Re: admin query showing uns

Re: admin query showing unstored fields

2012-11-16 Thread Jack Krupansky
16, 2012 8:09 AM To: solr-user@lucene.apache.org Subject: Re: admin query showing unstored fields I just noticed that you are using an old schema version, 1.1. Any reason for that? This suggests that you had an existing, old, Solr that you migrated to 4.0. What Solr release was it? Was the stored

Re: admin query showing unstored fields

2012-11-16 Thread Jack Krupansky
ion 1.1 has some odd, undocumented quirks, there must be some other steps you are performing that cause the unexpected behavior. -- Jack Krupansky -Original Message- From: Reik Schatz Sent: Friday, November 16, 2012 3:02 AM To: solr-user@lucene.apache.org Subject: Re: admin query sho

Re: admin query showing unstored fields

2012-11-16 Thread Reik Schatz
t; >> schema to have stored="false"? Changing the schema doesn't affect the > >> existing index/stored values. > >> > >> Also, what release are you using? > >> > >> -- Jack Krupansky > >> > >> -Original Message--

Re: admin query showing unstored fields

2012-11-16 Thread Erik Hatcher
what release are you using? >> >> -- Jack Krupansky >> >> -Original Message- From: Reik Schatz >> Sent: Friday, November 16, 2012 3:02 AM >> To: solr-user@lucene.apache.org >> Subject: Re: admin query showing unstored fi

Re: admin query showing unstored fields

2012-11-16 Thread Reik Schatz
AM > To: solr-user@lucene.apache.org > Subject: Re: admin query showing unstored fields > > I did this test. Here is my schema.xml (setting stored="false" explicitly > though it should be default): > > > > > precisionStep="32" omitN

Re: admin query showing unstored fields

2012-11-16 Thread Jack Krupansky
z Sent: Friday, November 16, 2012 3:02 AM To: solr-user@lucene.apache.org Subject: Re: admin query showing unstored fields I did this test. Here is my schema.xml (setting stored="false" explicitly though it should be default):

Re: admin query showing unstored fields

2012-11-16 Thread Reik Schatz
I did this test. Here is my schema.xml (setting stored="false" explicitly though it should be default): id players I indexed a single document via the sol4j api: // todo: make addings

Re: admin query showing unstored fields

2012-11-16 Thread Upayavira
Er, it can't. What are you seeing that seems wrong? Upayavira On Fri, Nov 16, 2012, at 10:13 AM, Reik Schatz wrote: > This might be a silly question but if I search *.* in the admin tool, how > can it show me the full document including all the fields that are set to > stored="false" or that don'