search for: hdr_name

...greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) > Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? The idea is that it calls something like: - build_key(type=hdr, hdr_name=From) - build_more("tss at iki.fi") - build_key(type=hdr, hdr_name=Subject) - build_more("Re: Solr -> Xapian ?") - build_key(type=body_part) - build_more("message body piece") - build_more("message body piece2") ... > Q3 : Searching/Lookup : THe...

...orting out-of-order indexing would be rather difficult to keep track of.) > > Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? > The idea is that it calls something like: > > - build_key(type=hdr, hdr_name=From) > - build_more("tss at iki.fi") > - build_key(type=hdr, hdr_name=Subject) > - build_more("Re: Solr -> Xapian ?") > - build_key(type=body_part) > - build_more("message body piece") > - build_more("message body piece2") > ... >...

...> > There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? > > On 2019-01-06 15:41, Joan Moreau wrote: > > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan Moreau wrote: > > for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? > > On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > > Thank you > > I...

...ed by "build_key". Why </div> <div> so ? What is the link with "build_more" ? </div> <div> The idea is that it calls something like: </div> <div> <br> </div> <div> - build_key(type=hdr, hdr_name=From) </div> <div> - build_more(" <a href="mailto:tss@iki.fi">tss@iki.fi</a>") </div> <div> - build_key(type=hdr, hdr_name=Subject) </div> <div> - build_more("Re: Solr -> Xapian ?")...

...rogram terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f4834fcc222 in fts_user_get_data_lang (user=0x16c7900) at fts-user.c:302 302 fts-user.c: No such file or directory. (gdb) info locals hdr = 0x1701f08 key = {uid = 8553, type = FTS_BACKEND_BUILD_KEY_HDR, part = 0x1696860, hdr_name = 0x1702120 "To", body_content_type = 0x0, body_content_disposition = 0x0} (gdb) bt full #0 0x00007f4834fcc222 in fts_user_get_data_lang (user=0x16c7900) at fts-user.c:302 fuser = 0x0 lang = 0x0 error = 0xf <error: Cannot access memory at address 0xf&g...

...t-of-order indexing would be rather difficult to keep track of.) > >> Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? > > The idea is that it calls something like: > > - build_key(type=hdr, hdr_name=From) > - build_more("tss at iki.fi") > - build_key(type=hdr, hdr_name=Subject) > - build_more("Re: Solr -> Xapian ?") > - build_key(type=body_part) > - build_more("message body piece") > - build_more("message body piece2") > ... >...

...tions on the mailbox ??? There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? On 2019-01-06 15:41, Joan Moreau wrote: > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan Moreau wrote: > > for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? > > On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > > Thank you > > I...

...e the greatest UID. (Supporting out-of-order indexing would be rather difficult to keep track of.) Q2 : WHen Indexing an email, the data is not passed by "build_key". Why so ? What is the link with "build_more" ? The idea is that it calls something like: - build_key(type=hdr, hdr_name=From) - build_more("tss at iki.fi") - build_key(type=hdr, hdr_name=Subject) - build_more("Re: Solr -> Xapian ?") - build_key(type=body_part) - build_more("message body piece") - build_more("message body piece2") ... Q3 : Searching/Lookup : THe fhea...

...er difficult to keep >> track of.) >> >> Q2 : WHen Indexing an email, the data is not passed by "build_key". Why >> so ? What is the link with "build_more" ? >> The idea is that it calls something like: >> >> - build_key(type=hdr, hdr_name=From) >> - build_more(" tss at iki.fi") >> - build_key(type=hdr, hdr_name=Subject) >> - build_more("Re: Solr -> Xapian ?") >> - build_key(type=body_part) >> - build_more("message body piece") >> - build_more("message bo...

Hi all, I'm planning to migrate my courier-imap imap server to dovecot, but I'm experiencing a strange issue with fts-lucene plugin. Basically, every time I start a search, the log starts to write: Apr 05 19:30:53 indexer: Error: Indexer worker disconnected, discarding 1 requests for XXXXXX Apr 05 19:30:53 indexer-worker(XXXXX): Fatal: master: service(indexer-worker): child 809 killed

On 10 May 2015, at 06:19, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > I'm now seeing these crashes in the indexing code: > > May 10 12:22:32 tornado.reub.net dovecot: master: Dovecot v2.2.17.rc1 (3903badc4ee0+) starting up for imap, lmtp, sieve > ... > May 10 13:07:50 tornado.reub.net dovecot: indexer: Error: Indexer worker disconnected, discarding 1

...ex=0x8b24130, uid=4403, part_idx=0, > data=0x8b38f08 "1: kernel: i7core_edac 0000:00:14.0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing "..., size=8188, > hdr_name=0x0) at lucene-wrapper.cc:582 > namesize = <optimized out> > dest = 0x915f5d0 L"1: kernel: i7core_edac 0000:00:14 0: restoring config space at offset 0x3 (was 0x800000, writing 0x800010)\n 1: kernel: pci 0000:00:1c 0: restoring config space at offset 0x1 (was 0x1...

for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > Thank you > > I still don't get the "build_key" function. The email (body, hearders, .. and the uid) is the one (and only) to index . What "key" is that function referring to ? Or is the

...;fts_backend_update_set_build_key" #8 0x00007f30fb0ba243 in fts_build_mail_header (block=0x7ffc1ba2c340, block=0x7ffc1ba2c340, ctx=0x7ffc1ba2c3b0) at fts-build-mail.c:173 hdr = <optimized out> key = {uid = 6006200, type = FTS_BACKEND_BUILD_KEY_HDR, part = 0x55c7b935eed0, hdr_name = 0x55c7b943fb5f "RETURN-PATH", body_content_type = 0x0, body_content_disposition = 0x0} ret = <optimized out> #9 fts_build_mail_real (may_need_retry_r=0x7ffc1ba2c2f3, retriable_err_msg_r=0x7ffc1ba2c300, mail=0x55c7b93dcff8, update_ctx=0x55c7b93e0140) at fts-buil...

also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? On 2019-01-06 14:10, Joan Moreau wrote: > for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? > > On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > > Thank you > > I still don't...

...> > There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? > > On 2019-01-06 15:41, Joan Moreau wrote: > > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan Moreau wrote: > > for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? > > On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > > Thank you > > I...

...> > There is alredy "fts_backend_xxx_update_expunge", so I beleive the management of the expunged messages is *NOT* in the backend, right ? > > On 2019-01-06 15:41, Joan Moreau wrote: > > also, for fts_backend_solr_update_set_build_key -> where is the data (of the hdr_name or the body) ? > > On 2019-01-06 14:10, Joan Moreau wrote: > > for the "last uid"-> this is not the last added, but the maximum of the UID in the indexed emails, right ? > > On 2019-01-06 11:53, Joan Moreau via dovecot wrote: > > Thank you > > I...

..."fts_backend_update_set_build_key" #6 0x00007ffff674dbb8 in fts_build_mail_header (block=0x7fffffffdcd0, block=0x7fffffffdcd0, ctx=0x7fffffffdd20) at fts-build-mail.c:174 hdr = <optimized out> key = {uid = 96, type = FTS_BACKEND_BUILD_KEY_HDR, part = 0x5555557dd2c0, hdr_name = 0x5555558396b0 "Return-Path", body_content_type = 0x0, body_content_disposition = 0x0} ret = <optimized out> #7 fts_build_mail_real (mail=0x555555838190, update_ctx=0x55555583a550) at fts-build-mail.c:548 block = {part = 0x5555557dd2c0, hdr = 0x555555839458, data...

...twhat = 0x58 <error: Cannot access memory at address 0x58>, error_number = 30249224} #10 0x0000000803b8c42e in lucene_index_build_more (index=0x801c1b640, uid=39486, part_idx=0, data=0x806041000 "<m.ray.mullins+caf_=mrm=lerctr.org at gmail.com>", size=45, hdr_name=0x801c1a520 "Return-Path") at lucene-wrapper.cc:572 id = L"\x1cc8c40\b\xffffd970\x7fff\xffffd960\x7fff\x1190eba\b\x1cc0c00\b\x1191739\b\x1cc8c40\b\x1190eba\b\xffffd990\x7fff-\000\000\001-" namesize = 34378158489 datasize = 140737488345424 dest = 0...

...order indexing would be rather difficult to keep > track of.) > > Q2 : WHen Indexing an email, the data is not passed by "build_key". Why > so ? What is the link with "build_more" ? > The idea is that it calls something like: > > - build_key(type=hdr, hdr_name=From) > - build_more(" tss at iki.fi") > - build_key(type=hdr, hdr_name=Subject) > - build_more("Re: Solr -> Xapian ?") > - build_key(type=body_part) > - build_more("message body piece") > - build_more("message body piece2") > ....