Inline.

On Tue, Jan 6, 2015 at 11:54 PM, Justin Workman <justinjwork...@gmail.com>
wrote:

> I am also using Phoenix in production and have been now for roughly 6
> months. We adopted Phoenix for most of the same reasons Anil mentions.
>
> We are connection to a secure cluster without issue. We have also
> implemented our own storm persistence bolt, and a lookup bolt that are
> reading and writing to our Phoenix/Hbase cluster.
>
> I have still had problems getting a secure connection from client tools
> for adhoc analysis other than sqlline. Still fighting though connections
> from SquirrelSQL, although I haven't dedicated a whole lot of time trying
> to figure it out.
>
Anil: We were successfully able to connect to secure HBase cluster via
SquirellSQL. What version of Phoenix you were using? What steps you follow
to connect to secure cluster? Can you share the error message?

>
> Thanks
> Justin
>
> Sent from my iPhone
>
> On Jan 7, 2015, at 12:26 AM, Siddharth Ubale <siddharth.ub...@syncoms.com>
> wrote:
>
>  Hi Anil,
>
>
>
> Thanks a lot for sharing ur thoughts.
>
> Have you tried using Phoenix API along with Apache Storm?
>
> There is a storm RDBMS connector implementation , but it was last updated
> in 2012 and I am having problems with it.
>
> Any thoughts on Storm-Phoenix integration?
>
>
>
> Thanks,
>
> Siddharth ubale
>
>
>
> *From:* anil gupta [mailto:anilgupt...@gmail.com <anilgupt...@gmail.com>]
> *Sent:* Wednesday, January 07, 2015 12:49 PM
> *To:* user@phoenix.apache.org
> *Cc:* James Taylor
> *Subject:* Re: Phoenix in production
>
>
>
> Hi Siddharth,
>
> I have used Phoenix in production for more than a year at Intuit.(i no
> longer work there.) I was pretty happy with Phoenix because it provided us
> capability to use sql-like(JDBC compliant) querying on a NoSql DB. With
> help of Phoenix, the adoption rate of HBase in my team was much more faster
> and it makes it very easy to read data from HBase Table.(without Phoenix, i
> personally used to write java programs for queries with complex filters.or
> non-string columns).
>
> Following are the some of the challenges i faced while using Phoenix:
>
> 1. Connecting to secure HBase cluster.
>
> 2. Phoenix creating big files under /tmp folder when a "select *" type
> query is done.
>
> 3. Phoenix only used to work with SQuirreL(GUI based DB client)
> <http://squirrel-sql.sourceforge.net/>
>
> I know for sure that #1 and #3 are addressed. There was jira for #2, i m
> not sure whats the status of it right now.
>
> Obviously,i haven't used all the features of Phoenix. So, i would suggest
> you to do your own evaluation(POC) and take guidance from the Phoenix
> community if you are planning to use any specific feature. This community
> is quite active.
>
>
>
> Hope This Helps,
>
> Anil Gupta
>
>
>
>
>
> On Thu, Jan 1, 2015 at 11:21 PM, Siddharth Ubale <
> siddharth.ub...@syncoms.com> wrote:
>
>  Hi Guys,
>
>
>
> We are seriously thinking of phoenix in Production environment , however,
> we have no much data of how Phoenix is behaving in production.
>
> Can anyone let us know if anyone is using Phoenix in Production and any
> challenges which they have experienced.
>
>
>
> Thanks,
>
> Siddharth Ubale,
>
> *Synchronized Communications *
>
> *#43, Velankani Tech Park, Block No. II, *
>
> *3rd Floor, Electronic City Phase I,*
>
> *Bangalore – 560 100*
>
> *Tel : +91 80 3202 4060 <%2B91%2080%203202%204060>*
>
> *Web:* *www.syncoms.com* <http://www.syncoms.com/>
>
> *<image001.jpg>*
>
> *London*|*Bangalore*|*Orlando*
>
>
>
> *we innovate, plan, execute, and transform the business​*
>
>
>
>
>
>
> --
>
> Thanks & Regards,
> Anil Gupta
>
>


-- 
Thanks & Regards,
Anil Gupta

Reply via email to