28.01.2013 Views

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SAP HANA Developer Guide - Get a Free Blog

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This deletes the node and all its child nodes.<br />

● To change the order of nodes or to move nodes to other parent nodes, you can drag and drop the nodes.<br />

With the <strong>SAP</strong> <strong>HANA</strong> studio running on Microsoft Windows, you can copy nodes below the same parent node<br />

or even to another parent node by pressing CTRL while dragging.<br />

● To change properties, click on the value of the property in the Properties view and enter the new value.<br />

Each node contains a set of properties that define the behavior of the search rules. Node properties are<br />

displayed in the Properties view of the <strong>SAP</strong> <strong>HANA</strong> studio when a node is selected in the tree. If the Properties<br />

view is not displayed, you can open it by choosing Window Show View Properties .<br />

Note: Some node properties refer to database objects or to column names. These properties are<br />

case-sensitive so you have to enter all names in the correct notation.<br />

Configuring Search Rule Sets<br />

● Define the attribute view.<br />

The search rule set searches on an attribute view that is modeled using the <strong>SAP</strong> <strong>HANA</strong> studio. The attribute<br />

view to be used is defined in the attribute view node of the search rule set. The name property contains the<br />

name of the attribute view. The FQN notation (fully qualified name) is used to specify the view.<br />

● Define the key columns and the score selection parameter.<br />

A search may return the same record more than once because it matches more than one rule.<br />

To enable the search to return each record only once, key columns must be defined in a way that makes<br />

records in the result set unique. For an attribute view, there is no definition of key columns available, so the<br />

key columns have to be defined for each search rule set.<br />

The key columns are a set of one or more columns of the attribute view that clearly identify a record in the<br />

view. So the key columns are similar to the primary key columns of a database table.<br />

As for primary keys, LOB types (BLOB, CLOB, NCLOB, TEXT) are not allowed as key columns.<br />

Note: It is possible to create an invalid key column definition that does not make the result set unique.<br />

In this case, when running a search, an error is raised when records returned by a single rule are not<br />

unique.<br />

By default, each search rule set contains one key column node below the attribute view node. If more columns<br />

are needed to make records unique, more key column nodes can be added below the attribute view node.<br />

In each key column node enter the name of the attribute view column in the properties panel.<br />

In addition to the key columns, you have to define how the result set shall be made unique. Records returned<br />

by more than one rule usually have different scores assigned. Only one combination of score and rule name<br />

can be returned in the result set.<br />

The score selection parameter defines whether the values with the highest score or the values found with the<br />

first matching rule are returned.<br />

The score selection parameter is defined in the properties panel of the rule set node.<br />

● Define stopwords and term mappings.<br />

To use stopwords and term mappings in a search rule set, the configuration options have to be added to the<br />

rule set.<br />

<strong>SAP</strong> <strong>HANA</strong> <strong>Developer</strong> <strong>Guide</strong><br />

Enabling Search<br />

P U B L I C<br />

© 2012 <strong>SAP</strong> AG. All rights reserved. 303

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!