Build failed in Jenkins: ManifoldCF-mvn #702

2019-02-28 Thread Apache Jenkins Server 
See 

--
[...truncated 447.17 KB...]
AU
site/src/documentation/resources/images/zh_CN/cmis-repository-connection-configuration-save.png
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-status.PNG
AU
site/src/documentation/resources/images/zh_CN/web-job-canonicalization.PNG
AU
site/src/documentation/resources/images/zh_CN/list-repository-connections.PNG
AU
site/src/documentation/resources/images/zh_CN/amazon-configure-server.PNG
AU
site/src/documentation/resources/images/zh_CN/email-configure-server.PNG
AU
site/src/documentation/resources/images/zh_CN/documentum-authority-user-mapping.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-web-client.PNG
AU
site/src/documentation/resources/images/zh_CN/opensearchserver-connection-parameters.PNG
AU
site/src/documentation/resources/images/zh_CN/add-new-authority-group-name.PNG
AUsite/src/documentation/resources/images/zh_CN/email-job-metadata.PNG
AU
site/src/documentation/resources/images/zh_CN/cmis-authority-connection-configuration-save.png
AUsite/src/documentation/resources/images/zh_CN/faq-list-path-rule.png
AUsite/src/documentation/resources/images/zh_CN/view-job.PNG
AUsite/src/documentation/resources/images/zh_CN/jdbc-status.PNG
AUsite/src/documentation/resources/images/zh_CN/hdfs-job-output-path.PNG
AU
site/src/documentation/resources/images/zh_CN/jdbc-configure-server.PNG
AU
site/src/documentation/resources/images/zh_CN/web-configure-access-credentials.PNG
AU
site/src/documentation/resources/images/zh_CN/wiki-configure-server.PNG
AU
site/src/documentation/resources/images/zh_CN/filesystem-job-hopcount.PNG
AU
site/src/documentation/resources/images/zh_CN/memex-connection-status.PNG
AU
site/src/documentation/resources/images/zh_CN/add-new-output-connection-type.PNG
AU
site/src/documentation/resources/images/zh_CN/dropbox-repository-connection-job-save.PNG
AU
site/src/documentation/resources/images/zh_CN/livelink-connection-document-view.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-authority-document-server.PNG
AU
site/src/documentation/resources/images/zh_CN/web-configure-bandwidth.PNG
AU
site/src/documentation/resources/images/zh_CN/solr-configure-arguments.PNG
AUsite/src/documentation/resources/images/zh_CN/documentum-status.PNG
AU
site/src/documentation/resources/images/zh_CN/transformation-throttling.PNG
AU
site/src/documentation/resources/images/zh_CN/documentum-authority-docbase.PNG
AU
site/src/documentation/resources/images/zh_CN/faq-list-all-metadata.png
AU
site/src/documentation/resources/images/zh_CN/regexp-mapping-status.PNG
AUsite/src/documentation/resources/images/zh_CN/list-jobs.PNG
AU
site/src/documentation/resources/images/zh_CN/hdfs-configure-server.PNG
AU
site/src/documentation/resources/images/zh_CN/dropbox-repository-connection-job-dropbox-folder-to-index.PNG
AUsite/src/documentation/resources/images/zh_CN/rss-job-time-values.PNG
AUsite/src/documentation/resources/images/zh_CN/filesystem-job-paths.PNG
AU
site/src/documentation/resources/images/zh_CN/alfresco-repository-connection-configuration-save.png
AU
site/src/documentation/resources/images/zh_CN/LCFApacheArchitecture.png
AUsite/src/documentation/resources/images/zh_CN/rss-job-exclusions.PNG
AUsite/src/documentation/resources/images/zh_CN/SecurityArchitecture.png
AUsite/src/documentation/resources/images/zh_CN/faq-list-summary.png
AUsite/src/documentation/resources/images/zh_CN/faq-list-contents.png
AU
site/src/documentation/resources/images/zh_CN/metadataadjuster-job-move-metadata.PNG
AUsite/src/documentation/resources/images/zh_CN/documentum-webtop.PNG
AUsite/src/documentation/resources/images/zh_CN/jdbc-job-security.PNG
AU
site/src/documentation/resources/images/zh_CN/add-new-authority-connection-name.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-connection-credentials.PNG
AU
site/src/documentation/resources/images/zh_CN/elasticsearch-job-parameters.png
AU
site/src/documentation/resources/images/zh_CN/add-new-mapping-connection-name.PNG
AU
site/src/documentation/resources/images/zh_CN/hdfs-repository-configure-server.PNG
AU
site/src/documentation/resources/images/zh_CN/repository-throttling-with-throttle.PNG
AU
site/src/documentation/resources/images/zh_CN/meridio-authority-user-service-server.PNG
AU
site/src/documentation/resources/images/zh_CN/view-authority-connection.PNG
AUsite/src/documentation/resources/images/zh_CN/rss-job-metadata.PNG
AU

[jira] [Commented] (CONNECTORS-1578) GSOC: Azure Storage Repository Connector

2019-02-28 Thread Rajiv Nayan (JIRA) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781210#comment-16781210
 ] 

Rajiv Nayan commented on CONNECTORS-1578:
-

[~piergiorgioluc...@gmail.com]  can you please tell me, how to subscribe the 
development mailing list

> GSOC: Azure Storage Repository Connector
> 
>
> Key: CONNECTORS-1578
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1578
> Project: ManifoldCF
>  Issue Type: New Feature
>  Components: Azure Storage Repository Connector
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Minor
>  Labels: gsoc2019
>
> This is a project idea for [Google Summer of 
> Code|https://summerofcode.withgoogle.com/] (GSOC).
> To discuss this or other ideas with your potential mentor from the Apache 
> ManifoldCF project, sign up and post to the dev@manifoldcf.apache.org list, 
> including "[GSOC]" in the subject. You may also comment on this Jira issue if 
> you have created an account. 
> We would like to extend the Content Indexing and Migration capabilities 
> adding Azure Storage as a new repository connector for reading and indexing 
> contents from one or more repositories supported by ManifoldCF. In this way 
> we will help users on indexing and migrating contents from different data 
> sources from Azure Storage.
> You will be involved in the development of the following tasks, you will 
> learn how to:
>  * Write the connector implementation
>  * Implement unit tests
>  * Build all the integration tests for testing the connector inside the 
> framework
>  * Write the documentation for this connector
> You will find a technical description about all the references to the Azure 
> Java SDK on an existing issue on our JIRA:
> https://issues.apache.org/jira/browse/CONNECTORS-1577
>  
> We have a complete documentation on how to implement a Repository Connector:
> [http://manifoldcf.apache.org/release/release-2.12/en_US/writing-repository-connectors.html]
>  
> Take a look at our book to understand better the framework and how to 
> implement connectors:
> [https://github.com/DaddyWri/manifoldcfinaction/tree/master/pdfs]
>  
> Prospective GSOC mentor: 
> [piergior...@apache.org|mailto:piergior...@apache.org]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (CONNECTORS-1588) Custom Jcifs Properties

2019-02-28 Thread Karl Wright (JIRA) 


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

Karl Wright reassigned CONNECTORS-1588:
---

Assignee: Karl Wright

> Custom Jcifs Properties
> ---
>
> Key: CONNECTORS-1588
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: JCIFS connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.13
>
> Attachments: CONNECTORS-1588
>
>
> In some cases, "jcifs" is running slowly. In order to solve this problem, we 
> need to set custom some properties. 
>   
>  For example; my problem was in my test environment: I have a windows server 
> and an ubuntu server in same network in AWS EC2 Service. The windows server 
> has Active Directory service, DNS Server and shared folder while the ubuntu 
> server has some instance such as manifoldcf, an db instance and solr. 
>   
>  If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
> Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1] 
> ; firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
> checks the DNS server. In my opinion, the linux server doesn't recognize the 
> DNS server and threads are waiting for every file for access to read.
>   
>  I suppose, WINS is used when accessing hosts on different subnets. So, I 
> have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
>   
>  Another suggestion for similar problem from [another 
> example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
>   
>  We need to set custom resolveOrder variable.
> ^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1588) Custom Jcifs Properties

2019-02-28 Thread Karl Wright (JIRA) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780473#comment-16780473
 ] 

Karl Wright commented on CONNECTORS-1588:
-

Patch looks fine.  I'll commit it.


> Custom Jcifs Properties
> ---
>
> Key: CONNECTORS-1588
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1588
> Project: ManifoldCF
>  Issue Type: Improvement
>  Components: JCIFS connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Cihad Guzel
>Assignee: Karl Wright
>Priority: Major
> Fix For: ManifoldCF 2.13
>
> Attachments: CONNECTORS-1588
>
>
> In some cases, "jcifs" is running slowly. In order to solve this problem, we 
> need to set custom some properties. 
>   
>  For example; my problem was in my test environment: I have a windows server 
> and an ubuntu server in same network in AWS EC2 Service. The windows server 
> has Active Directory service, DNS Server and shared folder while the ubuntu 
> server has some instance such as manifoldcf, an db instance and solr. 
>   
>  If the DNS settings are not defined on the ubuntu server, jcifs runs slowly. 
> Because the default resolver order is set as 'LMHOSTS,DNS,WINS'. It means[1] 
> ; firstly "jcifs" checks '/etc/hosts' files for linux/unix server'', then it 
> checks the DNS server. In my opinion, the linux server doesn't recognize the 
> DNS server and threads are waiting for every file for access to read.
>   
>  I suppose, WINS is used when accessing hosts on different subnets. So, I 
> have set "jcifs.resolveOrder = WINS" and my problem has been FIXED. 
>   
>  Another suggestion for similar problem from [another 
> example|https://stackoverflow.com/a/18837754] : "-Djcifs.resolveOrder = DNS"
>   
>  We need to set custom resolveOrder variable.
> ^[1]^ [https://www.jcifs.org/src/docs/resolver.html] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1563) SolrException: org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 bytes

2019-02-28 Thread Karl Wright (JIRA) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780373#comment-16780373
 ] 

Karl Wright commented on CONNECTORS-1563:
-

Hi [~Subasini],

The "excluded mime types" that you set are meant to exclude documents 
*entirely*, so changing that setting has no effect on *how* documents are 
indexed.  You can look at the Simple History report to verify that this is 
taking place as you desire, because most connectors create a record when they 
reject a document for any reason.  The Web Connector is no exception.


> SolrException: org.apache.tika.exception.ZeroByteFileException: InputStream 
> must have > 0 bytes
> ---
>
> Key: CONNECTORS-1563
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1563
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Lucene/SOLR connector
>Reporter: Sneha
>Assignee: Karl Wright
>Priority: Major
> Attachments: Document simple history.docx, Manifold and Solr 
> settings_CustomField.docx, managed-schema, manifold settings.docx, 
> manifoldcf.log, path.png, schema.png, solr.log, solrconfig.xml
>
>
> I am encountering this problem:
> I have checked "Use the Extract Update Handler:" param then I am getting an 
> error on Solr i.e. null:org.apache.solr.common.SolrException: 
> org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 
> bytes
> If I ignore tika exception, my documents get indexed but dont have content 
> field on Solr.
> I am using Solr 7.3.1 and manifoldCF 2.8.1
> I am using solr cell and hence not configured external tika extractor in 
> manifoldCF pipeline
> Please help me with this problem
> Thanks in advance



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CONNECTORS-1563) SolrException: org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 bytes

2019-02-28 Thread Subasini Rath (JIRA) 


[ 
https://issues.apache.org/jira/browse/CONNECTORS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780317#comment-16780317
 ] 

Subasini Rath commented on CONNECTORS-1563:
---

Hi Karl,
   After analysing I found that the below setting works fine if no MIMe type 
excluded in output connection.
I have to exclude MIME types like image/gif, image/jpg,text/css. I have 
specified them in the output connection-->documents tab-->Excluded MIME types.
When I removed, it worked fine.

Could you please suggest how it can work with excluded MIME types.





Thanks & Regards,
Subasini Rath
App Team Lead | TCS,Offshore
Mobile : +91-983-1234-341
M: subasini.r...@endeavourenergy.com.au | : www.endeavourenergy.com.au 
Planned Leave: 11th March – 13th March  
  



> SolrException: org.apache.tika.exception.ZeroByteFileException: InputStream 
> must have > 0 bytes
> ---
>
> Key: CONNECTORS-1563
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1563
> Project: ManifoldCF
>  Issue Type: Task
>  Components: Lucene/SOLR connector
>Reporter: Sneha
>Assignee: Karl Wright
>Priority: Major
> Attachments: Document simple history.docx, Manifold and Solr 
> settings_CustomField.docx, managed-schema, manifold settings.docx, 
> manifoldcf.log, path.png, schema.png, solr.log, solrconfig.xml
>
>
> I am encountering this problem:
> I have checked "Use the Extract Update Handler:" param then I am getting an 
> error on Solr i.e. null:org.apache.solr.common.SolrException: 
> org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 
> bytes
> If I ignore tika exception, my documents get indexed but dont have content 
> field on Solr.
> I am using Solr 7.3.1 and manifoldCF 2.8.1
> I am using solr cell and hence not configured external tika extractor in 
> manifoldCF pipeline
> Please help me with this problem
> Thanks in advance



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)