[jira] Commented: (CONNECTORS-37) LCF should use an XML configuration file, not the simple name/value config file it currently has
[ https://issues.apache.org/jira/browse/CONNECTORS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12873987#action_12873987 ] Erik Hatcher commented on CONNECTORS-37: my opinion - XML doesn't really add any value over a .properties file. but it is the enterprise Java way so to speak, so no objections. but since a database is involved, why not put the configuration entirely in the database? (except of course the pointer to the DB in the first place). regarding logging - it should be separate. if the goal is to stay in line with Solr's way, logging should be converted over to SLF4J so that the actual logging implementation can be pluggable, which can be handy in many environments were logging needs to be centralized across disparate apps. 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.
[jira] Commented: (CONNECTORS-37) LCF should use an XML configuration file, not the simple name/value config file it currently has
[ https://issues.apache.org/jira/browse/CONNECTORS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
[jira] Commented: (CONNECTORS-37) LCF should use an XML configuration file, not the simple name/value config file it currently has
[ https://issues.apache.org/jira/browse/CONNECTORS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874029#action_12874029 ] Jack Krupansky commented on CONNECTORS-37: -- I'll defer to the community on the logging issue, other than to simply say that it should be as standard as possible and relatively compatible with how Solr does logging so that it will not surprise people. I don't have a problem with the LCF .properties file per se, other than the fact that since it is restricted to being strictly keyword/value pairs it cannot contain more complex, structured configuration information. The main thing I'd like to see is that the current executecommand configuration setup, such as which output connectors and crawlers to register, be done using descriptions in a config file rather than discrete shell commands to manually execute. The default config file from svn checkout should have a default set of connectors, crawlers, etc., and have commented-out entries for other connectors that people can un-comment and edit as desired. A key advantage of having such a config file is that when people do report problems here we can ask them to provide their config file rather than ask them to try to remember and re-type whatever commands they might remember that they intended to type. Whether connections and jobs can be initially created from a config file is a larger discussion. The main point here is simply that it be easy to get LCF initialized and configured for the really basic stuff needed for a typical initial evaluation (comparable to what occurs in a Solr tutorial.) The proverbial zero-hour experience. 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.
[jira] Commented: (CONNECTORS-37) LCF should use an XML configuration file, not the simple name/value config file it currently has
[ https://issues.apache.org/jira/browse/CONNECTORS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874035#action_12874035 ] Karl Wright commented on CONNECTORS-37: --- I am not happy with the idea of configuration living in both the database and in an XML file. The idea that you can somehow read the XML configuration just once the first time LCF is started seems rife with potential problems. Far from improving the user experience, I think that the proposed design would instead create enormous confusion. Perhaps the problem is that Mr. Krupansky is attempting to do too much with a single configuration file here. It would be perfectly reasonable to introduce a read setup information command that would read what is effectively a sequence of commands from an XML file. However, that command file would be an execute once kind of affair - although it could be coded in such a way as to ignore the definition of entities that already exist in the database. Nevertheless, such a file would have a very different usage pattern than the configuration file as it exists today, so I'd have a lot of concern using the same configuration file for both purposes. 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.
