manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1219) Lucene Output Connector
Date Wed, 15 Jul 2015 09:59:04 GMT


Karl Wright commented on CONNECTORS-1219:

This is why I think we need a different process architecture.

There's a technology we use for Documentum and FileNet that might help here, called RMI. 
Each of these connectors has two "sidecar" processes that are required -- one is a service
process, and the other is a registry process.  There is only one of each process for a connector
for all of the ManifoldCF processes.

If there is a Lucene sidecar process, it could also run Jetty and provide search services,
so it would all work.

RMI uses Java serialization to work, so I don't know whether streams would do the right thing
or not.  I will have to do some research into how to do it.  But if Java streams do not work
there still should be a way to do it, because the underlying idea is just a socket that connects
objects on either side of the process boundary.

> Lucene Output Connector
> -----------------------
>                 Key: CONNECTORS-1219
>                 URL:
>             Project: ManifoldCF
>          Issue Type: New Feature
>            Reporter: Shinichiro Abe
>            Assignee: Shinichiro Abe
>         Attachments: CONNECTORS-1219-v0.1patch.patch, CONNECTORS-1219-v0.2.patch, CONNECTORS-1219-v0.3.patch
> A output connector for Lucene local index directly, not via remote search engine. It
would be nice if we could use Lucene various API to the index directly, even though we could
do the same thing to the Solr or Elasticsearch index. I assume we can do something to classification,
categorization, and tagging, using e.g lucene-classification package.

This message was sent by Atlassian JIRA

View raw message