Hi all,
On Solr 8.6, I have a multivalued field of dateRange type which contains an
availability table.
"availabilities": [
"[2021-12-22T00:00:00Z TO 2022-01-02T23:59:59Z]",
"[2022-01-20T00:00:00Z TO 2022-02-02T23:59:59Z]",
"[2022-02-10T00:00:00Z TO 2022-02-21T23:59:59Z]"
]
With a facet,
Hi All
For some of our collections when we run a collections API DELETE
synchronously followed immediately by a configset API DELETE for the
underlying configset we end up in a messed up state.
I have been unable to reproduce this issue in a test environment, it only
happens on the live productio
Hi,
I am using Solr 8.5.2
I made a simple in-place update request to Solr. This request has two
fields, one is the unique field and the other one is a field that returns
true for AtomicUpdateDocumentMerger.isSupportedFieldForInPlaceUpdate.
When I intercept this request during the debugging proce
I had some time to check this today and it's a documentation snafu. The
correct key name is `collectionNodeType`.
- https://issues.apache.org/jira/browse/SOLR-16256
- https://github.com/apache/solr/pull/908
On Mon, Jun 13, 2022 at 6:58 PM Ixai Lanzagorta <
ixai.lanzago...@rondhuit.com> wrote:
>