Hi, On Thu, Jul 18, 2013 at 3:12 PM, <[email protected]> wrote:
> Sorry for late reply. > Same here. I have been getting rammed in work right now so apologies for late reply to lists. > > Could we disable solr module for a while and release note it until we > resolve no 3 with HBase module? > This is certainly an option indeed. I would like to throw the cat in amongst the pigeons and propose the following in an attempt for us to reach consensus on a 0.4 roadmap... of sorts. * GORA-201 - Upgrade HBase API * GORA-72/257 OSGi/Classloading I am only throwing these two in right now as I think they are the most critical ones to address. I think it will give us a lot of flexibility if we can get the latter working as then it means modules can progress independently from a dependency POV. This is really important. When Renato was in town he was talking with some folks from another social network other than Facebook ;) which are having some Avro problems... The classloading and dependency management for us is an issue. One thought I've had on this though is that fundamentally everything needs to tie back in to core anyway... as we extend everything here... is it possible for us to decouple/extract away as much of our reliance upon external API's (such as Avro)? This would mean that core has less external dependencies? That being said, I think it would be nice for us to reach agreement on what needs to be fixed with the most urgency? I am happy to chip in on the HBase side when I get free time... but I do not wish to try this one alone as I'm going to be learning a pile of gear here. I will back a consensus. If the choice is to disable the Solr Module (temporarily adding HBase 0.90.4 compliant deps) then working on a branch for either issue... then I am happy to do this. Thanks Lewis https://issues.apache.org/jira/browse/GORA-201 https://issues.apache.org/jira/browse/GORA-257
