lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Sturge (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-2245) MailEntityProcessor Update
Date Thu, 25 Nov 2010 22:37:13 GMT

     [ https://issues.apache.org/jira/browse/SOLR-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Peter Sturge updated SOLR-2245:
-------------------------------

    Attachment: SOLR-2245.zip

This patch update does a more proper delta-import implementation, rather than the kludge used
in the previous version.
MailEntityProcessor with this patch is useful for importing emails 'en-masse' the first time
'round, then only new mails after that.

Behaviour:
* If you send a full-import command, then the 'fetchMailsSince' property specified in data-config.xml
will always be used.
* If you send a delta-import command, the 'fetchMailsSince' property specified in data-config.xml
is used for the first call only. 
  Subsequent delta-import commands will use the time since the last index update.

There are significant code changes in this version. So much so, that I've included the complete
MailEntityProcessor source as well as a PATCH file.

This version doesn't use the persistent last_index_time functionality of dataimport.properties
(i.e. it's delta only for the life of the solr process). If I get some free cycles, I'll try
to put this in.


> MailEntityProcessor Update
> --------------------------
>
>                 Key: SOLR-2245
>                 URL: https://issues.apache.org/jira/browse/SOLR-2245
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - DataImportHandler
>    Affects Versions: 1.4, 1.4.1
>            Reporter: Peter Sturge
>            Priority: Minor
>             Fix For: 1.4.2
>
>         Attachments: SOLR-2245.patch, SOLR-2245.patch, SOLR-2245.zip
>
>
> This patch addresses a number of issues in the MailEntityProcessor contrib-extras module.
> The changes are outlined here:
> * Added an 'includeContent' entity attribute to allow specifying content to be included
independently of processing attachments
>      e.g. <entity includeContent="true" processAttachments="false" . . . /> would
include message content, but not attachment content
> * Added a synonym called 'processAttachments', which is synonymous to the mis-spelled
(and singular) 'processAttachement' property. This property functions the same as processAttachement.
Default= 'true' - if either is false, then attachments are not processed. Note that only one
of these should really be specified in a given <entity> tag.
> * Added a FLAGS.NONE value, so that if an email has no flags (i.e. it is unread, not
deleted etc.), there is still a property value stored in the 'flags' field (the value is the
string "none")
> Note: there is a potential backward compat issue with FLAGS.NONE for clients that expect
the absence of the 'flags' field to mean 'Not read'. I'm calculating this would be extremely
rare, and is inadviasable in any case as user flags can be arbitrarily set, so fixing it up
now will ensure future client access will be consistent.
> * The folder name of an email is now included as a field called 'folder' (e.g. folder=INBOX.Sent).
This is quite handy in search/post-indexing processing
> * The addPartToDocument() method that processes attachments is significantly re-written,
as there looked to be no real way the existing code would ever actually process attachment
content and add it to the row data
> Tested on the 3.x trunk with a number of popular imap servers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message