Mailing-List: contact connectors-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: connectors-dev@incubator.apache.org
Date: Sun, 4 Mar 2012 22:08:59 +0000 (UTC)
From: "Karl Wright (Commented) (JIRA)" <jira@apache.org>
To: connectors-dev@incubator.apache.org
Message-ID: 
 <932969175.20425.1330898939670.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <934270927.14536.1320851751688.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CONNECTORS-288) An ElasticSearch connector
 would be helpful
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karl Wright commented on CONNECTORS-288:
----------------------------------------

Luca,

The BaseITDerby class call to super.setUp() calls ConnectorBase.setUp(), which looks like this:

{code}
  @Before
  public void setUp()
    throws Exception
  {
    try
    {
      localCleanUp();
    }
    catch (Exception e)
    {
      System.out.println("Warning: Preclean failed: "+e.getMessage());
    }
    try
    {
      localSetUp();
    }
    catch (Exception e)
    {
      e.printStackTrace();
      throw e;
    }
  }
{code}

The localCleanup() call does the following:

{code}
  protected void localCleanUp()
    throws Exception
  {
    initialize();
    if (isInitialized())
    {
      ... remove connections, jobs, etc.
    }
  }
{code}

There is no code that calls mcfInstance.stop() in the localCleanUp() method.

It is true that the agents process is meant to only run ONCE in a JVM instance.  That means you can start it, then stop it, but you cannot start it again after that.  The reasons are historical and have to do with avoiding race conditions when more than one entity is trying to start the agents process at the same time.

This is one reason that we use fork="true" for both the Maven and Ant invocations of tests.  If we do not do this, the agents process will not start on the second and subsequent tests that are called, because the JVM instance is shared in that model across all test runs.


> 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