: Now I follow. I was misreading the first comments, thinking that the field : content would be deconstructed to smaller components or pieces. Too much : (or not enough) coffee.
that's my bad .. i was trying to explain the concept by simplifying the numeric range part out of the discussion and just tell you about hte multifield phrase query idea. : I'm expecting the index doc needs to be constructed with lat/long/dates in : sequential order, i.e.: there's no requirement that you actually interleave them in the file, but yes: the value you add to the lat field would need to corrispond to the first value you add to the lon field and the when field as a single event instance. the second value you add to each field would all ned to corrispond to each other as the next instance. : Assuming slop count of 0, while the intention is to match lat/long/when in : that order, could it possibly match long/when/lat, or when/lat/long? Does : PhraseQuery enforce order and starting point as well? the key is that you aren't storing the lat/lon/when in the same field wo you'll only match the time in the when field, the lat in the lat field etc... : Assuming all of this, how does range query come into play? Or could the : PhraseQuery portion be applied as a filter? this is why i said it was pretty theoretical ... not only would you need a modified version of PhraseQuery to work across multiple fields, you'd need to change it to match on ranges as well. -Hoss
