14rth works for me too. I am mainly interested in vectorizing
parquet-cpp as well.

On Wed, Jul 6, 2016 at 4:50 PM, Nezih Yigitbasi
<[email protected]> wrote:
> 14th works for me too.
>
> On Wed, Jul 6, 2016 at 12:54 AM Uwe Korn <[email protected]> wrote:
>
>> Yes, I'm GMT +1
>>
>>
>> On 05.07.16 18:52, Julien Le Dem wrote:
>> > If there are people interested in the cpp implementation we’ll talk
>> about that too.
>> > I’m happy to give context or help with the encoding. In particular a
>> Parquet -> Arrow vectorized converter would be great.
>> > Are you GMT +1 ?
>> > We can schedule a 1 hour slot in the morning for discussing with remote
>> folks in Europe. (same in afternoon if there are people joining from Asia)
>> > Julien
>> >
>> >> On Jul 5, 2016, at 2:37 AM, Uwe Korn <[email protected]> wrote:
>> >>
>> >> Hello,
>> >>
>> >> this effort is only for the parquet-mr project or would there also be
>> some work/benefit for parquet-cpp? If so, I might join briefly in a hangout
>> but due to the timezone shift, I probably will not be able to be awake all
>> the time.
>> >>
>> >> Uwe
>> >>
>> >> On 02.07.16 01:01, Julien Le Dem wrote:
>> >>> Dear Parquet dev list,
>> >>> There have been efforts in several projects for vectorized reads of
>> Parquet.
>> >>> We had discussed during the Parquet sync up to organize a hackathon to
>> >>> brainstorm and look into a shared implementation.
>> >>> Some projects that would benefit:
>> >>>   - Apache Drill
>> >>>   - Apache Arrow
>> >>>   - Apache Spark
>> >>>   - Presto
>> >>>   - Apache Hive
>> >>>
>> >>> I'm planning to organize this at the Dremio office in Mountain View
>> with
>> >>> optionally a hangout for people who would want to join remotely.
>> >>> I'm adding to the "to:" people that have expressed interest or could be
>> >>> interested but that's not an exhaustive list. Please respond to this
>> email
>> >>> if you wish to be included.
>> >>> Who's interested and what dates would work between this Tuesday 7/5 and
>> >>> Wednesday 7/20 ?
>> >>>
>>
>>



-- 
regards,
Deepak Majeti

Reply via email to