How about you 'xml encode' your content, instead of using CDATA:
testing
I don't entirely get what's going on for you. I just did a test, posting
this:
UV1
testing
And query
I am working with an xml format named EAD (Encoded Archival
Description). That format need to be precompiled before it can be
digested by solr.
So I just need to store in my index the original XML file.
Maybe I need to work with DIH ?
2012/12/20 Upayavira :
> Solr does not support nested structu
The index is stored normally but, when i ask the index, all xml markup
is deleted in the response.
For exemple, when i store this field:
I obtain this kind of response when i ask index:
2012/12/20 Alexandre Rafalovitch :
> What happens if you just supply it as CDATA into a string field? S
Right, you can store it, but you can't search on it that way, and you
certainly can't do complex searches that take the XML structure into
account (e.g. xpath queries).
Upayavira
On Thu, Dec 20, 2012, at 10:22 PM, Alexandre Rafalovitch wrote:
> What happens if you just supply it as CDATA into a s
What happens if you just supply it as CDATA into a string field? Store, no
index, probably compressed and lazy.
Regards,
Alex
On 20 Dec 2012 09:30, "Modou DIA" wrote:
> Hi everybody,
>
> i'm newbie with Solr technologies but in the past i worked with lucene
> and another solution similar to
Solr does not support nested structures. You need to flatten your data
before indexing. You can store data in the way you did to be returned to
your users, but you will not be able to search within the XML as XML.
If you can explain the problem you are trying to solve, maybe folks here
can help yo
