similar to: elasticsearch max results ignored

Hi, Is anyone using Spotlight with Elasticsearch in production and what kind of tweaking have you had to do? Certain search types seem to work out of the box, but others not. Perhaps fscrawler and Elasticsearch need some customization that the wiki doesn?t mention. There also seems to be a difference in using the main search box in the Finder window or the more granular options below, even if

Hi Pertu, On 6/3/24 10:34 AM, Perttu Aaltonen via samba wrote: > I see a lot of back and forth network traffic when the results are > displayed, so to me it looks like it could be due to fragmentation, > while the native results seem to come back in a big chunk. iirc I recently added fragmentation support to the mdssvc client, but it's still not implemented in the client. Though

When comparing to native macOS Spotlight searches, the Samba & elasticsearch combo is much slower, at least for me. Samba takes minutes to return a few hundred results, while native macOS returns thousands of results in a few seconds. This is remotely over a mobile connection, LAN is probably better. Is this due to the missing Spotlight RPC packet fragmentation support mentioned in the

Howdy! Am 10/2/20 um 6:02 PM schrieb Perttu Aaltonen via samba: > I used your excellent packages but also tried building from source. I?m trying to get Tracker working. Elasticsearch was simpler to get going but it doesn?t really suite the use case due to limitations in fscrawler. hm, a customer is using this with good results on laaaaaaarge datasets. I had seen you mentioning problems in an

Hi Louis, I used your excellent packages but also tried building from source. I?m trying to get Tracker working. Elasticsearch was simpler to get going but it doesn?t really suite the use case due to limitations in fscrawler. I actually created the mdssvc user but also tried directly under root once the dedicated user didn?t work. The problem might be somewhere in D-Bus configuration but I

On 07/28/2016 07:40 AM, Tim Dunphy wrote: > Hey guys, > > I have this log rotation script setup in my /etc/logrotate.d folder > > /var/log/elasticsearch/*.log { > daily > rotate 100 > size 50M > copytruncate > compress > delaycompress > missingok > notifempty > create 644 elasticsearch elasticsearch > } > >

Hey guys, I have this log rotation script setup in my /etc/logrotate.d folder /var/log/elasticsearch/*.log { daily rotate 100 size 50M copytruncate compress delaycompress missingok notifempty create 644 elasticsearch elasticsearch } And I notice that log files are still being generated that are upwards of 7 or 8 GBs. Can anyone point out to me where the

Samba 4.12 release notes <https://www.samba.org/samba/history/samba-4.12.0.html> mention "New Spotlight backend for Elasticsearch" and specify some new parameters for smb.conf, but there appear to be zero guides or further instructions for getting this to work. I'm not even clear how filesystem indexing is supposed to work. ElasticSearch appears to be simply a searchable

> On 23 Oct 2019, at 18.54, Ralph Boehme <slow at samba.org> wrote: > > On 10/23/19 4:31 PM, Perttu Aaltonen via samba wrote: >> From version 4.10.6 onwards folder icons are not working anymore on macOS. I can see the "._Icon?? file written on disk but seems like Samba isn?t reading it back and presenting it to the client. Is there a change or new setting that is needed

Hi all, I have started work on an ElasticSearch FTS plugin for Dovecot. It's available now on GitHub at: https://github.com/ascendantcom/fts-elasticsearch Please note that it is still in heavy development right now. It supports indexing, searching and expunging with some caveats (no multi-mailbox search or attachments). Pull requests, suggestions and bug reports very welcome! Cheers,

I've done a number of small projects (<1 mil) docs w xapian. However when our needs grew to a couple of hundred million docs no go. Index times get insanely slow very quickly We add about 250,000 docs a day. You can play games with switching indexes during updates and multiple remote dDBs. But why. Using ES we index 1000 new docs in 4 seconds. Our search times are subsecond in most

Hi Ralf, You should check you firewall configuration ... most probably you need to allow port 9200. Also check if elasticsearch service is listening on all interfaces or just localhost (127.0.0.1). -I. On Tue, Feb 19, 2019 at 2:48 PM Ralf Prengel <ralf.prengel at rprengel.de> wrote: > Hallo, > is anyone here using elasticsearch on centos? > I tried several configs to configure

Selinux will not allow connections on other than default http ports. semanage port -m -t http_port_t -p tcp 9200 Andrea -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Ralf Prengel Sent: Tuesday, February 19, 2019 8:09 AM To: centos at centos.org Subject: {EXTERNAL} Re: [CentOS] elasticsearch connection refused Am 19.02.2019 um 13:55 schrieb Ionut

I was looking for performance comparisons. I just found this link (http://blog.inoi.fi/2010/10/migrating-from-xapian-to-elasticsearch.html <http://blog.inoi.fi/2010/10/migrating-from-xapian-to-elasticsearch.html>). This was write on 2010. Could someone comment it ? Is There some truth in what he said? I hate java, and didn?t want to back to java search engines...

Hallo, is anyone here using elasticsearch on centos? I tried several configs to configure external access but nothing is working. My tests: telnet localhost or 127.0.0.1 9200 works local on the machine telnet 192.168.242.4 9200 connection refused local on the machine. So it is clear that access from other systems can not work. Is there perhaps something special to consider when using centos 7?

Hi, I would like to know if is possible to use ElasticSearch instead of Solr for FTS. Regards, Erick Vitor de Barros.

From version 4.10.6 onwards folder icons are not working anymore on macOS. I can see the "._Icon?? file written on disk but seems like Samba isn?t reading it back and presenting it to the client. Is there a change or new setting that is needed on more recent versions, or have I hit a bug? I noticed 4.10.6 had some work done regarding AppleDouble and resource forks. In the client log I?m

On 2019-02-19, Pete Biggs <pete at biggs.org.uk> wrote: > On Tue, 2019-02-19 at 14:26 +0000, Pete Biggs wrote: >> >> It's not a web server port - elasticsearch is a database. > > Sorry, that was a bit abrupt - yes, it sort of looks like a web server. It's a bit of both. It is queryable like a database, but it answers requests using HTTP methods. --keith --

On Tue, 2019-02-19 at 14:17 +0000, Laack, Andrea P wrote: > Selinux will not allow connections on other than default http ports. > > semanage port -m -t http_port_t -p tcp 9200 It's not a web server port - elasticsearch is a database. P.

Am 19.02.2019 um 13:55 schrieb Ionut Hoza: > Hi Ralf, > > You should check you firewall configuration ... most probably you need to > allow port 9200. > Also check if elasticsearch service is listening on all interfaces or just > localhost (127.0.0.1). Hallo, the firewall is disabled. I tried several variations in the config-file. 0.0.0.0 192.168.242.4 Only 127.0.0.1 is