I agree actually (about not surprising the users). But the consequences of
forgetting this value may also lead to some serious debugging issues.
An interesting (not sure if reasonable) compromise would be to look at an
error message for @version=1 and using @multiValued attribute and make sure
it actually complains if it sees such combination and that the message
explicitly say "What's your @version value? Maybe it needs to be
explicit/more recent". Same with autoGeneratePhraseQueries and @version=1.4.
Then, somebody patching together a config file from multiple sources will
be guided in the right direction.
Just a newbie-oriented thought. I am sure, there are other more-processing
things on a pipeline.
Regards,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
- Time is the quality of nature that keeps events from happening all at
once. Lately, it doesn't seem to be working. (Anonymous - via GTD book)
On Fri, Dec 21, 2012 at 4:49 PM, Chris Hostetter
<hossman_luc...@fucit.org>wrote:
>
> : On another hand, having @version default to 1.0 is probably an oversight,
> : given the number of changes present.... Should it not default to latest
> or
> : at least to 1.5 (and change periodically)?
>
> If the default value changed, then users w/o a version attribute in their
> schema would suddenly get very different behavior if they upgraded from
> one version of solr the the next.
>
>
> -Hoss
>
