-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My mistake, I forgot to mention, that issues 1 and 3 are fixed. Ad 2: Our use-case was to upsert null values and with Phoenix 3.0 from old master has some issue. So we've add multiupsert function (with deleting null values) to node lib[1]. We had lot of disscusions at our firm, but previous principal architect said it is by design, so we choose that way. But now everything is fine.
Regards, Vaclav; [1] https://github.com/alibaba/node-hbase-client/pull/74 On 01/08/2015 03:39 AM, James Taylor wrote: > Thanks for sharing your experiences,Vaclav. That's very valuable. > > Yes, for (1) bad things can happen if a region server doesn't have > the Phoenix jar. This was improved as of HBase 0.98.9 with > HBASE-12573 and HBASE-12575. For (3), this was fixed as of Phoenix > 3.1/4.1 with PHOENIX-1075. If you have a chance, would you mind > filing a JIRA for (2) with as much detail as you have? > > Thanks, James > > On Wed, Jan 7, 2015 at 12:39 PM, Vaclav Loffelmann > <vaclav.loffelm...@socialbakers.com> wrote: Hi, > > here's my 2 cents. We've had few serious issues before deploy on > production. > > 1) deploying new server without Phoenix jar - make sure you have > properly configured tool for automatic server maintaining 2) > inserting empty string (byte array) to Phoenix - cause to our use > case this has impact several hours later. 3) upgrading Phoenix - > There was bug with priorities when evaluating math expressions. > > We are using micro service architecture with node.js. There are few > libs we are participation at[1-4]. > > Our use-case is very simple: aggregate data (sum, avg, ..) on > region server side. We aggregate time series data as client demand > timerange. Phoenix is very use full on this, thanks to parallel > querying. > > There are of course easy way, how to add own functionality - > creating build in functions. There [5] is old post, how to do that > although fundamentals are still same. > > So there are one basic advice: Don't underestimate testing. > > [1] > https://github.com/falsecz/byter#support-for-hbase-phoenix-v-300-data-types > > [2] https://github.com/falsecz/node-phoenix-proxy > [3] https://github.com/falsecz/phoenix-proxy-server [4] > https://github.com/falsecz/node-hbase [5] > http://phoenix-hbase.blogspot.cz/2013/04/how-to-add-your-own-built-in-function.html > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUs5OgAAoJEG3mD8Wtuk0W1lcH/2g/1L0kCHGMCszubI3LpYLY Jn+r5DcUk0S83V0UyIs3LbWc2/RtlKfJc4ZZ1MtpdnZE5zhvtvQ8M40zHKn69mpY tXjUkqp67833wKLi5H+tPr+M2pc8EeQInEONDJhBK8YGjqHsNsqrO15nq2kcJBJF DC4ycCK0ZeqSLHmtLZqtAMKeWY06/kwkXRgZUgQaZ1IIKVfDBIvDU1KHIbeB3j+K dQNCKlgtHWXf57RYnysjztZXcFnpCeOa6mjucyLuxarMHO2qILZrk054DWbnRAtI yEixCH9PzXcuDizISoH44dWM9/WcQng4B0Jau9Hir16AOclCMARDHrKtt4iHQL8= =DZkQ -----END PGP SIGNATURE-----
