[ https://issues.apache.org/jira/browse/NUTCH-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142475#comment-13142475 ]
Ferdy Galema commented on NUTCH-1189: ------------------------------------- I see what you're getting at. We could indeed include this most important 'hbase.zookeeper.quorum' Configuration property within gora.properties. But I'm not fully sure how to implement it. We could: A) Explicitely read this specific property in HBaseStore and paste it onto Configuration. (Requires modification of HBaseStore) B) Make it flexible so that for example every property starting with 'hbaseconf.' will be pasted onto Configuration. (Requires modification of HBaseStore). C) Even more generic, make is so that EVERY store benefits from Configuration property overrides. (This could be done in either Nutch or Gora code). D) Just mention the fact in gora.properties. For now I feel that D is the best solution, because it requires the least modifications and fits perfectly within the scope of this issue. Also it keeps a strict separation between gora properties and Configuration properties. This will avoid any confusion. If you agree with me then you could just paste something along the lines of my previous comment into the properties file. > add commented out default settings to gora.properties files > ------------------------------------------------------------ > > Key: NUTCH-1189 > URL: https://issues.apache.org/jira/browse/NUTCH-1189 > Project: Nutch > Issue Type: Sub-task > Components: storage > Affects Versions: nutchgora > Reporter: Lewis John McGibbney > Assignee: Lewis John McGibbney > Fix For: nutchgora > > Attachments: NUTCH-1189.patch > > > This issues should have been dealt with as part of its parent issue, however > I think as it is a fairly lareg task in itself, it needs to be done > independently. The gora.properties file should, amongst other settings, and > beside the extreme basic defaults for sqlstore, include defaults for opening > HBase, Cassandra, etc servers on their default ports etc. Leaving this down > to individual interpretation puts a huge owness of the user, hence > constructing a barrier to entry for getting the configuration settings up and > running. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira