[jira] [Commented] (CONNECTORS-60) Agent process should be started automatically
[ https://issues.apache.org/jira/browse/CONNECTORS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084067#comment-13084067 ] Karl Wright commented on CONNECTORS-60: --- The Quick Start definitely meets the requirements listed for this task, so I'm closing it. Agent process should be started automatically - Key: CONNECTORS-60 URL: https://issues.apache.org/jira/browse/CONNECTORS-60 Project: ManifoldCF Issue Type: Sub-task Components: Documentation Reporter: Jack Krupansky Priority: Minor Fix For: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 LCF as it exists today is a bit too complex to run for an average user, especially with a separate agent process for crawling. LCF should be as easy to run as Solr is today. QuickStart is a good move in this direction, but the same user-visible simplicity is needed for full LCF. The separate agent process is a reasonable design for execution, but a little too cumbersome for the average user to manage. Unfortunately, it is expected that starting up a multi-process application will require platform-specific scripting. Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. KDW - this functionality is already present; however the documentation is not adequate to help people figure out how to do it. So I'm moving this to Documentation and treating it as a doc bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONNECTORS-60) Agent process should be started automatically
[ https://issues.apache.org/jira/browse/CONNECTORS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888000#action_12888000 ] Jack Krupansky commented on CONNECTORS-60: -- Unless I am mistaken, the jetty integration is for QuickStart (single process) only. The issue is for non-QuickStart, multi-process execution. Agent process should be started automatically - Key: CONNECTORS-60 URL: https://issues.apache.org/jira/browse/CONNECTORS-60 Project: Lucene Connector Framework Issue Type: Sub-task Reporter: Jack Krupansky LCF as it exists today is a bit too complex to run for an average user, especially with a separate agent process for crawling. LCF should be as easy to run as Solr is today. QuickStart is a good move in this direction, but the same user-visible simplicity is needed for full LCF. The separate agent process is a reasonable design for execution, but a little too cumbersome for the average user to manage. Unfortunately, it is expected that starting up a multi-process application will require platform-specific scripting. Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (CONNECTORS-60) Agent process should be started automatically
Let me get this straight. There is a way you can deploy LCF that does everything you are currently asking for. But you are not willing to use it. Why? Karl -Original Message- From: ext Jack Krupansky (JIRA) [mailto:j...@apache.org] Sent: Tuesday, July 13, 2010 4:48 PM To: connectors-dev@incubator.apache.org Subject: [jira] Commented: (CONNECTORS-60) Agent process should be started automatically [ https://issues.apache.org/jira/browse/CONNECTORS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888000#action_12888000 ] Jack Krupansky commented on CONNECTORS-60: -- Unless I am mistaken, the jetty integration is for QuickStart (single process) only. The issue is for non-QuickStart, multi-process execution. Agent process should be started automatically - Key: CONNECTORS-60 URL: https://issues.apache.org/jira/browse/CONNECTORS-60 Project: Lucene Connector Framework Issue Type: Sub-task Reporter: Jack Krupansky LCF as it exists today is a bit too complex to run for an average user, especially with a separate agent process for crawling. LCF should be as easy to run as Solr is today. QuickStart is a good move in this direction, but the same user-visible simplicity is needed for full LCF. The separate agent process is a reasonable design for execution, but a little too cumbersome for the average user to manage. Unfortunately, it is expected that starting up a multi-process application will require platform-specific scripting. Note: This issue is part of Phase 1 of the CONNECTORS-50 umbrella issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (CONNECTORS-60) Agent process should be started automatically
So all you want to see is a postgresql version of QuickStart? That's actually trivial - it's a one-line modification to the properties.xml file. My suggestion is to simply address this with documentation.
Re: [jira] Commented: (CONNECTORS-60) Agent process should be started automatically
That would help. Keep in mind the Jira issue for bundling the database server as well. I was assuming that there was still some technical advantage to running LCF in the non-QuickStart multi-process configuration. -- Jack Krupansky -- From: karl.wri...@nokia.com Sent: Tuesday, July 13, 2010 5:09 PM To: connectors-dev@incubator.apache.org Subject: RE: [jira] Commented: (CONNECTORS-60) Agent process should be started automatically So all you want to see is a postgresql version of QuickStart? That's actually trivial - it's a one-line modification to the properties.xml file. My suggestion is to simply address this with documentation.
RE: [jira] Commented: (CONNECTORS-60) Agent process should be started automatically
That would help. Keep in mind the Jira issue for bundling the database server as well. I have neither the time nor the inclination to tackle the postgresql bundling proposal. You are on your own there. If you believe that LCF 1.0 cannot be released without such a canned installation procedure, then it is very likely your schedule will be disrupted. There is an existing ticket for writing installers - if you want to proceed on that I suggest that you attach your installer(s) as patches to that ticket, and take care of the postgresql bundling you desire at the same time. Good luck! I was assuming that there was still some technical advantage to running LCF in the non-QuickStart multi-process configuration. Multiprocess execution models are preferred by most Unix folks, because everything in Unix is done at a process level - security management, primarily, would be the important thing. In the future, when LCF has been Zookeeper'd, it will be very important to allow a multi-process model. But for the kinds of people you seem to be worrying about, a single process will do very nicely.
