[
https://issues.apache.org/jira/browse/CONNECTORS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886715#action_12886715
]
Mark Miller commented on CONNECTORS-55:
---------------------------------------
bq. Jack, for example, was extremely surprised to learn that embedded Derby
would not allow more than one process to access the database at a time
You can switch to a mode that allows multiple connections - I've started with
one and moved to the other in the past - its been too long so I'd have to go
look, but its entirely possible to use very similar code and run in a server
mode.
bq. so that we could understand your true goal here.
To make trying out and installing LCF much easier - the bar on this thing as a
user and a dev is just kind of ridiculous at the moment. I know a lot of
improvements are being made, but having to install a separate postgres db just
to get going - just to try LCF out - is something I'd like to see go away. A
java db would allow us to get to a point where you download the thing and
launch it - that would really get this project going. It will be helpful to
attract both users and a community of devs. There are at least half a dozen or
more committers that signed up for this project, but the bar is so high to even
'do anything', that I suspect thats why most of them have yet to contribute
even a comment - they don't have the time or motivation to go through that huge
'running LCF' doc - its a bear just to skim, say nothing about go through the
steps. In general, I like to think of all that work as something the computer
can do for me ;)
Baby steps though - I'm just pushing in that direction - I know there would be
a long, long path to get there.
> Bundle database server with LCF packaged product
> ------------------------------------------------
>
> Key: CONNECTORS-55
> URL: https://issues.apache.org/jira/browse/CONNECTORS-55
> Project: Lucene Connector Framework
> Issue Type: Improvement
> Components: Framework core
> Reporter: Jack Krupansky
>
> The current requirement that the user install and deploy a PostgreSQL server
> complicates the installation and deployment of LCF for the user. Installation
> and deployment of LCF should be as simple as Solr itself. QuickStart is great
> for the low-end and basic evaluation, but a comparable level of simplified
> installation and deployment is still needed for full-blown, high-end
> environments that need the full performance of a ProstgreSQL-class database
> server. So, PostgreSQL should be bundled with the packaged release of LCF so
> that installation and deployment of LCF will automatically install and deploy
> a subset of the full PostgreSQL distribution that is sufficient for the needs
> of LCF. Starting LCF, with or without the LCF UI, should automatically start
> the database server. Shutting down LCF should also shutdown the database
> server process.
> A typical use case would be for a non-developer who is comfortable with Solr
> and simply wants to crawl documents from, for example, a SharePoint
> repository and feed them into Solr. QuickStart should work well for the low
> end or in the early stages of evaluation, but the user would prefer to
> evaluate "the real thing" with something resembling a production crawl of
> thousands of documents. Such a user might not be a hard-core developer or be
> comfortable fiddling with a lot of software components simply to do one
> conceptually simple operation.
> It should still be possible for the user to supply database server settings
> to override the defaults, but the LCF package should have all of the
> best-practice settings deemed appropriate for use with LCF.
> One downside is that installation and deployment will be platform-specific
> since there are multiple processes and PostgreSQL itself requires a
> platform-specific installation.
> This proposal presumes that PostgreSQL is the best option for the foreseeable
> future, but nothing here is intended to preclude support for other database
> servers in futures releases.
> This proposal should not have any impact on QuickStart packaging or
> deployment.
> 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.
