[
https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206413#comment-13206413
]
Piergiorgio Lucidi edited comment on CONNECTORS-288 at 2/14/12 4:39 PM:
------------------------------------------------------------------------
{quote}1 - indent{quote}
{quote}2 - add the velocity parameters{quote}
Luca, I could work on this if you want ;)
Let me know!
{quote}
4 - integration tests
{quote}
Here I can help Luca and I can implement the integration test module, in this
way Luca could continue working directly on the connector.
I published a post in the ElasticSearch group to have a suggestion about
integration tests:
http://groups.google.com/group/elasticsearch/browse_thread/thread/5d568a7f5803acd0
This just to have their opinion about how to implement generic integration
tests.
Anyway I have an idea: we could download the latest stable distribution,
extract it and then start the search server with the bash command. But I would
like to understand if we can use the Java API directly as I saw in their
integration tests code, it could be better to control the instance parameters.
I'm looking forward for their reply and let us see how we could continue :)
Anyway here the integration tests process workflow that I would like to
implement:
* download, extract and run ElasticSearch server (the standard port is 9200)
* start Jetty with ManifoldCF
* create the test area on the File System
* configure the File System Repository Connection, ElasticSearch Output
Connection and the job for ManifoldCF using the REST API
* start the ManifoldCF job for crawling the File System connection and putting
content indexes in ElasticSearch server
* check results invoking standard query against the search server to verify the
work of the output connector
WDYT?
was (Author: [email protected]):
{quote}1 - indent{quote}
{quote}2 - add the velocity parameters{quote}
Luca, I could work on this if you want ;)
Let me know!
{quote}
4 - integration tests
{quote}
Here I can help Luca and I can implement the integration test module, in this
way Luca could continue working directly on the connector.
I published a post in the ElasticSearch group to have a suggestion about
integration tests:
http://groups.google.com/group/elasticsearch/browse_thread/thread/5d568a7f5803acd0
This just to have their opinion about how to implement generic integration
tests.
Anyway I have an idea: we could download the latest stable distribution,
extract it and then start the search server with the bash command. But I would
like to understand if we can use the Java API directly as I saw in their
integration tests code, it could be better to control the instance parameters.
I'm looking forward for their reply and let us see how we could continue :)
I suggest to use the OpenCMIS InMemory Server to test this new connector, I
used this in the CMIS Connector integration tests.
Anyway here the integration tests process workflow that I would like to
implement:
* download, extract and run ElasticSearch server (the standard port is 9200)
* start Jetty with ManifoldCF and OpenCMIS InMemory Server web app (the
standard port is 8085, for CMIS server I will set 9090)
* create the test area on the CMIS server
* configure CMIS Repository Connection, ElasticSearch Output Connection and the
job for ManifoldCF using the REST API
* start the ManifoldCF job for crawling the CMIS server and putting content
indexes in ElasticSearch server
* check results invoking standard query against the search server to verify the
work of the output connector
WDYT?
> 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, 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
