Partager via

Manually update navigator name

  • Article

In FAST ESP 5.3 you can update the navigator fields in the index profile and upload the new index profile using GUI or “bliss” command.

 

Index profile will check for the compatibility before the update and if the profile is incompatible then there can be chance of navigator fields failed to update.

 

You can see the below events in the bliss logs.

INFO : bliss@yourservername: systemmsg: Compatibility check: Attribute "display" for string-navigator with name="your old navigator name" in result-specification has different value "New navigator name".QR-server must be restarted.

INFO : bliss@yourservername: systemmsg: Compatibility check: Index-profiles are incompatible

INFO : bliss@yourservername: systemmsg: Running index-profile update without doing compatibility check

INFO : bliss@yourservername: systemmsg: New index-profile update finished successfully

 

If you check the output in FAST ESP QR-Server by accessing https://yourESPserver:15100 then you will still see the old navigator name. You can also verify the output for different views exist in your FAST ESP environment.

To get the updated navigator name try to clear the QR-server cache and to refresh and redeploy views. This can be done with the following steps:

 

  1. Stop the qrserver processes on all qrserver nodes.

  2. On all qrserver nodes, rename or move the $FASTSEARCH/var/qrserver/ directory to remove the 

              cache files.

  1. Restart the qrserver processes on all qrserver nodes.

  2. Run the following command to refresh the views:

              view-admin –m refresh

  1. Run the following command to deploy the views:

              view-admin –m deploy –a

 

If that doesn’t resolve the issue then follow the below steps to manually update the navigator name.

  1. Export the view in xml format which requires new navigator name update using the below command.

    view-admin -m export -V myview

  2. Manually edit the xml file, update the new navigator name and save it.

  3. Import the view using the below command.

    view-admin -m import -V teamsd1.xml -o –d

 

Note: Make sure you have taken the backup of exported view.xml file before editing and importing it to the ESP server. Even a minor index-profile update should be viewed as a serious procedure. This is not a simple task that lends itself to being performed every day on a multi-node cluster.

 

Reference: https://support.microsoft.com/en-us/kb/2587443

 

Published by - Prasad Joshi