On 10/1/2017 1:05 AM, Nawab Zada Asad Iqbal wrote:
> When upgrading from solr4.5 to solr 7.0, I noticed that many key names in
> solr-mbeans
The metrics have been expanded and moved to a new API. Try this URL
instead:
http://server:port/solr/admin/metrics
The new location was added in 6.4:
ht
UpdateRequestProcessor is probably your best bet, because you can
choose to trigger them by name with import parameter.
Then you can probably use CloneFieldUpdateProcessorFactory.
Regards,
Alex.
http://www.solr-start.com/ - Resources for Solr users, new and experienced
On 27 September 2
I think you're looking for SortingMergePolicyFactory, see:
https://issues.apache.org/jira/browse/SOLR-5730
The JIRA has some extensive discussion and the reference guide has an
example. It might take a little digging
Best,
Erick
On Sun, Oct 1, 2017 at 4:36 AM, Ahmet Arslan wrote:
>
>
> Hi A
Hi Alex,
Lucene has this capability (borrowed from Nutch) under
org.apache.lucene.index.sorter package.I think it has been integrated into
Solr, but could not find the Jira issue.
Ahmet
On Sunday, October 1, 2017, 10:22:45 AM GMT+3, alexpusch
wrote:
Hello,
We've got a pretty big
Hello,
We've got a pretty big index (~1B small docs). I'm interested in managing
the index so that the search results would be naturally sorted by a certain
numeric field, without specifying the actual sort field in query time.
My first attempt was using SortingMergePolicyFactory. I've found that
hi,
When upgrading from solr4.5 to solr 7.0, I noticed that many key names in
solr-mbeans (
http://localhost:8983/solr/tcore/admin/mbeans?stats=true&wt=json) have
changed. Mostly, "parent key" name is also appended to the stats keyname
e.g., instead of cumulative_evictions, I now have to look for
