Support @Fields() for multiple indexing per property (useful for sorting)

Description

None

Attachments

1

Activity

Show:

Emmanuel BernardMay 31, 2007 at 2:05 AM

Looks nice, thanks
it's missing the ability to define a FieldBridge (and analyzer later) per Field, so I'll take some time to cook it and mark it for beta3 (I'm cutting beta2 as we speak).

Brandon MunroeMay 31, 2007 at 1:11 AM

I have gone ahead and implemented the Fields annotation. Attached is the patch, with the LuceneQueryTest modified to provide proof of concept for the Fields annotation working, using sorting.

Brandon MunroeMay 15, 2007 at 1:01 AM

Continuing the discussion from: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-4

I believe @Fields would be perfectly adequate, I only created the @SortField because I was trying to keep the "one field per property" restriction that was in place. If you think that it would be best to just use the @Fields for sorting, then I don't see any issues arising from it.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created May 4, 2007 at 5:51 AM
Updated November 13, 2008 at 6:07 PM
Resolved July 25, 2007 at 10:45 PM