Re: Telco HBase POC

2016-01-28 Thread Vijay Vangapandu
die [mailto:willem.conra...@pbtgroup.co.za] Sent: Wednesday, January 20, 2016 8:31 AM To: jamestay...@apache.org<mailto:jamestay...@apache.org> Cc: user@phoenix.apache.org<mailto:user@phoenix.apache.org> Subject: RE: Telco HBase POC Hi James, Thanks for being willing to assist. This is what the in

Re: Telco HBase POC

2016-01-20 Thread Vijay Vangapandu
To: jamestay...@apache.org<mailto:jamestay...@apache.org> Cc: user@phoenix.apache.org<mailto:user@phoenix.apache.org> Subject: RE: Telco HBase POC Hi James, Thanks for being willing to assist. This is what the input data record will look like (test data) : UserID DateTime TXNID DeviceI

RE: Telco HBase POC

2016-01-20 Thread Willem Conradie
range. Regards, Willem From: James Taylor [mailto:jamestay...@apache.org] Sent: 19 January 2016 10:07 PM To: user <user@phoenix.apache.org> Subject: Re: Telco HBase POC Hi Willem, Let us know how we can help as you start getting into this, in particular with your schema design based o

RE: Telco HBase POC

2016-01-20 Thread Riesland, Zack
: Wednesday, January 20, 2016 8:31 AM To: jamestay...@apache.org Cc: user@phoenix.apache.org Subject: RE: Telco HBase POC Hi James, Thanks for being willing to assist. This is what the input data record will look like (test data) : UserID DateTime TXNID DeviceID IPAddress UsageArray URIArray

Re: Telco HBase POC

2016-01-19 Thread James Taylor
like hash on userid. >> 6. Define TTL to purge data periodically >> >> >> >> >> >> Regards, >> >> Willem >> >> >> >> *From:* Pariksheet Barapatre [mailto:pbarapa...@gmail.com] >> *Sent:* 15 January 2016 03:17 PM >>

RE: Telco HBase POC

2016-01-18 Thread Willem Conradie
. 6. Define TTL to purge data periodically Regards, Willem From: Pariksheet Barapatre [mailto:pbarapa...@gmail.com] Sent: 15 January 2016 03:17 PM To: user@phoenix.apache.org Subject: Re: Telco HBase POC Hi Willem, Looking at your use case. Phoenix would be a handy client. Few notes from my

RE: Telco HBase POC

2016-01-18 Thread Willem Conradie
Thanks for the prompt reply. From: Pedro Gandola [mailto:pedro.gand...@gmail.com] Sent: 15 January 2016 02:19 PM To: user@phoenix.apache.org Subject: Re: Telco HBase POC Hi Willem, Just to give you my short experience as phoenix user. I'm using Phoenix4.4 on top of a HBase cluster where I keep

RE: Telco HBase POC

2016-01-18 Thread Pariksheet Barapatre
t; Willem > > > > *From:* Pariksheet Barapatre [mailto:pbarapa...@gmail.com] > *Sent:* 15 January 2016 03:17 PM > *To:* user@phoenix.apache.org > *Subject:* Re: Telco HBase POC > > > > Hi Willem, > > Looking at your use case. Phoenix would be a handy client. > > Few

Re: Telco HBase POC

2016-01-15 Thread Pedro Gandola
Hi Willem, Just to give you my short experience as phoenix user. I'm using Phoenix4.4 on top of a HBase cluster where I keep 3 billion entries. In our use case Phoenix is doing very well and it saved a lot of code complexity and time. If you guys have already decided that HBase is the way to go

Re: Telco HBase POC

2016-01-15 Thread Pariksheet Barapatre
Hi Willem, Looking at your use case. Phoenix would be a handy client. Few notes from my experience : 1. Use bulk load rather than psql.py. Load larger files(merge) instead of small files. 2. Increase HBase block cache 3. Turn off HBase auto compaction 4. Select primary key correctly 5. Don't use

Telco HBase POC

2016-01-15 Thread Willem Conradie
Hi, I am currently consulting at a client with the following requirements. They want to make available detailed data usage CDRs for customers to verify their data usage against the websites that they visited. In short this can be seen as an itemised bill for data usage. The data is