[
https://issues.apache.org/jira/browse/CONNECTORS-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651313#comment-14651313
]
Shinichiro Abe commented on CONNECTORS-1219:
--------------------------------------------
currently I took a solrcloud on hdfs way where the relationship between an
indexwriter and an index directory is 1 by 1. In HdfsDirectory, I can replace
HdfsLockFactory with NoLockFactory which OakDirectory applies. If I do, perhaps
multiple indexwriters will happen some errors about when updating an index
segment because each indexwriter has each segment info, when updating index
segment, then an indexwriter realizes the difference between a segment info
itself and an existing segment info which other' writer wrote, as a result some
exception will throw. It is worth to try to change NoLockFactory for me, but I
think this impl is risky thouth, I'll look into this next weekend. Thanks.
> 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)
