Thanks. Done. https://issues.apache.org/jira/browse/SOLR-12321
On Mon, May 7, 2018 at 12:56 PM, Mark Miller wrote:
> Yeah, the project should never use built in serialization. I'd file a JIRA
> issue. We should remove this when we can.
>
> - Mark
>
> On Sun, May 6, 2018 at 9:39 PM Will Currie w
On 5/6/2018 3:09 PM, Atita Arora wrote:
I am working on a developing a utility which lets one monitor the
indexPipeline Status.
The indexing job runs in two forms where either it -
1. Creates a new core OR
2. Runs the delta on existing core.
To put down to simplest form I look into the DB timesta
Yeah, the project should never use built in serialization. I'd file a JIRA
issue. We should remove this when we can.
- Mark
On Sun, May 6, 2018 at 9:39 PM Will Currie wrote:
> Premise: During an upgrade I should be able to run a 7.3 pull replica
> against a 7.2 tlog leader. Or vice versa.
>
> M
Premise: During an upgrade I should be able to run a 7.3 pull replica
against a 7.2 tlog leader. Or vice versa.
Maybe I'm totally wrong in assuming that!
Assuming that's correct it looks like adding a new method[1] to
SolrResponse has broken binary compatibility. When I try to register a new
pull
When I looked at this in solr 5.5.3 The second phase of the query was only sent
to the shards that returned documents in the first phase, the problem is that
one shard may contain matching documents in a group but ranked outside the top
N results.
Fatduo this solution won't help you unless you
To those who noticed SortableTextField in Solr 7.3 and are curious
whether it is useful, it seems to be.
I've just finished a presentation at a Montreal Solr meetup on a rapid
schema evolution. I based it on a simplest schema/solrconfig that used
SortableTextField to make the initial data ingestio
Hi,
I am working on a developing a utility which lets one monitor the
indexPipeline Status.
The indexing job runs in two forms where either it -
1. Creates a new core OR
2. Runs the delta on existing core.
To put down to simplest form I look into the DB timestamp when the indexing
job was triggere