My suggestion would be to go with the compression that has shown to work for us from a stability and performance perspective. So, yes, we should go forward with SNAPPY and create that dependency. I don’t see why anyone would care what compression we used. If there is a motivation to change the compression, can we even articulate that? So, from ease of install, support, consistency of performance, etc. I think we should just go ahead and commit to SNAPPY.
Rohit From: Dave Birdsall [mailto:[email protected]] Sent: Wednesday, June 7, 2017 12:35 PM To: [email protected] Subject: RE: Make "HBase options" as default setting? One other point I’d make (or rather a question I would ask) is this: SNAPPY evidently is not installed on systems by default. If we make SNAPPY a default HBASE_OPTION, then Trafodion will not work out-of-the-box on all systems. Do we want to make snappy compression a required dependency for Trafodion? (It’s OK by me if we do; but we should make this decision intentionally not as an accidental byproduct of a default choice.) Dave From: Carol Pearson [mailto:[email protected]] Sent: Wednesday, June 7, 2017 10:14 AM To: [email protected]<mailto:[email protected]> Subject: Re: Make "HBase options" as default setting? I think we need to optimize for end users, not necessarily easier for development environments. End users the ones for whom we need to make things easy so that their initial experience doesn't include a bunch of extra switches to get reasonable performance. So I'm +1 on the original suggestion as well. I think that if it's an issue for dev environments, we add it to a trafodion developers environment customization script that developers can run as needed. But that's a discussion for the dev list, not user. -Carol P. --------------------------------------------------------------- Email: [email protected]<mailto:[email protected]> Twitter: @CarolP222 --------------------------------------------------------------- On Wed, Jun 7, 2017 at 9:51 AM, Rohit Jain <[email protected]<mailto:[email protected]>> wrote: I am suggesting that we change the default settings to those as proposed so that all tables use those settings by default. So, it is a +1. A CQD might be used to override the default. This, hopefully will be rare. I just think that having entries in a system DEFAULTS table are problematic for the reasons I mentioned. Of course, they would be in the compiler’s default settings. Rohit From: Dave Birdsall [mailto:[email protected]<mailto:[email protected]>] Sent: Wednesday, June 7, 2017 11:28 AM To: [email protected]<mailto:[email protected]> Subject: RE: Make "HBase options" as default setting? So, would this make you a -1 on the original suggestion? (that is, just changing the HBASE_OPTIONS defaults?) From: Rohit Jain [mailto:[email protected]] Sent: Wednesday, June 7, 2017 9:16 AM To: [email protected]<mailto:[email protected]> Subject: RE: Make "HBase options" as default setting? Dave, CQDs indicate that we might make a different decision on these for certain customers. If that is not the case, then we are just increasing the complexity of configuring a system with the right default defaults, etc. and opening ourselves us for the possibility that something may go wrong. Often times, folks are not even aware as to what is set in the DEFAULTS table and are puzzled by the behavior, sometimes because someone added something to that table or changed the setting and forgot to set it back, etc. Then you have to document these CQDs, when to change them, etc. So, while the flexibility of having sooooo many buttons may be a good thing to cover all possible theoretical combinations one might come up with, from a practical standpoint the KISS (Keep It Simple Stupid) principal trumps all. Rohit From: Dave Birdsall [mailto:[email protected]] Sent: Wednesday, June 7, 2017 10:44 AM To: [email protected]<mailto:[email protected]> Subject: RE: Make "HBase options" as default setting? What might make sense is to add a CQD (or maybe a set of them) with default values for certain HBASE_OPTIONS settings. Then one could put these CQDs in the system DEFAULTS table. So, you’d set it once in a cluster installation and then not have to worry about it afterwards. From: Dave Birdsall Sent: Wednesday, June 7, 2017 8:26 AM To: [email protected]<mailto:[email protected]> Subject: RE: Make "HBase options" as default setting? -1 Snappy is often not installed on workstations, so I would not want to make that the default. From: Eric Owhadi [mailto:[email protected]] Sent: Wednesday, June 7, 2017 4:52 AM To: [email protected]<mailto:[email protected]> Subject: Re: Make "HBase options" as default setting? +1 Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: "Liu, Yuan (Yuan)" <[email protected]<mailto:[email protected]>> Date: 6/6/17 10:29 PM (GMT-06:00) To: [email protected]<mailto:[email protected]> Subject: Make "HBase options" as default setting? Hi Trafodioners, As we know, for performance thinking, we always need to add below syntax in “create table” syntax. And I know in latest version, we have made “ATTRIBUTES ALIGNED FORMAT” as default, do we have a plan that make HBASE_OPTIONS(including ENCODING、COMPRESSION、MEMESTORE) as the default setting when creating table? I think this will be easier for new users? ATTRIBUTES ALIGNED FORMAT HBASE_OPTIONS ( DATA_BLOCK_ENCODING = 'FAST_DIFF', COMPRESSION = 'SNAPPY', MEMSTORE_FLUSH_SIZE = '1073741824' ) ; Best regards, Yuan Email: [email protected]<mailto:[email protected]> Cellphone: (+86) 13671935540<tel:+86%20136%207193%205540>
