Imho it's probably worth it. I feel we should focus on keeping the features we build as lightweight and efficient as possible. Let's leave possible future expansion for an issue we table later. As long as we're smart and build simple intuitive interfaces, it shouldn't be difficult to expand to new implementations as they become necessary. .
On Thursday, February 19, 2015, Dave <[email protected]> wrote: > On Thu, Feb 19, 2015 at 2:12 PM, Todd Nine <[email protected] > <javascript:;>> wrote: > > > Is there any way to remove jclouds and just use the lighter weight s3 > api? > > We've only really designed this to be used with S3. Maybe we should just > do > > that and leave the abstraction of outer cloud providers to be a future > > implementation. > > > > We could do that, but we use JClouds in a dozen or so places (all for S3), > so it would take some time. > > - Dave > > > > > > > On Thu, Feb 19, 2015 at 8:23 AM Dave <[email protected] <javascript:;>> > wrote: > > > > > On Thu, Feb 19, 2015 at 11:06 AM, Todd Nine <[email protected] > <javascript:;>> wrote: > > > > > > > Hmm, > > > > Guava 15 is the path of least resistance and will most likely be fine > > > IMHO. > > > > Is there a version between 15 and 18 that is more up to date but api > > > > compatible we can use? > > > > > > > > > > Thanks Todd. > > > > > > I'm not sure why we did not hit this problem before we moved to Guava > 18. > > > The error messages point to the method makeComputingMap, which was made > > > private in Guava 15: > > > > > > "tried to access method > > > com.google.common.collect.MapMaker.makeComputingMap( > > > Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap;" > > > > > > See also, https://github.com/google/guice/issues/846 > > > > > > I'm going to continue to experiment. > > > > > > - Dave > > > > > > > > > > > > > > > > > > > > On Thu, Feb 19, 2015 at 7:52 AM Dave <[email protected] > <javascript:;>> wrote: > > > > > > > > > I'm trying to debug problems in the new Arquillian-based REST tests > > in > > > > the > > > > > USERGRID-273 [1] branch. > > > > > > > > > > > > > > > I believe the tests are failing there because we upgraded to Guava > 18 > > > and > > > > > Guice 4-beta5 (the only version of Guice that will work with Guava > > 18). > > > > > Unfortunately, that completely breaks JClouds because the latest > > > version > > > > of > > > > > JClouds will not work with Guice 4-beta5. > > > > > > > > > > > > > > > So we have some options: > > > > > > > > > > > > > > > 1) Move back to a version of Guava before 15 until JClouds > releases a > > > > > version that will work with Guice 4. This should be easy to do, but > > > there > > > > > is a bug in the older Guava that may be causing us problems (I'm > not > > > 100% > > > > > certain about this). > > > > > > > > > > > > > > > 2) Remove JClouds from Usergrid and use AWS Java SDK directly. This > > is > > > > > probably a week of work at a minimum. JClouds is nice, but we only > > use > > > it > > > > > for S3 access and it brings in a boat-load of dependencies. > > > > > > > > > > > > > > > Thoughts? Other options? > > > > > > > > > > > > > > > - Dave > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/USERGRID-273 and > > > > > > > > > > https://github.com/apache/incubator-usergrid/tree/USERGRID-273 > > > > > > > > > > > > > > >
