Josh, Thanks a lot for sharing your notes on your JDBI usage. We are also looking to adopt JDBI within dropwizard as a layer wrapped around Phoenix. Will be happy to share any notes/experiences in the future.
Thanks, Anirudha On Mon, Mar 23, 2015 at 7:49 PM, Josh Mahonin <[email protected]> wrote: > Hi Anirudha, > > We're presently using Phoenix with the Dropwizard framework, using JDBI: > https://dropwizard.github.io/dropwizard/manual/jdbi.html > > As well, I did a small trial run with the Play 2 Framework using both > Anorm and Ebean, which were successful. We ended up choosing Dropwizard > instead though. > https://www.playframework.com/documentation/2.3.x/ScalaAnorm > https://www.playframework.com/documentation/2.3.x/JavaEbean > > If I recall correctly, most things just work out of the box. Depending on > the framework, you'll need to have a way to force the UPSERT syntax vs. > UPDATE. If you end up going with JDBI, I believe we had to override a > 'validation query' setting, as well as an 'auto commit' setting in the > Dropwizard DB configuration. > > Best, > > Josh > > On Thu, Mar 19, 2015 at 10:00 AM, Anirudha Khanna < > [email protected]> wrote: > >> Hi Thomas, >> >> Thanks for your response. We are looking to store our relational data in >> HBase through Phoenix. With this respect we are evaluating whether to use a >> framework like JPA or to go native SQL, using a lib like jdbi or jooq, for >> doing the serdes from the data store. Was curious if anyone in the >> community had a similar use case and how they are solving this problem. >> >> Cheers, >> Anirudha >> >> On Thu, Mar 19, 2015 at 1:39 AM, Thomas D'Silva <[email protected]> >> wrote: >> >>> Anirudha >>> >>> At Salesforce, one of the use cases Phoenix and HBase is used for is >>> storing immutable event data such as login information. We periodically run >>> aggregate queries to generate metrics eg. number of logins per user. We >>> select the columns of the primary key based on the filters used while >>> querying data. Our objects don't have multi-level parent child >>> relationships. >>> Do you have any specific information you are looking for? >>> >>> -Thomas >>> >>> On Wed, Mar 18, 2015 at 11:28 AM, Anirudha Khanna < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> We are evaluating using Phoenix over HBase for persisting relational >>>> data. Has anyone tried doing something similar? Any experience reports >>>> would be really helpful. >>>> Quick note, some of our objects have upto 3 - 4 levels of parent - >>>> child relations. >>>> >>>> Cheers, >>>> Anirudha >>>> >>> >>> >> >
