[jira] [Resolved] (CONNECTORS-408) Script engine scripts use MCF_HOME inconsistently with other scripts
[ https://issues.apache.org/jira/browse/CONNECTORS-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-408. Resolution: Fixed r1243320 > Script engine scripts use MCF_HOME inconsistently with other scripts > > > Key: CONNECTORS-408 > URL: https://issues.apache.org/jira/browse/CONNECTORS-408 > Project: ManifoldCF > Issue Type: Bug > Components: Examples >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > The script engine scripts do not use MCF_HOME in the same way that other > scripts do. The fix is to use a different environment variable for this > purpose. -- 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
[jira] [Created] (CONNECTORS-408) Script engine scripts use MCF_HOME inconsistently with other scripts
Script engine scripts use MCF_HOME inconsistently with other scripts Key: CONNECTORS-408 URL: https://issues.apache.org/jira/browse/CONNECTORS-408 Project: ManifoldCF Issue Type: Bug Components: Examples Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The script engine scripts do not use MCF_HOME in the same way that other scripts do. The fix is to use a different environment variable for this purpose. -- 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
[jira] [Resolved] (CONNECTORS-407) Ant build does not leave shell scripts with executable bits set for Linux
[ https://issues.apache.org/jira/browse/CONNECTORS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-407. Resolution: Fixed r1243314 > Ant build does not leave shell scripts with executable bits set for Linux > - > > Key: CONNECTORS-407 > URL: https://issues.apache.org/jira/browse/CONNECTORS-407 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.5 > > > The ant build does not make the .sh scripts executable, making for a lot of > work for Linux users. -- 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
[jira] [Created] (CONNECTORS-407) Ant build does not leave shell scripts with executable bits set for Linux
Ant build does not leave shell scripts with executable bits set for Linux - Key: CONNECTORS-407 URL: https://issues.apache.org/jira/browse/CONNECTORS-407 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Minor Fix For: ManifoldCF 0.5 The ant build does not make the .sh scripts executable, making for a lot of work for Linux users. -- 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
[jira] [Commented] (CONNECTORS-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206458#comment-13206458 ] Karl Wright commented on CONNECTORS-288: Committed latest patch. > 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, > 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
[jira] [Updated] (CONNECTORS-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Stancapiano updated CONNECTORS-288: Attachment: manifold-elasticsearch-patch yes, you say right.. now I updated and I add a better indentation too > 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, > 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
[jira] [Commented] (CONNECTORS-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206456#comment-13206456 ] Karl Wright commented on CONNECTORS-288: Could you do an svn update and then resubmit the latest patch? I'm getting conflicts; it looks like you haven't updated. > 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, 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
[jira] [Commented] (CONNECTORS-406) Some projects don't use the MultiThreadedHttpConnectionManager
[ https://issues.apache.org/jira/browse/CONNECTORS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206452#comment-13206452 ] Karl Wright commented on CONNECTORS-406: The pull-agent tests are not a problem since they do not need to perform under load. Scripting engine, though, should be worked on, as should the opensearch connector. > Some projects don't use the MultiThreadedHttpConnectionManager > -- > > Key: CONNECTORS-406 > URL: https://issues.apache.org/jira/browse/CONNECTORS-406 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process, OpenSearchServer connector, > Scripting client >Affects Versions: ManifoldCF 0.5 >Reporter: Luca Stancapiano > > I signal three projects not using the http multithread manager: > mcf-opensearch-connector > pull-agent (tests) > scripting-engine -- 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
[jira] [Updated] (CONNECTORS-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Stancapiano updated CONNECTORS-288: Attachment: manifold-elasticsearch-patch about tests I think it's a good start point. In this new patch I release two new update: 1 - Indent 2 - enable the HTTP connection pooling > 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, 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
[jira] [Created] (CONNECTORS-406) Some projects don't use the MultiThreadedHttpConnectionManager
Some projects don't use the MultiThreadedHttpConnectionManager -- Key: CONNECTORS-406 URL: https://issues.apache.org/jira/browse/CONNECTORS-406 Project: ManifoldCF Issue Type: Improvement Components: Framework agents process, OpenSearchServer connector, Scripting client Affects Versions: ManifoldCF 0.5 Reporter: Luca Stancapiano I signal three projects not using the http multithread manager: mcf-opensearch-connector pull-agent (tests) scripting-engine -- 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
[jira] [Issue Comment Edited] (CONNECTORS-288) An ElasticSearch connector would be helpful
[
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/12/12 2:36 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 :)
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?
was (Author: piergiorgioluc...@gmail.com):
{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 :)
> 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,
> 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
[jira] [Commented] (CONNECTORS-288) An ElasticSearch connector would be helpful
[
https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206413#comment-13206413
]
Piergiorgio Lucidi commented on CONNECTORS-288:
---
{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 :)
> 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,
> 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
[jira] [Commented] (CONNECTORS-347) MySQL HopCount test sometimes fails
[
https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206402#comment-13206402
]
Karl Wright commented on CONNECTORS-347:
I've seen this only once so far during normal test execution. That's too
infrequent to diagnose the problem. Running the test in a spinner might be the
only way to make it happen enough to catch.
> MySQL HopCount test sometimes fails
> ---
>
> Key: CONNECTORS-347
> URL: https://issues.apache.org/jira/browse/CONNECTORS-347
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
>Affects Versions: ManifoldCF 0.5
>Reporter: Karl Wright
>Assignee: Karl Wright
> Fix For: ManifoldCF 0.5
>
>
> The HopcountMySQLIT test sometimes fails complaining that it is expecting to
> see 6 documents but only sees 4.
> {code}
> [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong
> number of documents processed - expected 6, saw 4
> [junit] at
> org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152)
> {code}
> This does not happen on every run.
--
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
