[jira] [Commented] (CONNECTORS-1079) the parsing in TikaExtractor always return empty result
[ https://issues.apache.org/jira/browse/CONNECTORS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184445#comment-14184445 ] Mingchun Zhao commented on CONNECTORS-1079: --- Karl, thanks! It does work pretty well. the parsing in TikaExtractor always return empty result --- Key: CONNECTORS-1079 URL: https://issues.apache.org/jira/browse/CONNECTORS-1079 Project: ManifoldCF Issue Type: Bug Components: Tika extractor Affects Versions: ManifoldCF 2.0 Reporter: Mingchun Zhao Assignee: Karl Wright Fix For: ManifoldCF 1.8, ManifoldCF 2.0 When I use latest trunk source(2.0) to try the Tika content extractor,It did not return any expected results. I looked at it using debugging tools, found that the parser of Tika content extractor does not return any data. I've tried to move lib/tika-core-1.6.jar into connector-lib/, Then, the Tika content extractor returned data as expected. My configurations are as below: == Transformation: Type: Tika content extractor Output: Type:Solr(Use extract update handler=false) Repository: type: Web Job: 1.type: repository 2.type: transformation 3.type: output == Maybe, it is related to CONNECTORS-1074(?), It looks like that the place of tika-core-1.6.jar affects the result of TikaExtractor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1077) Add activity logging for decision and exception events across all connectors
[ https://issues.apache.org/jira/browse/CONNECTORS-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184589#comment-14184589 ] Muhammed Olgun commented on CONNECTORS-1077: r1634373 (trunk) for GridFS Add activity logging for decision and exception events across all connectors Key: CONNECTORS-1077 URL: https://issues.apache.org/jira/browse/CONNECTORS-1077 Project: ManifoldCF Issue Type: Improvement Components: Alfresco connector Affects Versions: ManifoldCF 2.0 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 2.0 Attachments: Example.patch, capture, elasticsearch_review.patch, elasticsearch_review2.patch Many document skip decisions or transient exceptions are only logged, and are not recorded as history events. This makes it necessary upon occasion to refer to the manifoldcf log for basic diagnosis. We should record activity events for most decisions and exceptions in the history. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CONNECTORS-1085) Introduce a mcf-connector-common.jar to save binary delivery space
[
https://issues.apache.org/jira/browse/CONNECTORS-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14184807#comment-14184807
]
Karl Wright commented on CONNECTORS-1085:
-
This change trims our binary down to this:
{code}
10/27/2014 12:15 AM 168,748,568 apache-manifoldcf-2.0-dev-bin.zip
{code}
Introduce a mcf-connector-common.jar to save binary delivery space
--
Key: CONNECTORS-1085
URL: https://issues.apache.org/jira/browse/CONNECTORS-1085
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 2.0
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 2.0
The ManifoldCF 2.0 deliverable provides a number of connector-only services
in mcf-core, such as:
- ISO 8601 date parsing and formatting
- Axis SOAP transport support via Httpcomponents Httpclient
- extension to mime type mapping
These functions have the unfortunate requirement that many (large) jar
packages wind up needing to be included at the root level, which since these
wind up in all of the various war files, really bloats the binary deliverable.
For MCF 2.0, we can fix this by moving this functionality to a
mcf-connector-common.jar, which would be included in connector-lib rather
than at the root level.
This can't be done for MCF 1.8, because of backwards compatibility reasons.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
