[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226945#comment-13226945 ]
Luca Stancapiano commented on CONNECTORS-288: --------------------------------------------- Ok....deleting the properties.xml after each test I can now run and fix the test. The problem of the delete is tied to a last update: class org.apache.manifoldcf.agents.output.elasticsearch.ElasticSearchDelete:row 34 {code} String fileName = java.net.URLEncoder.encode(documentURI,"utf-8"); {code} it must be a fileNome, not a Uri because it is the id to use for the delete. The delete method in the elasticsearch connector is as a curl as below: {code} curl -XDELETE http://localhost:9200/index/generictype/null {code} where gtgt is the 'fileName' variable so it'ld become so: {code} curl -XDELETE http://localhost:9200/index/generictype/http%3A%2F%2Flocalhost%3A9090%2Fchemistry-opencmis-server-inmemory%2Fatom%2F139%2Fnull {code} If you modify the row as it was before so: {code} String fileName = FilenameUtils.getName(documentURI); {code} the delete works. Done it there is a new problem tied to https://issues.apache.org/jira/browse/CONNECTORS-417: our test create multiple versions of the document called 'null' When the delete is called, the test succeeds to delete the first 'null' document because the dlete operation delete all versions for the document. So, after, the 'null' document is not more there but it try to delete anyhow and it goes in a loop. I suppose this problem is done because the resolution of https://issues.apache.org/jira/browse/CONNECTORS-417 is not committed in the branch. Let me know for it > An ElasticSearch connector would be helpful > ------------------------------------------- > > Key: CONNECTORS-288 > URL: https://issues.apache.org/jira/browse/CONNECTORS-288 > Project: ManifoldCF > Issue Type: New Feature > Affects Versions: ManifoldCF 0.5 > Reporter: Piergiorgio Lucidi > Assignee: Piergiorgio Lucidi > Labels: elasticsearch > Fix For: ManifoldCF next > > Attachments: manifold-elasticsearch-patch, > manifold-elasticsearch-patch, manifold-elasticsearch-patch, > manifold-elasticsearch-patch, manifold-elasticsearch-patch, > manifold-elasticsearch-patch, manifold-elasticsearch-patch, > manifold-elasticsearch-velocity-patch, manifoldcf-elasticsearch-project-patct > > Original Estimate: 120h > Remaining Estimate: 120h > > An ElasticSearch connector could be very useful to spread the use of > ManifoldCF -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira