hanaliang 's Profile

Potential UTF-8 encoding issue

This is a small note: In some environment, the default javascript escape() may fail to encoded non-ASCII character into the utf-8 encoded string, which will make the search failed.

To solve the problem universally, please refer the utf-8 encoding package by webtoolkit.info to write your own encoding function: http://www.webtoolkit.info/javascript-url-decode-encode.html

Potential UTF-8 encoding issue

This is a small note: In some environment, the default javascript escape() may fail to encoded non-ASCII character into the utf-8 encoded string, which will make the search failed.

To solve the problem universally, please refer the utf-8 encoding package by webtoolkit.info to write your own encoding function: http://www.webtoolkit.info/javascript-url-decode-encode.html

Tagging and excluding Filters

One can tag specific filters and exclude those filters when faceting. This is generally needed when doing multi-select faceting.

Consider the following example query with faceting:

q=mainquery&fq=status:public&fq=doctype:pdf&facet=on&facet.field=doctype

Because everything is already constrained by the filter doctype:pdf, the facet.field=doctype facet command is currently redundant and will return 0 counts for everything except doctype:pdf.

To implement a multi-select facet for doctype, a GUI may want to still display the other doctype values and their associated counts, as if the doctype:pdf constraint had not yet been applied. Example:

=== Document Type ===
  [ ] Word (42)
  [x] PDF  (96)
  [ ] Excel(11)
  [ ] HTML (63)

To return counts for doctype values that are currently not selected, tag filters that directly constrain doctype, and exclude those filters when faceting on doctype.

q=mainquery&fq=status:public&fq={!tag=dt}doctype:pdf&facet=on&facet.field={!ex=dt}doctype

Filter exclusion is supported for all types of facets. Both the tag and ex local params may specify multiple values by separating them with commas.

ample, the place fields will be indexed in the
Place index. The Place index
documents will also contain the fields address.id,
address.street, and address.city
which you will be able to query. This is enabled by the
@IndexedEmbedded annotation.

Be careful. Because the data is denormalized in the Lucene index
when using the @IndexedEmbedded technique,
Hibernate Search needs to be aware of any change in the
Place object and any change in the
Address object to keep the index up to date. To
make sure the Place Lucene
document is updated when it's Address changes,
you need to mark the other side of the bidirectional relationship with
@ContainedIn.

@ContainedIn is only useful on associations
pointing to entities as opposed to embedded (collection of

When @IndexedEmbedded points to an entity, the association has to
be directional and the other side has to be annotated
@ContainedIn (as seen in the previous example). If
not, Hibernate Search has no way to update the root index when the
associated entity is updated (in our example, a Place
index document has to be updated when the associated
Address instance is updated).

Sometimes, the object type annotated by
@IndexedEmbedded is not the object type targeted
by Hibernate and Hibernate Search. This is especially the case when
interfaces are used in lieu of their implementation. For this reason you
can override the object type targeted by Hibernate Search using the
targetElement parameter.