: Ok, so my issue is that it must be a flat structure. Why isn't the JSON
: parser able to deconstruct the object into a flatter structure for indexing?
: Shouldn't it be able to take any valid JSON structure?
Becuase no one has contributed code to do it?
In general accepting any arbitrary JSON structures (or arbitary xml
structures) and deciding how to flatten that and what the resulting field
names should be is non-trivial.
there would need to be a set of default
mappings/assumptions, and configuration options for people who want to
tweak those default mappings/assumptions.
Your example had...
"shipping": [
{
"nextDay": 10.19,
"secondDay": 6.45,
"ground": 1.69
}
],
...where "shipping" is an array that can evidently contain multiple
sub-maps. should the keys in those sub-maps be mapped to fields like...
shipping_0_nextDay = 10.19
shipping_0_secondDay = 6.45
shipping_0_ground = 1.69
...
shipping_1_nextDay = ...
...or should things like "shipping_nextDay" be a multivalued field
collecting all of the values of the sub-maps in order...
shipping_nextDay = [ 10.19, ... ]
shipping_secondDay = [ 6.45, ... ]
shipping_ground = [ 1.69, ... ]
...your expecations are not neccessarily the same as everyone elses, so
the lowest common denominator is to have the clients decide exactly what
the field = value pairs should be and send them precisely.
-Hoss
