Need to come up with a strategy for dealing with soft dependencies between 
packages
-----------------------------------------------------------------------------------

                 Key: BIGTOP-101
                 URL: https://issues.apache.org/jira/browse/BIGTOP-101
             Project: Bigtop
          Issue Type: New Feature
          Components: General
    Affects Versions: 0.1.0
            Reporter: Roman Shaposhnik
            Assignee: Roman Shaposhnik
             Fix For: 0.3.0


Quite a few components in Bigtop have, what's known as, soft dependency. They 
detect presence of other Bigtop components during run-time and extend their 
functionality accordingly. A good example of that is Pig, which, if HBase 
client jars are present would allow HBase queries to be performed. We have to 
come up with the best client delivery strategy for such things. One option is 
to split things like HBase into multiple packages, like lib, client, and server 
- but that requires upstream changes as well to split the jars up. Another 
approach is to have subpackages (e.g. hbase-hive subpackage or hbase-pig, etc.) 
We have to come up with a unifying strategy for how to deal with this.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to