Did you try the sort? Operations applied in the indexing analysis chain do
not affect the stored version of the field, the one you see in search
results. They only affect the internal lucene indexed version of the
field, which is what will be used for sorting. The Solr admin UI provides
an Analysi
>
> Cheers,
> Calvin
>
> On Mon, Jul 1, 2024 at 3:39 PM Jeremy Buckley - IQS-C
> wrote:
>
> > I can reproduce the error on a fresh collection with only a single
> document
> > added, so it may be something related to my schema.
> >
> > I think at t
ce_list_url, but instead by some
> other field (or even document) that is identified as a nested object.
>
> If you can provide a simplified reproducer, it will be easier to suggest
> working solutions.
>
> On Mon, Jul 1, 2024 at 5:58 PM Jeremy Buckley - IQS-C
> wrote:
>
>
r request? One potential root
> cause I can think of is mixing the endpoints /update/json/docs and /update.
>
> Sincerely,
> Christos
>
> On Sun, Jun 30, 2024 at 8:50 PM Jeremy Buckley - IQS-C
> wrote:
>
> > After updating to 9.6.1, the following updat
After updating to 9.6.1, the following update is failing:
[{
"id":"contracts 36F79718D0274 | 65 II C",
"price_list_url" : { "set" : "https://prices.anywhere.com"; }
}]
Solr responds with:
{
"responseHeader": {
"rf": 1,
"status": 400,
"QTime": 4
},
"error":
Try this. In your schema, explicitly define all the fields that you want
in your collection. Then, as the last field entry, add:
On Tue, Jun 4, 2024 at 1:06 PM Thomas Corthals
wrote:
> When you extra text from PDF with Tika, it includes additional metadata
> fields. This is the document I ge
