-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 
Author Message
 Post subject: Pad number bridge not built in to hibernate search?
PostPosted: Wed Feb 17, 2010 7:05 pm 
Regular
Regular

Joined: Mon Mar 10, 2008 6:40 pm
Posts: 114
Is it possible that Hibernate Search doesn't have a built-in bridge to pad numbers??


Top
 Profile  
 
 Post subject: Re: Pad number bridge not built in to hibernate search?
PostPosted: Thu Feb 18, 2010 9:36 am 
Hibernate Team
Hibernate Team

Joined: Thu Apr 05, 2007 5:52 am
Posts: 1689
Location: Sweden
Padding is not built-in. The documentation and in test code contain a PaddedIntegerBridge which you could use for build your own field bridge. This relates to HSEARCH-17

--Hardy


Top
 Profile  
 
 Post subject: Re: Pad number bridge not built in to hibernate search?
PostPosted: Fri Feb 19, 2010 1:06 am 
Regular
Regular

Joined: Mon Mar 10, 2008 6:40 pm
Posts: 114
hardy.ferentschik wrote:
Padding is not built-in. The documentation and in test code contain a PaddedIntegerBridge which you could use for build your own field bridge. This relates to HSEARCH-17

Seems like buying a car and then realizing you have to build the steering wheel... The Hibernate Search teem did such a great job on the product and didn't add the very basic but critical component of searching on numbers? Not a big deal.. and don't want to complain about what seems like an excellent product at an even better price :).


Top
 Profile  
 
 Post subject: Re: Pad number bridge not built in to hibernate search?
PostPosted: Sun Feb 21, 2010 7:55 am 
Hibernate Team
Hibernate Team

Joined: Fri Oct 05, 2007 4:47 pm
Posts: 2536
Location: Third rock from the Sun
I think it was never done as the format to be used depends a lot on use cases, like having negative numbers or not, float precision and effectively know the min/max boundaries; it's really recommended that users make their own conscious decision about it rather than let the framework pick an implementation flavor.

Of course if you can come up with some general purpose utility which you think would always be useful, that would definitely be considered to be included.
Please remember padding then needs to be applied also at query time, so it must satisfy both sorting and query requirements, and possibly also two-way bridge to enable projections or use on primary keys.

_________________
Sanne
http://in.relation.to/


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.