Duplicate keys are somewhat surprising, but absolutely allowed and always have been.
From the ECMA JSON spec: "The JSON syntax does not impose any restrictions on the strings used as names, does not require that name strings be unique, and does not assign any significance to the ordering of name/value pairs.” https://www.ecma-international.org/publications-and-standards/standards/ecma-404/ wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Oct 31, 2022, at 1:42 PM, Adam Constabaris <ajcon...@ncsu.edu.INVALID> > wrote: > > I don't know if there's a generally accepted name for it (but see > https://en.wikipedia.org/wiki/JSON_streaming) -- when you're using JSON to > pass around large numbers of objects, it's nice to be able to treat the > data as "just a bunch of records" that you can process one by one as they > arrive rather than having to read a very large array of objects into memory > which you then process. These various kinds of "JSON serialization" see a > fair amount of use in the wild, including within Solr. > > cheers, > > AC > > > On Fri, Oct 28, 2022 at 6:01 PM dmitri maziuk <dmitri.maz...@gmail.com> > wrote: > >> On 2022-10-28 4:26 PM, Mikhail Khludnev wrote: >>> Well, Dmitry. Turns out keys in JSON _should be_ but not ought to be >>> unique. >> >> Right, just like a parachute _should_ but not ought to open on your way >> down. >> >>> You can think about streaming writer or reader in any rational >> programming >>> language. >> >> Of course I can hand-write the string to be any kind of garbage I want, >> and then hand-write a parser to read it. But JSON stands for JavaScript >> Object Notation. If a string can't be demarshalled into a valid >> JavaScript Object, it goes *splat* on the ground. >> >> Dima >> >>
