Indexing nested props with NEST 7.1 leads to unqueryable $ref props in indexed docs?!

[nielo]

Dear team and people out there,

we just upgraded from 6.3 to 7.1 and after recreating our indices and reindexing our docs poco properties like

[Nest.Nested]
public Address Location
{
    get { return HasAddress ? Address : Organizer?.Organization?.Address; }
}

with many properties inside like "Street", "Zip", "City" and so on are being saved in index with simple

      "Location" : {
        "$ref" : "7165"
      },

Simple queries with

,
            {
                "bool": {
                    "must": [
                        {
                            "range": {
                                "Location.Latitude": {
                                    "gte": 0,
                                    "lte": 100
                                }
                            }
                        }
                    ]
                }
            }

don't work anymore.
Does anybody have the slightest clue about what's going on here?

Thx in advance // nielo

[forloop (Russ Cam)]

Can you provide more detail about how the client is configured and the serializer that you're using? Also, the code that was used to index documents would also help.

[nielo]

Thanks, Russ, for your interest. Meanwhile I've found the reason: JsonNetSerializer's

PreserveReferencesHandling = PreserveReferencesHandling.All 

seemed to cause this internal json referencing.

[forloop (Russ Cam)]

My suspicion was that this is in the JsonNetSerializer configuration used, as "$ref" is a reference property used by Json.NET.