The request contains the Hierarchy Manager configuration, a list of entity keys, and the filtering criteria. The response contains lists of entity records and relationships, and a search token to use for fetching additional information. Use GetOneHop to understand relationships between records in a hierarchy.

For timeline-enabled entities, the request must include the EffectiveDate parameter value.

When you use GetOneHop to calculate the best version of the truth for many records, increase the value of the following properties in

cmxserver.properties

:

For example, if you use GetOneHop for more than 10,000 records, set the values as shown in the following example:

sif.search.result.query.temptableTimeToLive.seconds=3600 
searchQuery.buildBvtTemp.MaxRowCount=100000

If you process a higher number of records, increase the values for the

searchQuery.buildBvtTemp.MaxRowCount

and

sif.search.result.query.temptableTimeToLive.seconds

properties.

If you enable timeline, start with a value of

5000

for the

searchQuery.buildBvtTemp.MaxRowCount

property.

You must also increase the transaction timeout value of the application server.