> > I would say that this throws an exception. At least atm. Numeric encoded > > fields needs to be targeted by a range query. One could imagine to > > transparently > > create a range query in this case. I guess by the metadata we could tell > > that we have > > a numeric field. However, that's a a lot of magic then, in particular since > > we > > always that that a keyword query maps to a TermQuery. > > Hum, but that's already happening, no? > > See DSLTest.testUseOfFieldBridge() where we do exactly that: > > monthQb.keyword().onField( "monthValue" ).matching( 2 ).createQuery(); > > Internally it's creating a NumericRangeQuery with start/end set to the > same value.
Hmm, I am pretty sure we did not start of this way, but maybe this has changed in the meantime. I seem to vaguely remember that we did something in this area after the first cut. --Hardy
pgpCQm0WUxNQl.pgp
Description: PGP signature
_______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
