Hi Chris,
Thanks for your detailed explanations. The default value is a difficult
limitation. Especially for financial figures. I may try with some
workaround like the lowest possible number for TrieLongField, but would be
better to avoid such :)
Regards.
On 22 March 2013 20:39, Chris Hostetter
: Thank you for your response. Yes, that's strange. By enabling DocValues the
: information about missing fields is lost, which changes the way of sorting
: as well. Adding default value to the fields can change a logic of
: application dramatically (I can't set default value to 0 for all
: Trie*F
Hi Shawn,
Thank you for your response. Yes, that's strange. By enabling DocValues the
information about missing fields is lost, which changes the way of sorting
as well. Adding default value to the fields can change a logic of
application dramatically (I can't set default value to 0 for all
Trie*F
On 3/21/2013 3:07 PM, Shawn Heisey wrote:
This might be a requirement of the lower-level Lucene API, or it might
be a requirement that was instituted at the Solr level because a problem
was found when docs did not contain the field. Google seems reluctant
to tell me, and I haven't figured out th
On 3/21/2013 5:46 AM, Marcin Rzewucki wrote:
Hi,
Can somebody explain why there are additional requirements for a field to
be able to use DocValues ? For example: Trie*Fields have to be required or
have default value.
"Schema Parsing Failed: Field
tlong{class=org.apache.solr.schema.TrieLongFiel
Hi,
Can somebody explain why there are additional requirements for a field to
be able to use DocValues ? For example: Trie*Fields have to be required or
have default value.
"Schema Parsing Failed: Field
tlong{class=org.apache.solr.schema.TrieLongField,analyzer=org.apache.solr.analysis.TokenizerCh
