Github user icexelloss commented on the issue:
https://github.com/apache/spark/pull/15821
Bryan,
I am working on:
(1) Add more numbers to benchmark.py
(2) Add support for date/timestamp/binary type
(3) Fix memory leaking in the code.
All these should be done soon (tomorrow, if not today), but I think we can
start getting feedbacks from Spark committers.
What do you think? Is there anything else you want to be done before
updating the PR to Spark committers?
Li
On Wed, Jan 18, 2017 at 7:52 PM, Bryan Cutler <[email protected]>
wrote:
> Shall we update this PR to the latest and solicit from involvement from
> Spark committers?
>
> Yeah, I think it's about ready for that. After we integrate the latest
> changes, I'll go over once more for some minor cleanup and update this.
> Probably in the next day or so.
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/15821#issuecomment-273649530>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAwbrDkFMHPoyXOD0H-OYSyeAx_1EL2Jks5rTrO4gaJpZM4KtGBc>
> .
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
