Oracle Endeca – How to reduce the size of the Navigation query result?

By default Oracle Endeca Navigation query result would contain all the stored (searchable and non searchable) properties in the index. In many cases you may not want to show all the properties in the screen. Reducing the number of properties returned from the MDEX would also increase the performance of the whole query process. In this post we will share a sample navigation query that would limit the properties in the ERec to three.

This sample program would connect to an Oracle Endeca MDEX server and make a navigation query. Query will be applied with nid zero. This client connect to Oracle Endeca MDEX installed in localhost at default port 15000.

How to create navigation query that limit the properties in the result?

Complete sample program.

2 thoughts on “Oracle Endeca – How to reduce the size of the Navigation query result?

Leave a comment

Your email address will not be published. Required fields are marked *