Re: [hibernate-dev] [Hibernate Search] DocValues and Sorting API -> new mapping annotations ?

>> One possible workaround is to enforce the indexNullAs value to match the >> underlying field type, at the >> moment it is always a string. > > Interesting idea, but the user would need to provide which "value" > he's ok to give up, as he would need to pick a number to be treated as > NaN. > Since the indexNullAs parameter requires a string, would we expect > people to write a number in there? +1 for that idea.

Isn't that what's happening already atm.? If a value is null (and indexNullAs() is *not* given), it will not be part of the index as per my observations. But if it is null and indexNullAs() is given, that token will be used. That seems like the right thing to do IMO. Esp. I would not ignore indexNullAs() if given, apparently the user meant to encode null in that case e.g. to use it in queries.