You'll have to give us more details on what exactly you are doing to
reproduce the problem you are seeing, and more detals on how exactly
you upgraded (and what version you upgraded from) ...
https://wiki.apache.org/solr/UsingMailingLists
When i launch 6.3.0 using "bin/solr -e techproducts
Hello all,
We've been indexing documents with empty strings for some fields.
After our latest round of Solr/SolrJ updates to 6.3.0 we have discovered
that fields with empty strings are no longer being stored, effectively
storing documents with those fields as being NULL/NOT-PRESENT instead of
Correct. In fact, faceting pulls its values normally from the indexed
terms anyway. It completely ignores stored.
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On 13 August 2015 at 19:49, Nagasharath wrote:
> If I just want faceting(no search) c
If I just want faceting(no search) can I set stored='false' and
docValues='true' with indexed='true'
> On 13-Aug-2015, at 5:21 pm, Erick Erickson wrote:
>
> DocValues, stored and indexed are all independent.
> So no, docValues is not an alternative to stored.
>
> Best,
> Erick
>
> On Thu, Au
DocValues, stored and indexed are all independent.
So no, docValues is not an alternative to stored.
Best,
Erick
On Thu, Aug 13, 2015 at 2:51 PM, naga sharathrayapati
wrote:
> Do we need to specify stored='true' even when we specify docValues='true'
> in the schema
>
> is docValues not the alter
Do we need to specify stored='true' even when we specify docValues='true'
in the schema
is docValues not the alternate of stored?
On Thu, Aug 13, 2015 at 2:48 PM, Shawn Heisey wrote:
> On 8/13/2015 9:07 AM, Erick Erickson wrote:
> > No. But how do they default to "true"? In the fieldType? Which
On 8/13/2015 9:07 AM, Erick Erickson wrote:
> No. But how do they default to "true"? In the fieldType? Which will be
> potentially different for different fieldTypes, so as a matter of style I
> prefer
> to list them in the field definition. But that's not necessary.
I previously looked at the co
My two cents,
If anything else, declaring them as indexed="true" and stored="true" helps
to auto document the schema and make its options explicit.
Best,
Eddie
On Thu, Aug 13, 2015 at 12:07 PM, Erick Erickson
wrote:
> No. But how do they default to "true"? In the fieldType? Which will be
> po
what if i do something like this in the schema
will the filed name be stored? or not stored? as i have not specified in
the schema as stored='true'/'false'.
On Thu, Aug 13, 2015 at 10:07 AM, Erick Erickson
wrote:
> No. But how do they default to "true"? In the fieldType? Which will be
> poten
No. But how do they default to "true"? In the fieldType? Which will be
potentially different for different fieldTypes, so as a matter of style I prefer
to list them in the field definition. But that's not necessary.
Best,
Erick
On Wed, Aug 12, 2015 at 4:42 PM, Nagasharath wrote:
> As stored & in
As stored & indexed both default to "true" do we still need to specify in the
schema as
Indexed="true" & stored="true"
11 matches
Mail list logo
