I wonder if the nature of the proposal should be to hide the complexity of raw
hbase options and provide a better semantic specifications for the
HBASE_OPTIONS clause.
>From
>http://archive.cloudera.com/cdh5/cdh/5/hbase-0.98.6-cdh5.2.4/book/compression.html,
> there is a good set of rules for
t;
> Eric
>
> *From:* Eric Owhadi [mailto:eric.owh...@esgyn.com]
> *Sent:* Tuesday, September 20, 2016 12:10 AM
> *To:* '乔彦克' <qya...@gmail.com>; 'user@trafodion.incubator.apache.org' <
> user@trafodion.incubator.apache.org>
> *Cc:* 'dev' <d...@trafodion.incubator.apache.org>
, so I only use the
> hbase compression.
>
> Qifan Chen <qifan.c...@esgyn.com>于2016年9月12日周一 下午10:43写道:
>
>> Hi Qiao,
>>
>> You can also send us the DDL and the query plan to help with the tuning.
>>
>> To generate a query plan, do the following from s
Hi Qiao,
You can also send us the DDL and the query plan to help with the tuning.
To generate a query plan, do the following from sqlci, and the plan is in
text file mylog.
1. log mylog clear;
2. prepare xx from ;
3. explain xx;
4. explain options 'f' xx;
5. exit;
Thanks
The implementation probably will be involving the following:
1. add a new type for column TEXT_TYPE in meta-table
TRAFODION."_MD_".TEXT, say COMMENT_TYPE;
2. allow COMMENT ON syntax in the parser;
3. convert the content of COMMENT ON stmt into insertion/update of a
row(s) in the
The scan optimizer picks the MDAM scan or subset scan based on the *cost*.
For MDAm to win, the low UEC on the leading key columns is a
pre-condition.
Thanks --Qifan
On Mon, Mar 28, 2016 at 10:23 AM, Rohit wrote:
> And remember, the key available for MDAM in a secondary
I agree omitting default values from storage is an optimization and as such it
should provide the same UPSERT semantics as with other storage
formats/optimizations.
Specially our code could insert default value checking expression to verify
that an value is exact the same as the default value
+1 for 13.
On Thu, Feb 18, 2016 at 8:34 PM, Trina Krug wrote:
> +1 for 13
>
> Trina
>
> On Feb 18, 2016, at 6:01 PM, Roberta Marton
> wrote:
>
> There has been quite a lot of discussion on our user list regarding the
> proposed Apache Trafodion
ache.org
> *Cc:* Rohit Jain <rohit.j...@esgyn.com>; Gunnar Tapper <
> tapper.gun...@gmail.com>
> *Subject:* RE: Logo Proposal
>
>
>
> It seems we might need multiple votes:
>
> - One color or multiple colors?
>
> - Thin font or thick f
I wonder if we could also consider a mod to option 4 where only the dragon
and the word trafodion are present. See the two images attached.
I sampled a couple apache project logs and found they do not have the word
APACHE in their logos (e.g., HIVE, MONGODB, AVRO, SPARK).
With this approach, it
10 matches
Mail list logo