[
https://issues.apache.org/jira/browse/CONNECTORS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874000#action_12874000
]
Karl Wright commented on CONNECTORS-37:
---------------------------------------
Which comes first, chicken or egg? The current properties file specifies quite
a bit of stuff about database implementation and access, so obviously that
can't go into the database. Also, the pointer to the logging configuration
file, and any other file pointers, probably should stay out of the database,
since these tend to be local instance configuration rather than global
configuration. While I'm sure that there are still *some* configuration
parameters that are legitimately global in nature, most of the serious
configuration (like connections, authorities, jobs, etc.) are already in the
database.
So maybe this ticket should read, "... excluding all global configuration
information, which should be moved to a database table..."
The driver behind this ticket, FWIW, is a complaint that configuring LCF
requires repeated user interaction with the database - and that user prefers
solr-style XML config files instead. I don't necessarily buy that view, but
using XML instead of name/value pairs seemed like a wise precaution. ;-)
> LCF should use an XML configuration file, not the simple name/value config
> file it currently has
> ------------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-37
> URL: https://issues.apache.org/jira/browse/CONNECTORS-37
> Project: Lucene Connector Framework
> Issue Type: Improvement
> Components: Framework core
> Reporter: Karl Wright
>
> LCF's configuration file is limited in what it can specify, and XML
> configuration files seem to offer more flexibility and are the modern norm.
> Before backwards compatibility becomes an issue, it may therefore be worth
> converting the property file reader to use XML rather than name/value format.
> It would also be nice to be able to fold the logging configuration into the
> same file, if this seems possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
