Hi,
I see SOLR-16443 is being addressed in version 9.
Will this jackson-databind update also be applied to 8.11?
Thanks,
Jay
Hi Thomas,
I am attempting to define my fields to accept the data that will actually be
sent, it is more deeply nested.
In doing so I have interpreted the results of the previous configuration to not
include (pseudo-)fields. In the JSON below I believe those to be "content" from
the prior exampl
This mail server chopped off my cur request so I am posting it here with the
domain marked out so it just looks like text:
curl --location --request POST '
:8983/solr/talix/update?json.command=false' \
--header 'Content-Type: application/json' \
--data-raw '{
"partner": "88027688-62c4-459a-
Are there any differences between your jetty and solr.xml setup between
your local and cloud installation?
- Houston
On Wed, Oct 26, 2022 at 1:10 PM Stephen Lewis Bianamara <
stephen.bianam...@gmail.com> wrote:
> Hi Solr Community,
>
> I have been looking into the v2 API and testing it with solr
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 rathe
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 na
Solr does deviate from the 'does not assign any significance to the
ordering of name/value pairs' part of that spec though. The order of "add"s
and "delete"s within an update request does matter.
Thomas
Op ma 31 okt. 2022 om 21:50 schreef Walter Underwood :
> Duplicate keys are somewhat surprisi
On 2022-10-31 4:55 PM, Thomas Corthals wrote:
Solr does deviate from the 'does not assign any significance to the
ordering of name/value pairs' part of that spec though. The order of "add"s
and "delete"s within an update request does matter.
Yeah, that's the other problem with using a dict (pyt
Hi Matthew
If you set json.command=false your JSON will be treated as custom JSON.
You'll have to remove that parameter to have it treated as Solr JSON. You
can use the full command index:
curl --location --request POST ' :8983/solr/talix/update' \
--header 'Content-Type: application/json' \
