I've the same problem but I cannot upgrade to Cloudera Navigator 2.11 because I cannot upgrade the whole CDH installation (I'm working with an Oracle BDA).
I can make a Cloudera Navigator backup so if you can share with us the workaround I will try to apply it.
AS an alternative workaround, may I delete the offending document from Cloudera Navigator Solr collection?
Thanks and regards
I am afraid that I'm not sure what workaround I thought might work; perhaps we were considering something that did not actually turn out to work around the problem... I'm don't know. I looked back at the internal Jiras and we don't have a workaround.
I know there are recent releases of Oracle BDA that contain the fix. I recommend working with Oracle to obtain a solution path.
There are no instructions on deleting individual documents to resolve this issue, though I suppose it may be possible.