Path Missing In Logged Warning

[ddjksa]

(20-09-2018 15:52)simoncn Wrote:  You need to change this setting to DateTag.yearOnly.index.sort. This will remove the conflict messages you have been getting.

The yearOnly option doesn't affect date truncation warnings. It causes MinimServer to disregard everything beyond the year portion for indexing and/or sorting purposes. The workaround that I suggested for for date truncation warnings was to change Date to DateTag.

If you are enabling yearOnly for index and not for sort, this can produce an index value 2008 with two conflicting sort values:

2008 (from a tag with value 2008)
2008-00-00 (from a tag with value 2008-00-00, indexed as 2008)

By enabling yearOnly for sort as well as index, the sort value in the second case becomes 2008 and there is no conflict.

This conflict is detected only when you browse to a container that contains an entry with an index value of 2008. This is why you don't see it as part of the initial scan.

Thanks Simon. I'll try that and feedback. Were you able to figure out why the messages are repeated 3 times?