[jira] Commented: (CONNECTORS-61) Support bundling of LCF with an app

2010-07-13 Thread Karl Wright (JIRA)

[ 
https://issues.apache.org/jira/browse/CONNECTORS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12887806#action_12887806
 ] 

Karl Wright commented on CONNECTORS-61:
---

I'm tempted to close this issue because (a) there is absolutely no reason 
anyone competent cannot bundle lcf with an app today, and (b) it is completely 
unclear what, if anything, the 'fix' would look like.  A specific statement of 
an actual concrete problem is the only thing that will prevent me from closing 
this.


--- original message ---
From: ext Jack Krupansky (JIRA) j...@apache.org
Subject: [jira] Created: (CONNECTORS-61) Support bundling of LCF with an app
Date: July 12, 2010
Time: 2:48:11  PM


Support bundling of LCF with an app
---

 Key: CONNECTORS-61
 URL: https://issues.apache.org/jira/browse/CONNECTORS-61
 Project: Lucene Connector Framework
  Issue Type: Sub-task
  Components: Framework core
Reporter: Jack Krupansky


It should be possible for an application developer to bundle LCF with an 
application to facilitate installation and deployment of the application in 
conjunction with LCF. This may (or may not) be as simple as providing 
appropriate jar files and documentation for how to use them, but there may be 
other components or scripts needed.

There are two options: 1) include the LCF UI along with the other LCF 
processes, and 2) exclude the LCF UI and include only the other processes that 
can be controlled via the full API.

The database server would be included.

The web app server would be optional since the application may have its own 
choice of web app server.

One use case is bundling LCF with Solr or a Solr-based application.

Note: This issue is part of Phase 2 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.




 Support bundling of LCF with an app
 ---

 Key: CONNECTORS-61
 URL: https://issues.apache.org/jira/browse/CONNECTORS-61
 Project: Lucene Connector Framework
  Issue Type: Sub-task
  Components: Framework core
Reporter: Jack Krupansky

 It should be possible for an application developer to bundle LCF with an 
 application to facilitate installation and deployment of the application in 
 conjunction with LCF. This may (or may not) be as simple as providing 
 appropriate jar files and documentation for how to use them, but there may be 
 other components or scripts needed.
 There are two options: 1) include the LCF UI along with the other LCF 
 processes, and 2) exclude the LCF UI and include only the other processes 
 that can be controlled via the full API.
 The database server would be included.
 The web app server would be optional since the application may have its own 
 choice of web app server.
 One use case is bundling LCF with Solr or a Solr-based application.
 Note: This issue is part of Phase 2 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.



[jira] Commented: (CONNECTORS-60) Agent process should be started automatically

2010-07-13 Thread Jack Krupansky (JIRA)

[ 
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

2010-07-13 Thread karl.wright
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: JSON license

2010-07-13 Thread Jack Krupansky
I'm no expert on licenses, so I would look at what Solr does and maybe ping 
Grant. Presumably LCF should have a legal subdirectory somewhere for 
license notices.


-- Jack Krupansky

--
From: karl.wri...@nokia.com
Sent: Tuesday, July 13, 2010 5:02 PM
To: jack.krupan...@lucidimagination.com
Cc: connectors-dev@incubator.apache.org
Subject: RE: JSON license

Can you clarify what is meant by add this license to /legal?  And what 
the update to NOTICES.TXT should look like?  Something like this?


Apache Lucene Connector Framework
Copyright 2010 The Apache Software Foundation

This product includes software developed by
The Apache Software Foundation (http://www.apache.org/).

Portions of the software are licensed as follows:

Copyright (c) 2002 JSON.org
Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation
files (the Software), to deal in the Software without restriction, 
including without limitation the rights to use, copy, modify,
merge, publish, distribute, sublicense, and/or sell copies of the 
Software, and to permit persons to whom the Software is furnished

to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

The Software shall be used for Good, not Evil.
THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND 
NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH 
THE SOFTWARE OR THE USE OR OTHER

DEALINGS IN THE SOFTWARE.



Karl





RE: [jira] Commented: (CONNECTORS-60) Agent process should be started automatically

2010-07-13 Thread karl.wright
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

2010-07-13 Thread Jack Krupansky
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

2010-07-13 Thread karl.wright


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.