RE: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-11-11 Thread Xie, Qi
: Xu, Cheng A ; Dong, Xin ; Zhang, Jie1 Subject: Re: [Discuss] Provide pluggable APIs to support user customized compression codec Hi, Le 27/10/2020 à 09:55, Xie, Qi a écrit : > > The HW decompressor can't fall back automatically on SW decompression, but we > can fallback t

Re: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-27 Thread Antoine Pitrou
> Sent: Thursday, October 22, 2020 7:20 PM > To: dev@arrow.apache.org; Xie, Qi > Cc: Xu, Cheng A ; Dong, Xin ; > Zhang, Jie1 > Subject: Re: [Discuss] Provide pluggable APIs to support user customized > compression codec > > > Ok, thank you. Another question: why

RE: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-27 Thread Xie, Qi
u > Sent: Thursday, October 22, 2020 4:30 PM > To: Xie, Qi ; dev > Cc: Xu, Cheng A ; Dong, Xin > ; Zhang, Jie1 > Subject: Re: [Discuss] Provide pluggable APIs to support user > customized compression codec > > > Le 22/10/2020 à 05:38, Xie, Qi a écrit : >> H

Re: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-22 Thread Antoine Pitrou
Thursday, October 22, 2020 4:30 PM > To: Xie, Qi ; dev > Cc: Xu, Cheng A ; Dong, Xin ; > Zhang, Jie1 > Subject: Re: [Discuss] Provide pluggable APIs to support user customized > compression codec > > > Le 22/10/2020 à 05:38, Xie, Qi a écrit : >> Hi, >> &g

RE: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-22 Thread Xie, Qi
4:30 PM To: Xie, Qi ; dev Cc: Xu, Cheng A ; Dong, Xin ; Zhang, Jie1 Subject: Re: [Discuss] Provide pluggable APIs to support user customized compression codec Le 22/10/2020 à 05:38, Xie, Qi a écrit : > Hi, > > I just tested with the Intel QuickAssist Technology, which pr

Re: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-22 Thread Antoine Pitrou
Le 22/10/2020 à 05:38, Xie, Qi a écrit : > Hi, > > I just tested with the Intel QuickAssist Technology, which provide hardware > accelerate to GZIP, you can see detail here > https://www.intel.com/content/www/us/en/architecture-and-technology/intel-quick-assist-technology-overview.html > >

RE: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-21 Thread Xie, Qi
: dev Cc: anto...@python.org; Xu, Cheng A ; Dong, Xin ; Zhang, Jie1 ; Xie, Qi Subject: Re: [Discuss] Provide pluggable APIs to support user customized compression codec Yes, I think he's asking about the motivation for the project. My understanding is that Snappy is used more often than

Re: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-21 Thread Wes McKinney
t; > Thanks, > XieQi > > -Original Message- > From: Antoine Pitrou > Sent: Tuesday, October 20, 2020 10:38 PM > To: dev@arrow.apache.org; Xie, Qi > Cc: Xu, Cheng A ; Dong, Xin ; > Zhang, Jie1 > Subject: Re: [Discuss] Provide pluggable APIs to support user customiz

RE: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-21 Thread Xie, Qi
pluggable APIs to support user customized compression codec Le 20/10/2020 à 12:09, Xie, Qi a écrit : > Hi, Wes > > Yes currently the purpose of the key-value metadata is just a hint to > indicate that the parquet file is compressed by plugin so that the parquet > reader can

Re: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-20 Thread Antoine Pitrou
Le 20/10/2020 à 12:09, Xie, Qi a écrit : > Hi, Wes > > Yes currently the purpose of the key-value metadata is just a hint to > indicate that the parquet file is compressed by plugin so that the parquet > reader can load the plugin library and use plugin to decompress the file. > There are man

RE: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-20 Thread Xie, Qi
adata to distinguish it from the standard gzip. Thanks, XieQi -Original Message- From: Wes McKinney Sent: Tuesday, October 20, 2020 11:06 AM To: dev Cc: Xie, Qi ; Xu, Cheng A ; Dong, Xin ; Zhang, Jie1 Subject: Re: [Discuss] Provide pluggable APIs to support user customized compre

Re: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-19 Thread Wes McKinney
What is the purpose of the key-value metadata aside from automatically loading the plugin library if it's available (which seems like a security risk if reading a data file can cause a shared library to be loaded dynamically)? Is it necessary to have that metadata for it to be safe to use the optim

Re: [Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-19 Thread Antoine Pitrou
Hi, Again, I think the whole plugin concept falls outside of Arrow. It should be much simpler to simply allow people to override the compression codec factory. Then applications can define "plugins" if they want to. Regards Antoine. Le 19/10/2020 à 03:30, Xie, Qi a écrit : > Hi, all > > A

[Discuss] Provide pluggable APIs to support user customized compression codec

2020-10-18 Thread Xie, Qi
Hi, all Again as we discussed in the previous email, We are proposing an pluggable APIs to support user customized compression codec in ARROW. See proposal https://docs.google.com/document/d/1W_TxVRN7WV1wBVOTdbxngzBek1nTolMlJWy6aqC6WG8/edit We want to redefine the scope of the pluggable API and