[#GPSEARCHABLE-127] Mapping: More closure mapping configuration: Class and instance meta data, static and dynamic; analyzers; Searchable component, Searchable parent, id, ... - Grails JIRA

Details

Type: Improvement
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 0.3
Fix Version/s: 0.7
Component/s: None
Labels:
None

Issue Links

This issue is depended upon by:
GPSEARCHABLE-8	[Searchable Plugin] Oracle name

Options
- Show All
- Show Open

Sub-Tasks

1.	Config: Verify all Compass configuration is supported by Searchable Plugin hooks	Resolved	Maurice Nicholson
2.	allow alias to be set in searchable closure	Resolved	Maurice Nicholson
3.	allow constant meta data to be set in searchable closure	Resolved	Maurice Nicholson
4.	alow (constant) sub-index to be defined in searchable closure	Resolved	Maurice Nicholson
5.	allow (class default) analyzer to be defined in searchable closure	Resolved	Maurice Nicholson
6.	allow boost to be defined in searchable closure	Resolved	Maurice Nicholson
7.	allow (class default) converter to be defined searchable closure	Resolved	Maurice Nicholson
8.	expose Compass's @Searchable#enableAll option	Resolved	Maurice Nicholson
9.	expose Compass's @Searchable#managedId option	Resolved	Maurice Nicholson
10.	expose Compass's @Searchable#root option	Resolved	Maurice Nicholson
11.	expose Compass's @Searchable#supportUnmarshall option	Resolved	Maurice Nicholson
12.	expose Compass's @SearchableAllMetaData options as per XML all-xxx names	Resolved	Maurice Nicholson
13.	allow definitio of sub-index has like Compass's @SearchableSubIndexHash	Resolved	Maurice Nicholson
14.	allow dynamic constant meta data to be defined in searchable closure	Reopened	Maurice Nicholson
15.	expose functionality like Compass's @SearchableAnalyzerProperty	Open	Maurice Nicholson
16.	expose functionality like Compass's @SearchableBoostProperty	Open	Maurice Nicholson
17.	expose functionality like Compass's @SearchableId	Open	Maurice Nicholson
18.	review Compass @SearchableProperty fields and make sure they are valid for plugin mapping DSL	Resolved	Maurice Nicholson

Activity

Hide

Permalink

Maurice Nicholson added a comment - 13/Jun/07 6:19 AM

Also multiple meta-data mappings per field for "searchable properties", eg:

static searchable = {
    postcode() // or "postcode(name: 'postcode')" or similar
    postcode(name: 'postcodeUnTokenized, index: 'un_tokenized')
}

leading to two postcode fields in the index per record, one tokenized and one not (default).

Show

Maurice Nicholson added a comment - 13/Jun/07 6:19 AM Also multiple meta-data mappings per field for "searchable properties", eg:

static searchable = {
    postcode() // or "postcode(name: 'postcode')" or similar
    postcode(name: 'postcodeUnTokenized, index: 'un_tokenized')
}

leading to two postcode fields in the index per record, one tokenized and one not (default).

People

Assignee:

Maurice Nicholson

Reporter:

Maurice Nicholson

Vote (0)

Watch (0)

Dates

Created:

13/May/07 10:10 AM

Updated:

19/Jul/11 9:41 AM

Searchable Plugin

Mapping: More closure mapping configuration: Class and instance meta data, static and dynamic; analyzers; Searchable component, Searchable parent, id, ...