Hi,
I'm using a map-reduce job with HFileOutputFormat followed by bulk loads/merges
to create and populate a table with multiple column familes. I would like to
understand how compression works, and how to specify a non-default compression
in this setup. So:
AFAIK, there are two relevant s
://apache-hbase.679495.n3.nabble.com/Hbase-Compression-tp4051122.html
Sent from the HBase User mailing list archive at Nabble.com.
Hi Adam,
Answers inline below:
On Sat, Nov 20, 2010 at 7:14 AM, Adam Portley wrote:
>
> Hi,
> I'm using a map-reduce job with HFileOutputFormat followed by bulk
> loads/merges to create and populate a table with multiple column familes. I
> would like to understand how compression works, and h
hen it finally added, the size is 64.4m. Lastly, there are 2 more
> parameters which is 128.2m and 48.0m for currentsize.
>
> I never specify hbase.regionserver.codecs preperty in my hbase-site.xml
> file, so is the size difference still because of compression?
>
> Thanks,
>
&g
rty in my hbase-site.xml
> file, so is the size difference still because of compression?
>
> Thanks,
>
> aiyoh79
>
>
>
> --
> View this message in context:
> http://apache-hbase.679495.n3.nabble.com/Hbase-Compression-tp4051122.html
> Sent from the HBase User mailing list archive at Nabble.com.
>
added, the size is 64.4m. Lastly, there are 2 more
>> parameters which is 128.2m and 48.0m for currentsize.
>>
>> I never specify hbase.regionserver.codecs preperty in my hbase-site.xml
>> file, so is the size difference still because of compression?
>>
>> Thank
>> parameters which is 128.2m and 48.0m for currentsize.
>>
>> I never specify hbase.regionserver.codecs preperty in my hbase-site.xml
>> file, so is the size difference still because of compression?
>>
>> Thanks,
>>
>> aiyoh79
>>
>>
aster/hbase-compression/hbase-compression-xz).
We depend on version 1.9 of xz-java, which was published in 2021, well
before maintenance changes in the project and the involvement of a person
who is now believed to be a malicious actor. Projects like HBase that
depend on xz-java have no reason
ort
> for the LZMA algorithm (
> https://github.com/apache/hbase/tree/master/hbase-compression/hbase-compression-xz).
> We depend on version 1.9 of xz-java, which was published in 2021, well
> before maintenance changes in the project and the involvement of a person
> who is now beli
recent releases of the native liblzma library as a vector for malicious
> > code.
> >
> > This is not the pure Java version that we depend upon for HBase's support
> > for the LZMA algorithm (
> >
> https://github.com/apache/hbase/tree/master/hbase-compression/h
> recent releases of the native liblzma library as a vector for malicious
> > code.
> >
> > This is not the pure Java version that we depend upon for HBase's support
> > for the LZMA algorithm (
> >
> https://github.com/apache/hbase/tree/master/hbase-compres
11 matches
Mail list logo
