PING.

[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]

----- Reply message -----
From: "Sally Khudairi" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>, <[email protected]>, 
<[email protected]>, <[email protected]>, <[email protected]>, 
<[email protected]>, <[email protected]>, <[email protected]>
Subject: PRIORITY - Fwd: SD Times story on Apache Parquet graduating to TLP
Date: Mon, Apr 27, 2015 16:09

Hello Julien and Parquet PMC --per below, the SD Times is looking to cover 
Parquet for a story tomorrow morning and needs the following questions answered.

If you can please forward your responses, I'll be happy to coordinate with Rob.

Thanks in advance,
Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]

----- Forwarded message -----
From: "Rob Marvin" <[email protected]>
To: "Sally Khudairi" <[email protected]>
Subject: SD Times story on Apache Parquet graduating to TLP
Date: Mon, Apr 27, 2015 15:41

Hi Sally,
I hope you're well. I'm reaching out because I'm putting together a brief SD 
Times story on Apache Parquet's elevation to Top-Level Project, and I'd like to 
get an original quote or two to accompany the story. Can you ping Julien Le 
Dern or another ASF member on the Apache Parquet team for a brief comment or 
two?

We're looking to run the story by tomorrow morning at the latest. Here are a 
couple questions to guide the comments:

-What is it that makes Apache Parquet unique in what the columnar storage 
format brings to the Hadoop ecosystem and the many companies using the project 
in production?

-What does Parquet's elevation to TLP signify for its development going 
forward, and what can developers expect in terms of the future growth and 
evolution of the project?

That's it! Quick and easy. Let me know if you have any questions and when I can 
expect the quotes. 

Thanks in advance for your help!

Best,
Rob

-- 
Rob MarvinOnline & Social Media EditorBZ Media LLC, SD Times
O: (631) 421-4158 x131 C: (516) [email protected]

Reply via email to