Does anyone know why the __Raw_bodyText field in the external index are not searchable? Or better yet, how to make these searchable? Hell, a third question - where did it come from? My external index seems to have a __Raw_ prefixed field for every property, some of which are indexed and searchable and others that aren't.
I know I can add custom fields in the GatheringNodeData event, but figured if it's already in there, why store it twice?
I'm fine with adding new fields, but I was more curious as to where the __Raw_ fields had come from - there's nothing I can find in my site that is adding these to the index, yet there they are.
I'd rather not store another copy of a node's HTML when it exists in the __Raw_bodyText field, but the issue is that it's not searchable. Which largely defeats the purpose of storing it in a searchable index.
If I have to, I'll push the raw html into a new field, but that leaves me with three copies in the index (bodyText, __Raw_bodyText, myNewRawHtml), which is a bit of bloat that I'd like to avoid.
As an aside - should my GatheringNodeData event fire when the index is rebuilt? It works fine when I publish a node, but not on the initial index build, which is when I really need it to fire to ensure the index contains the fields I need...
__Raw_bodyText in External index
Does anyone know why the
__Raw_bodyText
field in the external index are not searchable? Or better yet, how to make these searchable? Hell, a third question - where did it come from? My external index seems to have a__Raw_
prefixed field for every property, some of which are indexed and searchable and others that aren't.I know I can add custom fields in the
GatheringNodeData
event, but figured if it's already in there, why store it twice?Hi Nathan
Don't know if you perhaps have read these posts about Examine? http://24days.in/umbraco/2013/getting-started-with-examine/ and http://umbraco.com/follow-us/blog-archive/2011/9/16/examining-examine.aspx
If I get it right you should be able to configure Examine to include the field in your configuration.
Hope this helps.
/Jan
Hi Jan
I'm fine with adding new fields, but I was more curious as to where the __Raw_ fields had come from - there's nothing I can find in my site that is adding these to the index, yet there they are.
I'd rather not store another copy of a node's HTML when it exists in the __Raw_bodyText field, but the issue is that it's not searchable. Which largely defeats the purpose of storing it in a searchable index.
If I have to, I'll push the raw html into a new field, but that leaves me with three copies in the index (bodyText, __Raw_bodyText, myNewRawHtml), which is a bit of bloat that I'd like to avoid.
As an aside - should my GatheringNodeData event fire when the index is rebuilt? It works fine when I publish a node, but not on the initial index build, which is when I really need it to fire to ensure the index contains the fields I need...
Thanks for your help
Nathan
is working on a reply...