The JSON keys within the "highlighting" object are the document IDs, and
then the keys within those objects are the highlighted field names.
Again, I repeat my question: Exactly why is it difficult to deserialize?
Seems simple enough.
-- Jack Krupansky
-----Original Message-----
From: Mysurf Mail
Sent: Tuesday, July 23, 2013 1:48 AM
To: solr-user@lucene.apache.org
Subject: Re: deserializing highlighting json result
the guid appears as the attribute id and not as
"id":"baf8434a-99a4-4046-8a4d-2f7ec09eafc8":
Trying to create an object that holds this guid will create an attribute
with name baf8434a-99a4-4046-8a4d-2f7ec09eafc8
On Mon, Jul 22, 2013 at 6:30 PM, Jack Krupansky
<j...@basetechnology.com>wrote:
Exactly why is it difficult to deserialize? Seems simple enough.
-- Jack Krupansky
-----Original Message----- From: Mysurf Mail Sent: Monday, July 22, 2013
11:14 AM To: solr-user@lucene.apache.org Subject: deserializing
highlighting json result
When I request a json result I get the following streucture in the
highlighting
{"highlighting":{
"394c65f1-dfb1-4b76-9b6c-**2f14c9682cc9":{
"PackageName":["- <em>Testing<em> channel twenty."]},
"baf8434a-99a4-4046-8a4d-**2f7ec09eafc8":{
"PackageName":["- <em>Testing<em> channel twenty."]},
"0a699062-cd09-4b2e-a817-**330193a352c1":{
"PackageName":["- <em>Testing<em> channel twenty."]},
"0b9ec891-5ef8-4085-9de2-**38bfa9ea327e":{
"PackageName":["- <em>Testing<em> channel twenty."]}}}
It is difficult to deserialize this json because the guid is in the
attribute name.
Is that solveable (using c#)?
