: q=*:*&fq=+i_yearStartSort:{* TO 1995}&fq=+i_yearStopSort:{* TO *} ... : Unfortunately, under 3.6.1 with class="solr.TrieField" type="integer", this : query is returning docs that have neither an i_yearStopSort nor a : i_yearStartSort value.
Hmmmm... I can't seem to reproduce this. Here's what i tried... 1) start up the Solr 3.6.1 example 2) index the 3.6.1 example docs... java -jar post.jar *.xml 3) index a single doc using some "*_ti" dynamic fields (which us "tint")... java -Ddata=args -jar post.jar '<add><doc><field name="id">HOSS</field><field name="start_ti">45</field><field name="end_ti">100</field></doc></add>' If i do some open ended range queries on the *_ti fields, i get the results i expect (either only my HOSS doc if it's in the ranges, or no docs if HOSS is out of range)... Matches HOSS... http://localhost:8983/solr/select?q=*:*&fq=start_ti:{*%20TO%2050}&fl=start_ti,id,end_ti http://localhost:8983/solr/select?q=*:*&fq=start_ti:{*%20TO%2050}&fq=end_ti:{*%20TO%20*}fl=start_ti,id,end_ti Matches nothing... http://localhost:8983/solr/select?q=*:*&fq=start_ti:{*%20TO%205}&fl=start_ti,id,end_ti http://localhost:8983/solr/select?q=*:*&fq=start_ti:{*%20TO%205}&fq=end_ti:{*%20TO%20*}fl=start_ti,id,end_ti I repeated the test after deleting all data, and adding sortMissingLast="true" to the example "tint" fieldType, and got the same results. : Solr 3.6.1 Relevant Schema Parts - Not working as expected: : ----------------------------------------------------------------------------------------- : <fieldType name="tint" class="solr.TrieField" type="integer" : precisionStep="4" sortMissingLast="true" positionIncrementGap="0" : omitNorms="true"/> FYI: you have some wackiness there: 'type="integer"' inside the '<fieldType name="tint" .../>' ... that shouldn't have caused any problems though, but it doesn't make any sense. : <field name="i_yearStartSort" type="tint" indexed="true" stored="false" : required="false" multiValued="false"/> : <field name="i_yearStopSort" type="tint" indexed="true" stored="false" : required="false" multiValued="false"/> can you try changing those to stored="true" and re-indexing as a sanity check? perhaps your indexing code is putting a default value in that you aren't realizing? w/o more specifics (ie: sample docs to index) on how to reproduce, i can't seem to find any problem. -Hoss