search for: standardtokenizerfactori

Displaying 20 results from an estimated 21 matches for "standardtokenizerfactori".

2018 Dec 10
3
Solr
On 12/4/2018 10:40 AM, Joan Moreau via dovecot wrote: > > In the Wiki, ( https://wiki.dovecot.org/Plugins/FTS/Solr ), it would > nice to stipulate to the reader? to type the command : > > sudo -u solr /opt/solr/bin/solr create -c dovecot # to create the > dovecot instance > > before updating the schema.xml . > > Also,? schema.xml is in
2019 Jan 02
3
Solr
Refinement of the schema.xml (below) THis however does not solve the "no results" and "Out of range" errors in Dovecot and Solr <?xml version="1.0" encoding="UTF-8"?> <schema name="dovecot" version="2.0"> <uniqueKey>id</uniqueKey> <fieldType name="booleans" class="solr.BoolField"
2018 Dec 08
2
Solr
After some testsing, I managed to get proper functionning - The schema.xml is attached below (quite different from the one provided on teh wiki) (in bold the core differences) (NGramFilterFactory is the class that replace the fts_squat "partial=3 full=15", everything else is just a big hammer to smash a tiny fly) - One need to remove the "managed-schema" file in the
2018 Dec 15
2
Solr
here my latest schema.xml (remove the "long" type hich seems to be very deprecated in 7.x) <?xml version="1.0" encoding="UTF-8"?> <schema name="dovecot" version="2.0"> <uniqueKey>id</uniqueKey> <types> <fieldType name="string" class="solr.StrField" /> <fieldType name="gjlong"
2018 Dec 10
2
Solr
The one on the Wiki is mine...which I'm using now.? So it certainly does work - but perhaps there's a setting you have differently from me. Performing a "create -c dovecot" creates a Solr instance *named* dovecot - that does *not* initialize it with the necessary schema.? You need to specify "-d dovecot", with a dovecot configset already setup, to do that. The
2018 Dec 10
0
Solr
Hi Daniel, THere is no need of all this, just the command (on Solr 7.5) "create -c dovecot " is enough The chema.xml provided on the wiki basically does not work on 7.5 Here the latest one I am working on , but nothing works properly (bad search results, errors in ftp_solr, etc..) <?xml version="1.0" encoding="UTF-8"?> <schema name="dovecot"
2017 Feb 09
2
Solr 6.4.1
I've been running Solr for a while (4.10.3) - wanted to make the jump to the latest & greatest. I installed 6.4.1, copied over my schema.xml - and after a couple false starts where I needed to tweak it work with the new version...it works! I did not copy the database, started from scratch, and executed a "doveadm fts rescan -A". But... Judging solely from at least one
2018 Dec 11
0
Solr
I shared the errors already so many times (check this mailinling for "solr" in teh title) Contrary to what you say, with SOlr 7.5 and Dovecot git, I had to remove the "managed-schema" to make solr respond a bit properly. It relies on schema.xml In order to create the instance, no, it copies the default config in the dovecot instance. Bottom line, the end results is that
2018 Dec 21
3
Solr
Dear Daniel. Thank you for your kind reply. Regarding NFS, no, there is nothing like this in my setup. Deleteing SOLR and recreating it, I did it so many times already. I started with *your* setup in the first place, as FTS_squat (which actually works very well and very straightforward, I have no clue why going for SOlr which is just a pain and not maintaining squat), and it leads to
2018 Dec 09
0
Solr
However, Solr crashes and Dovecot plugin ftS_solr returns multitude of errors Dec 09 09:21:09 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' Dec 09 09:21:10 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' And returns are totaly funny (keywords not presentin teh
2018 Dec 16
0
Solr
Joan, I understand and sympathize with your frustration - trying to get multiple applications to work together, particularly given the lack of documentation for some of them, can be extremely challenging.? That said, I suggest you consider an alternative viewpoint.? Frequently being misunderstood myself I apologize in advance if I'm reading you wrong - but it appears your view towards
2018 Dec 05
5
Solr
THen the Squat shall be maintained until the SOlr plugin is upgraded, as Squat does resolve the problem (fts, partial search, etc...) On 2018-12-05 12:20, Aki Tuomi wrote: > It seems we forgot to document that "break-imap-search" was dropped in v2.3. That has now been updated. > > Also Solr does not support prefix/substring search unless you configure solr to support it.
2018 Dec 11
1
Solr
Additionally, here the errors I get in logs: Dovecot: Dec 09 09:21:09 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' Dec 09 09:21:10 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' or 11 03:36:03 indexer-worker(jom at
2018 Dec 12
2
Solr
On 12/11/2018 4:46 AM, Joan Moreau via dovecot wrote: > > I shared the errors already so many times (check this mailinling for > "solr" in teh title) > > Contrary to what you say, with SOlr 7.5 and Dovecot git,? I had to > remove the "managed-schema" to make solr respond a bit properly. It > relies on schema.xml > > In order to create the instance,
2018 Dec 30
3
Solr
Hi Daniel, I am on Archlinux. Anyway, I adapted the scripts. 2 questions: 1 - It looks like we are not on the same version . I am on 7.5.0. Which version are you running ? 2 - Your conf shows that you let managed-schema but deleted schema.xml. What is the meaning of each ? Thank you On 2018-12-22 00:19, Daniel Miller wrote: > Joan, > > The reason for dropping squat, I'm
2018 Dec 21
0
Solr
Joan, The reason for dropping squat, I'm assuming, is that Lucene and Solr potentially provide superior features & performance and as they are 3rd-party libraries & apps it reduces the maintenance responsibilities and let's the Dovecot team focus on mail server specific stuff - and let others focus on FTS.? There is a *huge* difference between a functional Solr setup &
2018 Dec 30
0
Solr
Also : - Java is 10.0.2 - If i delete schema.xml but create only managed-schema, the solr refuses to start with a java error "schema.xml missing" On 2018-12-30 08:46, Joan Moreau wrote: > Hi Daniel, > > I am on Archlinux. Anyway, I adapted the scripts. > > 2 questions: > > 1 - It looks like we are not on the same version . I am on 7.5.0. Which version
2019 Jan 02
0
Solr
Another bug appearing today: Jan 02 09:59:08 indexer-worker(jom at grosjo.net)<6777><MOgFATKLLFwPHAAA0thIag:oLJjJjKLLFx5GgAA0thIag>: Warning: FTS-SOLR(JOM at GROSJO.NET): Mailbox XXXXXX UID=121635 HEADER SIZE IS HUGE, TRUNCATING header of the said email has nothing of "huge" On 2019-01-02 15:22, Joan Moreau via dovecot wrote: > Refinement of the schema.xml (below)
2020 Nov 02
0
removing 'use_libfts' from dovecot fts_solr config; docs/examples of solr-backend-only tokenizer config for dovecot?
given existing problems with fts_solr = ... use_libfts ... i've rm'd it from dovecot config, and am moving all tokenization to solr config. iiuc, in dovecot + solr context, that's correctly config'd in solr/data/dovecot/conf/schema.xml dovecot release ships with 'starter configs', cp -af /usr/share/doc/dovecot/solr-config-7.7.0.xml
2019 Jan 02
1
Solr
In the code, it says #define SOLR_HEADER_MAX_SIZE (1024*1024) and line 620 if (!ctx->truncate_header && str_len(ctx->cur_value) >= SOLR_HEADER_MAX_SIZE) { /* a large header */ so this is a 1Mo header. This is of course completely wrong. Maybe this is not the root cause of the errors of fts_solr, but maybe this will help On 2019-01-02 18:00, Joan Moreau via dovecot