[
https://issues.apache.org/jira/browse/CONNECTORS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627710#comment-14627710
]
Karl Wright commented on CONNECTORS-1219:
-----------------------------------------
Hi Abe-san,
>From what you say, only the single-process example can possibly work with the
>Lucene output connector that you have proposed. None of the multi-process or
>distributed models will work with it properly.
Before you commit to trunk, we really have to think this through, because this
would be the first connector with such a restriction. It might be better, for
instance, to have a secondary process in which Lucene runs, and a socket (maybe
with a REST API?) where the documents are sent and/or requests are made. It is
more work but it is also more consistent with ManifoldCF operating model.
> Lucene Output Connector
> -----------------------
>
> Key: CONNECTORS-1219
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1219
> 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
(v6.3.4#6332)
